Skip to content
MCPSTAMP
MCP server report

SpecProof MCP server

ai.specproof/specproof-mcp

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 79 of 100 (grade C), higher than 24.9% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
79C
Sign-in
OAuth
Tools listed
17
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by readOnlyHint or destructiveHint on every tool and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

7 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 6/17 tools set neither readOnlyHint nor destructiveHint: get_spec_references, get_spec_dependents, get_relationship_graph, get_spec_metadata, get_most_reference

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 6/17 tools miss an explicit hint: get_spec_references, get_spec_dependents, get_relationship_graph, get_spec_metadata, get_most_referenced_specs and 1 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  3. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 6/17 without title: get_spec_references, get_spec_dependents, get_relationship_graph, get_spec_metadata, get_most_referenced_specs and 1 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  4. Fails

    initialize latency

    latency

    Measured 5165 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

  5. Fails

    GET answers SSE or 405

    get_stream

    Measured HTTP 200 application/json

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

  6. Warning

    Tool descriptions

    tool_descriptions

    Measured 1 under 60 chars: get_database_stats

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  7. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured JSON-RPC error -32602 instead of -32601

    Return JSON-RPC error code -32601 (Method not found) for unknown methods.

19 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for SpecProof

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.specproof.ai%2F)](https://www.mcpstamp.com/r/ai-specproof-specproof-mcp/)

HTML

<a href="https://www.mcpstamp.com/r/ai-specproof-specproof-mcp/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fmcp.specproof.ai%2F" alt="McpStamp score" height="20"></a>
Registry entry

About this server

SpecProof: Search standards specs with MCP-ready precision.
Registry name
ai.specproof/specproof-mcp
Remote URL
https://mcp.specproof.ai/
Version
1.0.0
Source
github.com/ibouazizi/specproof.git
Website
specproof.ai
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade C servers

All grade C servers · All server reports · State of MCP readiness, November 2026