mcp-registry/ai.specproof/specproof-mcp · v1.30.0
As of 2026-10-23 23:05 UTC, the Specproof MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 6 minutes.
SpecProof: Search standards specs with MCP-ready precision.
Claude Code
claude mcp add --transport http specproof-mcp-server https://mcp.specproof.ai/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"specproof-mcp-server": {
"type": "http",
"url": "https://mcp.specproof.ai/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
49 parameter(s) across 15 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 →
6 of 17 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 15 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.specproof%2Fspecproof-mcp/fixes
{
"name": "get_most_referenced_specs",
"description": "Get the most referenced (most important) specifications ranked by incoming reference count.\n\n Args:\n doc_type: Filter by \"3gpp\" or \"ietf\"\n series: Filter by series number\n limit: Maximum results (default: 20)\n ",
"inputSchema": {
"type": "object",
"title": "get_most_referenced_specsArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 20
},
"series": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Series",
"default": null
},
"doc_type": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Doc Type",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_relationship_graph",
"description": "Get a relationship graph centered on a specification, expanding N hops.\n\n Returns JSON with nodes and edges suitable for graph visualization.\n Each node includes title, series, working group, and reference counts.\n Each edge includes source, target, reference type, and count.\n\n Args:\n spec_number: Center specification number\n depth: Number of hops to expand (1-3, default: 1)\n reference_type: Filter by type - \"normative\", \"informative\" ",
"inputSchema": {
"type": "object",
"title": "get_relationship_graphArguments",
"required": [
"spec_number"
],
"properties": {
"depth": {
"type": "integer",
"title": "Depth",
"default": 1
},
"spec_number": {
"type": "string",
"title": "Spec Number"
},
"reference_type": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Reference Type",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_series_overview",
"description": "Get an overview of all specification series with document counts, reference statistics, and working group assignments.",
"inputSchema": {
"type": "object",
"title": "get_series_overviewArguments",
"properties": {}
},
"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/ai.specproof/specproof-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.specproof/specproof-mcp"}) over MCP.
diff_spec_versions ~297 tokensget_requirements ~274 tokensget_schema_definitions ~270 tokensget_spec_metadata ~269 tokensbuild_cross_spec_suite ~258 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%2Fai.specproof%2Fspecproof-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.specproof%2Fspecproof-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.specproof%2Fspecproof-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.specproof%2Fspecproof-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fai.specproof%2Fspecproof-mcp?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:34f63684d7e208e5…, first seen 2026-10-17, included at leaf 14308 of 55,119. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable code servers · most reliable data servers · most reliable retrieval servers · most reliable search 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-23 23:05 UTC, the Specproof MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 6 minutes.
Specproof MCP server advertises 17 tools, including build_cross_spec_suite, diff_spec_versions, generate_tests, get_database_stats, get_document_content.
Point your MCP client at this streamable-http endpoint: https://mcp.specproof.ai/
Glimind scanned all 17 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.