Skip to content

SpecProof

ai.specproof/specproof-mcpspecproof.aistreamable-httpv1.0.0Scanned

SpecProof: Search standards specs with MCP-ready precision.

17 tools: 2 change things and 15 only read.

Tools: 0 delete, 0 irreversible, 2 write, 15 read.
  • Reads private data · 5
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Changes things 2Claude Code: ask
  • build_cross_spec_suiteAssemble 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 sing…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • generate_testsGenerate a cited, runnable conformance test that verifies one normative requirement.1 finding

    Why it is in this group

    • The name "generate_tests" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "generate_tests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "generate_tests" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 15Show 15 read-only tools
  • diff_spec_versionsDiff two versions of a specification at the NORMATIVE level: which requirements were added, removed, or reworded.No findings

    Why it is in this group

    • The name "diff_spec_versions" says "diff": a word for reading.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_database_statsGet comprehensive database and system statistics.Reads private dataNo findings

    Why it is in this group

    • The name "get_database_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_database_stats" says "get" and "database": it reads databases.
    • private-dataThe description's first sentence says "get" and "database": it reads databases.
    Description, as the server wrote it
    Get comprehensive database and system statistics.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_document_contentGet specific content from a specification document.Reads private dataNo findings

    Why it is in this group

    • The name "get_document_content" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_document_content" says "get" and "document": it reads documents.
    • private-dataThe description's first sentence says "get" and "document": it reads documents.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_most_referenced_specsGet the most referenced (most important) specifications ranked by incoming reference count.No findings

    Why it is in this group

    • The name "get_most_referenced_specs" says "get": a word for reading.
    Description, as the server wrote it
    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)
  • get_relationship_graphGet a relationship graph centered on a specification, expanding N hops.No findings

    Why it is in this group

    • The name "get_relationship_graph" says "get": a word for reading.
    Description, as the server wrote it
    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)
  • get_requirementsList normative requirements (RFC 2119 / BCP 14 "shall/should/may" statements) extracted from specifications, each cited back to its source clause.No findings

    Why it is in this group

    • The name "get_requirements" says "get": a word for reading.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_rfc_lineageAn RFC's revision history.No findings

    Why it is in this group

    • The name "get_rfc_lineage" says "get": a word for reading.
    Description, as the server wrote it
    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"

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_schema_definitionsLook 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…No findings

    Why it is in this group

    • The name "get_schema_definitions" says "get": a word for reading.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_series_overviewGet an overview of all specification series with document counts, reference statistics, and working group assignments.Reads private dataNo findings

    Why it is in this group

    • The name "get_series_overview" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "document": it reads documents.
    Description, as the server wrote it
    Get an overview of all specification series with document counts, reference statistics, and working group assignments.
  • get_spec_dependentsGet all specifications that reference a given spec (reverse lookup).No findings

    Why it is in this group

    • The name "get_spec_dependents" says "get": a word for reading.
    Description, as the server wrote it
    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)
  • get_spec_metadataGet enriched metadata for specifications with filtering.No findings

    Why it is in this group

    • The name "get_spec_metadata" says "get": a word for reading.
    Description, as the server wrote it
    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)
  • get_spec_referencesGet all specifications referenced by a given spec.No findings

    Why it is in this group

    • The name "get_spec_references" says "get": a word for reading.
    Description, as the server wrote it
    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)
  • list_documentsList available specification documents.Reads private dataNo findings

    Why it is in this group

    • The name "list_documents" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_documents" says "list" and "document": it reads documents.
    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_specificationsSearch across 3GPP, IETF, and Multimedia specification documents using full-text search.Reads private dataNo findings

    Why it is in this group

    • The name "search_specifications" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "document": it reads documents.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Oct 22, 2026, 14:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.specproof.ai/.well-known/oauth-protected-resource
Authorization servers
https://mcp.specproof.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.specproof.ai/: tools/list returned 17 tools to an anonymous client, including generate_tests (write), build_cross_spec_suite (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "generate_tests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "generate_tests" says "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http specproof https://mcp.specproof.ai/
claude mcp add --transport http specproof https://mcp.specproof.ai/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__specproof__get_spec_references",
      "mcp__specproof__get_spec_dependents",
      "mcp__specproof__get_relationship_graph",
      "mcp__specproof__get_spec_metadata",
      "mcp__specproof__get_most_referenced_specs",
      "mcp__specproof__get_series_overview",
      "mcp__specproof__search_specifications",
      "mcp__specproof__semantic_search",
      "mcp__specproof__get_document_content",
      "mcp__specproof__list_documents",
      "mcp__specproof__get_requirements",
      "mcp__specproof__diff_spec_versions",
      "mcp__specproof__get_schema_definitions",
      "mcp__specproof__get_rfc_lineage",
      "mcp__specproof__get_database_stats"
    ],
    "ask": [
      "mcp__specproof__generate_tests",
      "mcp__specproof__build_cross_spec_suite"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as specproof. Review it before you use it.

Capability tags behind 5 rules
  • mcp__specproof__get_series_overview private-data
  • mcp__specproof__search_specifications private-data
  • mcp__specproof__get_document_content private-data
  • mcp__specproof__list_documents private-data
  • mcp__specproof__get_database_stats private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/ai.specproof/specproof-mcp/verify?hash=d5ac783fbe89bce273a0f7c422409ee3b422d86fb87a74b29d3de7425eb8e0e2" | jq -e '.changed == false'

Pinned hash d5ac783fbe89, from Oct 21, 2026, 18:31 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/ai.specproof/specproof-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for ai.specproof/specproof-mcp
[![anlyon.dev](https://anlyon.dev/badge/ai.specproof/specproof-mcp.svg)](https://anlyon.dev/servers/ai.specproof/specproof-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:43 UTC.