Categories › Data & Databases › NoSQL, key-value & search engines
SpecProof: Search standards specs with MCP-ready precision.
Remote server: your requests and data go to mcp.specproof.ai. Claude Code: claude mcp add --transport http specproof https://mcp.specproof.ai/ · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
get_spec_references — Get all specifications referenced by a given spec. Args: spec_number: Specification number (e.g., "23.501", "26.230") reference_type: Filterget_spec_dependents — Get all specifications that reference a given spec (reverse lookup). Args: spec_number: Specification number to find dependents of max_resulget_relationship_graph — Get a relationship graph centered on a specification, expanding N hops. Returns JSON with nodes and edges suitable for graph visualization. get_spec_metadata — Get enriched metadata for specifications with filtering. Args: spec_number: Filter by spec number (partial match) series: Filter by series (get_most_referenced_specs — Get the most referenced (most important) specifications ranked by incoming reference count. Args: doc_type: Filter by "3gpp" or "ietf" serieget_series_overview — Get an overview of all specification series with document counts, reference statistics, and working group assignments.search_specifications — Search across 3GPP, IETF, and Multimedia specification documents using full-text search. Args: query: Search query terms (required) doc_typesemantic_search — Perform semantic search using vector embeddings with FAISS acceleration. Args: query: Natural language search query (required) max_results: get_document_content — Get specific content from a specification document. Args: filename: Document filename (required) page_range: Page range like "10-15" or singlist_documents — List available specification documents. Args: doc_type: Filter by document type - "3gpp", "ietf", or "mpeg" (optional) search_pattern: Searcget_requirements — List normative requirements (RFC 2119 / BCP 14 "shall/should/may" statements) extracted from specifications, each cited back to its source cgenerate_tests — Generate a cited, runnable conformance test that verifies one normative requirement. The test is grounded in the requirement sentence plus idiff_spec_versions — Diff two versions of a specification at the NORMATIVE level: which requirements were added, removed, or reworded. Not a textual diff — a claget_schema_definitions — Look up formal, machine-checkable structure defined in the specifications: ASN.1 types (3GPP RRC/NAS message grammars) and JSON Schema / Opeget_rfc_lineage — An RFC's revision history. RFCs are immutable — an RFC is never revised, it is obsoleted or updated by a *different* RFC — so this Obsoletesbuild_cross_spec_suite — Assemble the normative requirements for one procedure across a spec AND the specs it normatively references — a procedure like registration get_database_stats — Get comprehensive database and system statistics.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.