SpecProof
REMOTE · MCP.SPECPROOF.AI · SCANNED SEP 25
SpecProof: Search standards specs with MCP-ready precision.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2286 tokens (~134/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SpecProof MCP server?
SpecProof is a hosted endpoint at https://mcp.specproof.ai/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.specproof.ai
claude mcp add --transport http ai-specproof-specproof-mcp 'https://mcp.specproof.ai/'
{
"mcpServers": {
"ai-specproof-specproof-mcp": {
"url": "https://mcp.specproof.ai/"
}
}
} {
"servers": {
"ai-specproof-specproof-mcp": {
"type": "http",
"url": "https://mcp.specproof.ai/"
}
}
} [mcp_servers.ai-specproof-specproof-mcp] url = "https://mcp.specproof.ai/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-specproof-specproof-mcp": {
"type": "remote",
"url": "https://mcp.specproof.ai/",
"enabled": true
}
}
} openclaw mcp add ai-specproof-specproof-mcp --url 'https://mcp.specproof.ai/' --transport streamable-http
mcp_servers:
ai-specproof-specproof-mcp:
url: "https://mcp.specproof.ai/" {
"McpServers": {
"ai-specproof-specproof-mcp": {
"Transport": "http",
"Url": "https://mcp.specproof.ai/"
}
}
} assistant mcp add ai-specproof-specproof-mcp -t streamable-http -u 'https://mcp.specproof.ai/'
{
"mcpServers": {
"ai-specproof-specproof-mcp": {
"type": "http",
"url": "https://mcp.specproof.ai/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 12 Aug 26 0
- Server version: 1.28.1 → 1.29.0 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.specproof.ai/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.specproof.ai | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 29 Jan 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | fc56cef36b9a4324c5539297c1fc3f34 |
| SANs: *.specproof.ai, specproof.ai | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
| CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 1 Feb 2010 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | 1fd6d30fca3ca51a81bbc640e35032d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.specproof.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| specproof.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.specproof.ai/ | Verified | 200 | |
| http (plaintext) | http://mcp.specproof.ai/ | HTTPS enforced | 301 | https://mcp.specproof.ai/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_cross_spec_suite Build Cross-Spec Suite ~174
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", "handover", "authentication" include_references: Also pull matching clauses from specs this one references (default: True) limit: Max requirements in the plan (default: 20, max: 50)
| Name | Type | Req | Description |
|---|---|---|---|
| include_references | boolean | – | – |
| keyword | string | yes | – |
| limit | integer | – | – |
| spec_base | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diff_spec_versions Diff Spec Versions ~208
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) to_version: Newer version label, e.g. "j30" (default: the newest in the corpus) obligation: Only report changes at this strength — "must", "must_not", "should", "should_not", "may" limit: Max requirements to list per bucket (default: 25)
| Name | Type | Req | Description |
|---|---|---|---|
| from_version | – | – | – |
| limit | integer | – | – |
| obligation | – | – | – |
| spec_base | string | yes | – |
| to_version | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_tests Generate Conformance Tests ~152
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: requirement_id: The requirement's id, as shown by get_requirements target: "pytest" for a runnable Python test module, or "gherkin" for a reviewable .feature file (default: pytest)
| Name | Type | Req | Description |
|---|---|---|---|
| requirement_id | integer | yes | – |
| target | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_database_stats Database Statistics ~16
Get comprehensive database and system statistics.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_document_content Get Document Content ~78
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)
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | – |
| page_range | – | – | – |
| section | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_most_referenced_specs ~83
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)
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | – | – | – |
| limit | integer | – | – |
| series | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_relationship_graph ~133
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 to expand (1-3, default: 1) reference_type: Filter by type - "normative", "informative" (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| reference_type | – | – | – |
| spec_number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_requirements Get Requirements ~159
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 requirement text (optional) limit: Maximum number of requirements to return (default: 30, max: 100)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| obligation | – | – | – |
| search | – | – | – |
| spec_number | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_rfc_lineage RFC Lineage ~120
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"
| Name | Type | Req | Description |
|---|---|---|---|
| rfc | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_schema_definitions Get Schema Definitions ~213
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 than recalled. Args: name: Type or schema name, e.g. "RRCSetup", "MeasConfig", "SmContextCreateData" spec_number: Restrict to a spec, e.g. "38.331" kind: "asn1", "openapi" or "json_schema" limit: Maximum definitions to return (default: 10, max: 25)
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | – |
| limit | integer | – | – |
| name | – | – | – |
| spec_number | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_series_overview ~29
Get an overview of all specification series with document counts, reference statistics, and working group assignments.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_spec_dependents ~66
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)
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| spec_number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_spec_metadata ~125
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)
| Name | Type | Req | Description |
|---|---|---|---|
| doc_class | – | – | – |
| limit | integer | – | – |
| series | – | – | – |
| spec_number | – | – | – |
| working_group | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_spec_references ~79
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)
| Name | Type | Req | Description |
|---|---|---|---|
| reference_type | – | – | – |
| spec_number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_documents List Documents ~93
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)
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | – | – | – |
| limit | integer | – | – |
| search_pattern | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_specifications Search Specifications ~125
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)
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | – | – | – |
| max_results | integer | – | – |
| query | string | yes | – |
| spec_number | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
semantic_search Semantic Search ~135
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)
| Name | Type | Req | Description |
|---|---|---|---|
| index_type | – | – | – |
| max_results | integer | – | – |
| query | string | yes | – |
| similarity_threshold | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the SpecProof MCP server?
SpecProof is an MCP server listed in the public MCP registry as ai.specproof/specproof-mcp. SpecProof: Search standards specs with MCP-ready precision. This page covers its hosted endpoint (https://mcp.specproof.ai/).
Is the SpecProof MCP server safe to use?
SpecProof scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SpecProof MCP server expose?
SpecProof exposes 17 tools: get_spec_references, get_spec_dependents, get_relationship_graph, get_spec_metadata, get_most_referenced_specs, and 12 more. Their descriptions and schemas cost roughly 1,988 tokens of context every time the server is loaded.
Does the SpecProof MCP server require authentication?
No. We connected to SpecProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SpecProof MCP server still maintained?
SpecProof is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.