mcp-registry/dev.fetchgate/fetchgate · v0.1.0
As of 2026-10-18 12:58 UTC, the Fetchgate MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Fetch any URL as clean Markdown or metadata, and buy digital goods via x402 — for AI agents.
Claude Code
claude mcp add --transport http fetchgate-mcp-server https://fetchgate.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"fetchgate-mcp-server": {
"type": "http",
"url": "https://fetchgate.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,923 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.fetchgate%2Ffetchgate/fixes
{
"name": "check_base_token",
"description": "Screen a token contract on Base before an agent buys it. Reads the contract (ERC-20 metadata, owner, upgradeable proxy, and mint / pause / blacklist / fee selectors in its bytecode) and its DEX liquidity (WETH and USDC held by its Uniswap and Aerodrome pools, read on-chain). Returns a verdict — ok, caution, avoid or unknown — with the reasons. A heuristic screen: it does not simulate a sell, read tax rates or check pool age. Wraps GET /v1/token/check. Same free daily tier as read_url; $0.01/call",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$",
"description": "The token contract address on Base."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Check a Base token before swapping into it"
}{
"name": "check_x402_endpoint",
"description": "Decide whether an unfamiliar pay-per-call (x402) endpoint is worth paying. Sends one unpaid GET to read its live payment challenge (format, price, network, signing domain), then adds its settled-call and unique-payer history, whether its live price matches its listed price, and its domain's reputation (template farm or not, share of its endpoints that answer). Returns a verdict — ok, caution, avoid or unknown — with the reasons. Nothing is paid. Use before an agent sends money to an endpoint it ",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "The x402 endpoint URL to check."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Check an x402 endpoint before paying it"
}{
"name": "get_agent_census",
"description": "Return the Agent Web Crawler Census: every named bot observed crawling a live, publicly-listed x402 + MCP endpoint over a 24-hour window, each with a case-insensitive regex `matcher` and a behavioural `category` (liveness-monitor, directory-crawler, price-scraper, security-research, ai-training, ...) so you can classify your own access log. Observed first-hand, not aggregated from third-party bot lists. Notable finding: of the named agent-web crawlers in the census, zero have ever presented a pa",
"inputSchema": {
"type": "object",
"properties": {
"category": {
"type": "string",
"description": "Optional. Return only agents in this behavioural category, e.g. \"price-scraper\" or \"liveness-monitor\". Omit for the full census."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get Agent Web Crawler Census"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.fetchgate/fetchgate"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.fetchgate/fetchgate"}) over MCP.
search_x402_services ~305 tokensscan_for_prompt_injection ~228 tokensget_agent_census ~222 tokenscheck_base_token ~210 tokensscan_mcp_server ~210 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.fetchgate%2Ffetchgate?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.fetchgate%2Ffetchgate?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.fetchgate%2Ffetchgate.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.fetchgate%2Ffetchgate.svg :target: https://glimind.com/server/mcp-registry%2Fdev.fetchgate%2Ffetchgate?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:47ffa85644bd7447…, first seen 2026-10-17, included at leaf 3976 of 21,982. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable knowledge servers · most reliable web servers · most reliable commerce servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 12:58 UTC, the Fetchgate MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Fetchgate MCP server advertises 10 tools, including check_base_token, check_x402_endpoint, get_agent_census, get_metadata, get_purchase_info.
Point your MCP client at this streamable-http endpoint: https://fetchgate.dev/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.