Skip to content
External endpointresponds

SpecProof

SpecProof: Search standards specs with MCP-ready precision.

Endpoint URL
https://mcp.specproof.ai
Current status
responds
Last checked
Aug 17, 2026, 05:05 AM UTC
Check
MCP initialize · 8s limit
Latency
204 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
ai.specproof/specproof-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
3gpp-spec-server
Version
1.29.0
Capability keys
experimental, prompts, resources, tools
Tool names
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
Instructions excerpt

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 not

Reported Aug 17, 2026, 05:05 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 185ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 659ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 188ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 204ms