MCP serverai.specproof/specproof-mcp
SpecProof: Search standards specs with MCP-ready precision.
Overview
Score?
UNRATED 0.681
of what a free look can see, on 32 looks
Looks
36
last 8 hr ago
Tools
17
More info
URL
mcp.specproof.ai/
streamable-http
Says it is
3gpp-spec-server 1.29.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.681 · highest on record 0.8561
Toolsfrom sha256:e842207c71…3aad17
| Tool | Schema |
|---|---|
| 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
|
input · output |
| 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
|
input · output |
| 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
|
input · output |
| get_database_stats Get comprehensive database and system statistics. |
input · output |
| 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" (o |
input · output |
| 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: Filt |
input · output |
| 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 titl |
input · output |
| 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_numbe |
input · output |
| 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, |
input · output |
| 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
In |
input · output |
| get_series_overview Get an overview of all specification series with document counts, reference statistics, and working group assignments. |
input · output |
| get_spec_dependents Get all specifications that reference a given spec (reverse lookup).
Args:
spec_number: Specification number to find dependents of
max_results: Max |
input · output |
| 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., " |
input · output |
| 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 typ |
input · output |
| list_documents List available specification documents.
Args:
doc_type: Filter by document type - "3gpp", "ietf", or "mpeg" (optional)
search_pattern: Search pattern for s |
input · output |
| search_specifications Search across 3GPP, IETF, and Multimedia specification documents using full-text search.
Args:
query: Search query terms (required)
doc_type: Filter by documen |
input · output |
| semantic_search Perform semantic search using vector embeddings with FAISS acceleration.
Args:
query: Natural language search query (required)
max_results: Maximum number |
input · output |
Verify it yourself
npx teppi-check https://mcp.specproof.ai/curl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2331DH2TE6GN48EWYKRC