SpecProof is an MCP server with 17 tools an agent can call, among them build_cross_spec_suite, diff_spec_versions, generate_tests. It answers at https://mcp.specproof.ai/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
SpecProof: Search standards specs with MCP-ready precision.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
build_cross_spec_suite | Assemble the normative requirements for one procedure across a spec AND the specs it normatively references — a procedure like registration or handover is never described in a single document. Returns a cited suite plan; feed the requiremen Inputs: spec_base, keyword, include_references, limit |
diff_spec_versions | Diff two versions of a specification at the NORMATIVE level: which requirements were added, removed, or reworded. Not a textual diff — a clause that merely moved page or was recased counts as unchanged. Args: spec_base: Spec identity withou Inputs: spec_base, from_version, to_version, obligation, limit |
generate_tests | Generate a cited, runnable conformance test that verifies one normative requirement. The test is grounded in the requirement sentence plus its surrounding clause from the corpus, and every test cites the spec, section and page it enforces. Inputs: requirement_id, target |
get_database_stats | Get comprehensive database and system statistics. |
get_document_content | Get specific content from a specification document. Args: filename: Document filename (required) page_range: Page range like "10-15" or single page "20" (optional) section: Section title filter (optional) Inputs: filename, page_range, section |
get_most_referenced_specs | Get the most referenced (most important) specifications ranked by incoming reference count. Args: doc_type: Filter by "3gpp" or "ietf" series: Filter by series number limit: Maximum results (default: 20) Inputs: doc_type, series, limit |
get_relationship_graph | Get a relationship graph centered on a specification, expanding N hops. Returns JSON with nodes and edges suitable for graph visualization. Each node includes title, series, working group, and reference counts. Each edge includes source, ta Inputs: spec_number, depth, reference_type |
get_requirements | List normative requirements (RFC 2119 / BCP 14 "shall/should/may" statements) extracted from specifications, each cited back to its source clause. Args: spec_number: Filter by spec number, e.g. "23.501" or "RFC 9110" (optional) obligation: Inputs: spec_number, obligation, search, limit |
get_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 Obsoletes/Updates graph, not a version diff, IS its change history. Use it to find out whether an RFC you dep Inputs: rfc |
get_schema_definitions | Look up formal, machine-checkable structure defined in the specifications: ASN.1 types (3GPP RRC/NAS message grammars) and JSON Schema / OpenAPI models (5G Service Based Interfaces). Prefer this over prose search when the question is about Inputs: name, spec_number, kind, limit |
get_series_overview | Get an overview of all specification series with document counts, reference statistics, and working group assignments. |
get_spec_dependents | Get all specifications that reference a given spec (reverse lookup). Args: spec_number: Specification number to find dependents of max_results: Maximum results (default: 50) Inputs: spec_number, max_results |
get_spec_metadata | Get enriched metadata for specifications with filtering. Args: spec_number: Filter by spec number (partial match) series: Filter by series (e.g., "26" for 26.xxx codecs) working_group: Filter by working group (e.g., "SA4") doc_class: Filter Inputs: spec_number, series, working_group, doc_class, limit |
get_spec_references | Get all specifications referenced by a given spec. Args: spec_number: Specification number (e.g., "23.501", "26.230") reference_type: Filter by type - "normative", "informative", "inline" (optional) Inputs: spec_number, reference_type |
list_documents | List available specification documents. Args: doc_type: Filter by document type - "3gpp", "ietf", or "mpeg" (optional) search_pattern: Search pattern for spec number or title (optional) limit: Maximum number of results (default: 20, max: 10 Inputs: doc_type, search_pattern, limit |
search_specifications | Search across 3GPP, IETF, and Multimedia specification documents using full-text search. Args: query: Search query terms (required) doc_type: Filter by document type - "3gpp", "ietf", or "mpeg" (optional) spec_number: Filter by specificatio Inputs: query, doc_type, spec_number, max_results |
semantic_search | Perform semantic search using vector embeddings with FAISS acceleration. Args: query: Natural language search query (required) max_results: Maximum number of results to return (default: 5, max: 20) similarity_threshold: Minimum similarity t Inputs: query, max_results, similarity_threshold, index_type |
Every block below points at https://mcp.specproof.ai/. Pick your client and copy.
claude mcp add --transport http specproof https://mcp.specproof.ai/
{
"mcpServers": {
"specproof": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.specproof.ai/"]
}
}
}{
"mcpServers": {
"specproof": {
"url": "https://mcp.specproof.ai/"
}
}
}{
"servers": {
"specproof": {
"type": "http",
"url": "https://mcp.specproof.ai/"
}
}
}{
"context_servers": {
"specproof": {
"url": "https://mcp.specproof.ai/"
}
}
}{
"mcpServers": {
"specproof": {
"serverUrl": "https://mcp.specproof.ai/"
}
}
}{
"mcpServers": {
"specproof": {
"url": "https://mcp.specproof.ai/"
}
}
}name: SpecProof
version: 0.0.1
schema: v1
mcpServers:
- name: SpecProof
type: streamable-http
url: https://mcp.specproof.ai/{
"mcpServers": {
"specproof": {
"httpUrl": "https://mcp.specproof.ai/"
}
}
}{
"mcpServers": {
"specproof": {
"type": "http",
"url": "https://mcp.specproof.ai/"
}
}
}{
"mcpServers": {
"specproof": {
"url": "https://mcp.specproof.ai/"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.specproof.ai%2F&type=streamable_http&id=specproof&name=SpecProof
It answered our last check on 17 October 2026 in 379 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by specproof.ai and served from mcp.specproof.ai, the vendor's own domain: https://mcp.specproof.ai/.
17, as returned by the server's own tools/list on 8 September 2026: build_cross_spec_suite, diff_spec_versions, generate_tests, get_database_stats, get_document_content, get_most_referenced_specs, get_relationship_graph, get_requirements, and 9 more.
It answered our last check on 17 October 2026 in 379 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.specproof.ai/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.specproof. Endpoint host: mcp.specproof.ai. ARD identifier: urn:air:ai.specproof:mcp:specproof-mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.