SpecProof
v1.0.0SpecProof: Search standards specs with MCP-ready precision.
Endpoint health
online- Last checked
- 11/20/2026, 5:16:43 AM
- Latency
- 110 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.specproof%2Fspecproof-mcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.specproof/specproof-mcp": {
"url": "https://mcp.specproof.ai/"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
17 shown · authentication unknown
Build Cross-Spec Suite
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", "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)
Schema valid · SHA-256 f089e930576c…
View input schema
{ "type": "object", "properties": { "spec_base": { "title": "Spec Base", "type": "string" }, "keyword": { "title": "Keyword", "type": "string" }, "include_references": { "default": true, "title": "Include References", "type": "boolean" }, "limit": { "default": 20, "title": "Limit", "type": "integer" } }, "required": [ "spec_base", "keyword" ], "title": "build_cross_spec_suiteArguments" }Diff Spec Versions
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) 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)
Connections
streamable-http
https://mcp.specproof.ai/