Home / MCP registry index / ai.specproof/specproof-mcp
SpecProof
ai.specproof/specproof-mcp in the official MCP registry.
Endpoint https://mcp.specproof.ai/. Source: github.com/ibouazizi/specproof.git.
The registry describes it as: SpecProof: Search standards specs with MCP-ready precision.
We read its 17 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_spec_references get_spec_dependents get_relationship_graph get_spec_metadata get_most_referenced_specs get_series_overview search_specifications semantic_search get_document_content list_documents get_requirements generate_tests diff_spec_versions get_schema_definitions get_rfc_lineage build_cross_spec_suite get_database_stats
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-specproof-specproof-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.