SpecProof
SpecProof: Search standards specs with MCP-ready precision.
| Endpoint | https://mcp.specproof.ai (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 17 tools · grade C (76) · pin ts_e6d36d301ecff40fdd6aafa2b1301b52 · protocol 2025-06-18 |
| First / last listed | 2026-10-27 05:54 UTC / 2026-10-27 05:54 UTC |
| Grade over time | 2026-10-27: C (76), 17 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: 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
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)
params: spec_number*, reference_type |
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)
params: spec_number*, max_results |
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, target, reference type, and count.
Args:
spec_number: Center specification number
depth: Number of hops params: spec_number*, depth, reference_type |
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 by document class - "TS" or "TR"
limit: Maximum results (default: 50)
params: spec_number, series, working_group, doc_class, limit |
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)
params: doc_type, series, limit |
get_series_overview | Get an overview of all specification series with document counts, reference statistics, and working group assignments. params: none |
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 specification number (optional)
max_results: Maximum number of results to return (default: 10, max: 50)
params: 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 threshold 0.0-1.0 (default: 0.3)
index_type: FAISS index type - "hnsw", "ivf", or "flat" (optional, auto-selected)
params: query*, max_results, similarity_threshold, index_type |
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)
params: filename*, page_range, section |
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: 100)
params: doc_type, search_pattern, limit |
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: Filter by strength - "must", "must_not", "should", "should_not", or "may" (optional)
search: Keyword to search within the requi params: spec_number, obligation, search, 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. If the requirement
is not testable (boilerplate, scope text), the generator abstains rather than inventing
a test.
Args:
requireme params: requirement_id*, target |
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 without the version, e.g. "38331" or "23501"
from_version: Older version label, e.g. "j20" (default: the second-newest in the corpus)
params: spec_base*, from_version, to_version, obligation, limit |
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 a message's *structure* — field
names, types, ranges, optionality. The definition is returned verbatim from the spec, so
it is exact rather params: name, spec_number, kind, 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 depend on has been superseded.
Args:
rfc: The RFC, e.g. "7231", "rfc7231" or "RFC 7231"
params: rfc* |
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 requirement_ids to generate_tests.
Args:
spec_base: The anchor spec, e.g. "23502" or "38331"
keyword: The procedure/topic, e.g. "registration params: spec_base*, keyword*, include_references, limit |
get_database_stats | Get comprehensive database and system statistics. params: none |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.