Developer Tools
specproof.ai
Analyzes and retrieves relationships and metadata for specifications.
ENDPOINT 1
https://mcp.specproof.ai
MCP server metadata
- Name
- 3gpp-spec-server
- Version
- 1.28.1
SpecProof serves 3GPP, IETF and MPEG specification text indexed from the published documents. Equations are preserved verbatim from the source specification and are delimited with $...$ (inline) and $$...$$ (display) inside the text these tools return. When quoting or presenting an equation: - Copy the stored string exactly, including its $ delimiters. Do not retype it, do not reformat it across multiple lines, and do not convert it to \( \) or \[ \] form. Retyping silently loses characters -- a dropped "=" turns a normative formula into nonsense that still reads as an equation -- and the \( \) and \[ \] delimiters lose their backslashes to markdown in most clients, which corrupts the equation on screen. - If you need to explain an equation, quote it verbatim first, then describe it separately. - A passage containing "[equation image]" marks an equation that could not be converted to LaTeX. Say that it is unavailable rather than reconstructing it. Other notes: - page_number is the chunk's position in the extracted text, not the specification's own printed pagination. Cite clause numbers, which are authoritative; do not cite page numbers. - Requirements carry req_uid, a version-stable identifier; req_key is not stable across re-indexing and should not be persisted.
Known tools 17
get_spec_dependentsGet all specifications that reference a given spec (reverse lookup).
Inferred read-onlyget_relationship_graphGet a relationship graph centered on a specification, expanding N hops.
Inferred read-onlyget_most_referenced_specsGet the most referenced (most important) specifications ranked by incoming reference count.
Inferred read-onlyget_series_overviewGet an overview of all specification series with document counts, reference statistics, and working group assignments.
Inferred read-onlysearch_specificationsSearch across 3GPP, IETF, and Multimedia specification documents using full-text search.
Inferred read-onlysemantic_searchPerform semantic search using vector embeddings with FAISS acceleration.
Inferred read-onlyget_requirementsList normative requirements (RFC 2119 / BCP 14 "shall/should/may" statements) extracted from specifications, each cited back to its source clause.
Inferred read-onlygenerate_testsGenerate a cited, runnable conformance test that verifies one normative requirement.
Inferred read-onlydiff_spec_versionsDiff two versions of a specification at the NORMATIVE level: which requirements were added, removed, or reworded.
Inferred read-onlyget_schema_definitionsLook up formal, machine-checkable structure defined in the specifications: ASN.
Inferred read-onlybuild_cross_spec_suiteAssemble 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.3gpp-spec-server]
url = "https://mcp.specproof.ai"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"3gpp-spec-server": {
"type": "http",
"url": "https://mcp.specproof.ai"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: 3gpp-spec-server
Remote MCP URL: https://mcp.specproof.ai
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"3gpp-spec-server": {
"url": "https://mcp.specproof.ai"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"3gpp-spec-server": {
"type": "http",
"url": "https://mcp.specproof.ai"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "3gpp-spec-server",
"transport": "streamable-http",
"url": "https://mcp.specproof.ai"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.