mcp-registry/io.github.airpote/avalanche-docs · v2.5.0
As of 2026-10-26 18:44 UTC, the Airpote Avalanche Docs MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search and retrieve Avalanche blockchain documentation for building on AVAX.
Point your MCP client at this streamable-http endpoint: https://build.avax.network/api/mcp
47 of 47 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 →
47 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
In the last 30 days: 1 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
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. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.airpote%2Favalanche-docs/fixes
{
"name": "acp_list",
"description": "List Avalanche Community Proposals with structured fields, optionally filtered by status (Activated, Implementable, Proposed, Stale, Withdrawn) or track (Standards, Best Practices, Meta, Subnet).",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"limit": {
"type": "number",
"maximum": 100,
"minimum": 1,
"description": "Maximum number of ACPs to return (default: 50)"
},
"track": {
"enum": [
"Standards",
"Best Practices",
"Meta",
"Subnet"
],
"type": "string",
"description": "Filter by ACP track. Matches Standards, Best Practices, Meta, or Subnet."
},
"status": {
"enum": [
"Proposed",
"Implementable",
"Activated",
"Stale",
"Withdrawn",
"Unknown"
],
"type": "string",
"description": "Filter by ACP status (case-insensitive)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "acp_lookup",
"description": "Look up Avalanche Community Proposals (ACPs) by number, title, or topic. When a number is provided the structured ACP record is returned (title, status, track, authors, cross-references).",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"limit": {
"type": "number",
"maximum": 20,
"minimum": 1,
"description": "Maximum number of results (default: 8)"
},
"query": {
"type": "string",
"description": "ACP title, topic, or keyword"
},
"number": {
"type": "number",
"description": "ACP number, if known"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "avalanche_docs_fetch",
"description": "Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "The page URL path (e.g., /docs/primary-network/overview)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/io.github.airpote/avalanche-docs"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.airpote/avalanche-docs"}) over MCP.
build_plan ~697 tokensonchain_activity ~467 tokenschain_stats ~377 tokensonchain_lookup ~371 tokensconsole_link ~221 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%2Fio.github.airpote%2Favalanche-docs?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.airpote%2Favalanche-docs?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.airpote%2Favalanche-docs.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.airpote%2Favalanche-docs.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.airpote%2Favalanche-docs?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:7e47d723dfed00a0…, first seen 2026-10-22, included at leaf 47518 of 74,811. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable search servers · most reliable other servers · most reliable data servers · most reliable blockchain 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-26 18:44 UTC, the Airpote Avalanche Docs MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Airpote Avalanche Docs MCP server advertises 47 tools, including acp_list, acp_lookup, avalanche_docs_fetch, avalanche_docs_list_sections, avalanche_docs_search.
Point your MCP client at this streamable-http endpoint: https://build.avax.network/api/mcp
Glimind scanned all 47 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.