General Catalyst MCP server

Which servers in the official MCP registry are General Catalyst's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to General Catalyst

Whose server it is

Registry namedev.past/pastverified in the MCP registry

The registry name sits under past.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools3
Server calls itselfpast-docs
Server version1.0.0
Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 120 ms.

Measured dailydaily checks: 1, the first on 2026-10-19

Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer235 ms
Space in an agent's context≈ 241 tokensthe definitions of all its tools (3), which an agent carries on every turn
Tool definitionsA · 100 of 100

Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.

Tools it offers3 tools · read 2026-10-19

search_docs
Search the past.dev developer documentation (Memory API and MCP server) and get back matching pages with an excerpt. Lexical search over the full corpus.
read_page
Read one documentation page as Markdown. Get product and slug values from list_pages or search_docs.
list_pages
List every documentation page with its product, slug, title and URL.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "past": {
      "type": "http",
      "url": "https://past.dev/mcp"
    }
  }
}

OpenAPI spec

27 paths, read 2026-10-19. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.