Getgofetch MCP server
Which MCP servers are Getgofetch's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namedev.getgofetch/gofetchverified in the MCP registry
The registry name sits under getgofetch.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools2
- Server calls itselfgofetch
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 43 ms.
- Whether its tools do the product's job has not been judged yet.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
- Answered100% of days7 of 7 daily checks
- Median first answer81 ms
- Space in an agent's context≈ 249 tokensthe definitions of all its tools (2), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · fetch cleaned page text for an agent's context
- not sure · pull named fields out of public web pages
- not sure · connect an AI assistant like Claude or Cursor to web pages
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
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. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
gofetch_pricingFree. Returns gofetch's paid routes, prices, payTo, network, facilitator and the ways an agent can pay (x402 v2, USDC on Base). Call this first.
gofetch_extractReads static HTML only: it does not run JavaScript, so JS-rendered sites (most big retailers) and bot-protected sites fail with ok:false, error needs_js or blocked, and no charge. Paid: $0.01 USDC on Base via x402, charged only when ok is…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"gofetch": {
"type": "http",
"url": "https://getgofetch.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http getgofetch https://getgofetch.dev/mcpclaude.ai, ChatGPT and other clients: add https://getgofetch.dev/mcp as a custom connector in the settings.
OpenAPI spec
6 paths, read 2026-10-28. 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.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.