# SpecProof (remote · mcp.specproof.ai)

SpecProof: Search standards specs with MCP-ready precision.

- Trust score: 62/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.specproof.ai`: 62/100 (this document), [markdown](https://verifymcp.io/servers/ai-specproof-specproof-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-specproof-specproof-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.specproof.ai/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.ai-specproof-specproof-mcp]
url = "https://mcp.specproof.ai/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-specproof-specproof-mcp": {
      "type": "remote",
      "url": "https://mcp.specproof.ai/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-specproof-specproof-mcp --url https://mcp.specproof.ai/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-specproof-specproof-mcp:
    url: "https://mcp.specproof.ai/"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (17)

### `get_spec_references` (~79 tokens)

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)

Input parameters:

- `reference_type`
- `spec_number` (string, required)

Output parameters:

- `result` (string)

### `get_spec_dependents` (~66 tokens)

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)

Input parameters:

- `max_results` (integer)
- `spec_number` (string, required)

Output parameters:

- `result` (string)

### `get_relationship_graph` (~133 tokens)

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)

Input parameters:

- `depth` (integer)
- `reference_type`
- `spec_number` (string, required)

Output parameters:

- `result` (string)

### `get_spec_metadata` (~125 tokens)

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)

Input parameters:

- `doc_class`
- `limit` (integer)
- `series`
- `spec_number`
- `working_group`

Output parameters:

- `result` (string)

### `get_most_referenced_specs` (~83 tokens)

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)

Input parameters:

- `doc_type`
- `limit` (integer)
- `series`

Output parameters:

- `result` (string)

### `get_series_overview` (~29 tokens)

Get an overview of all specification series with document counts, reference statistics, and working group assignments.

Output parameters:

- `result` (string)

### `search_specifications` (~125 tokens)

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)

Input parameters:

- `doc_type`
- `max_results` (integer)
- `query` (string, required)
- `spec_number`

Output parameters:

- `result` (string)

### `semantic_search` (~135 tokens)

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)

Input parameters:

- `index_type`
- `max_results` (integer)
- `query` (string, required)
- `similarity_threshold` (number)

Output parameters:

- `result` (string)

### `get_document_content` (~78 tokens)

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)

Input parameters:

- `filename` (string, required)
- `page_range`
- `section`

Output parameters:

- `result` (string)

### `list_documents` (~93 tokens)

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)

Input parameters:

- `doc_type`
- `limit` (integer)
- `search_pattern`

Output parameters:

- `result` (string)

### `get_requirements` (~159 tokens)

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 requirement text (optional)
        limit: Maximum number of requirements to return (default: 30, max: 100)

Input parameters:

- `limit` (integer)
- `obligation`
- `search`
- `spec_number`

Output parameters:

- `result` (string)

### `generate_tests` (~152 tokens)

Generate Conformance 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:
        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)

Input parameters:

- `requirement_id` (integer, required)
- `target` (string)

Output parameters:

- `result` (string)

### `diff_spec_versions` (~208 tokens)

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)

Input parameters:

- `from_version`
- `limit` (integer)
- `obligation`
- `spec_base` (string, required)
- `to_version`

Output parameters:

- `result` (string)

### `get_schema_definitions` (~213 tokens)

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 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)

Input parameters:

- `kind`
- `limit` (integer)
- `name`
- `spec_number`

Output parameters:

- `result` (string)

### `get_rfc_lineage` (~120 tokens)

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"

Input parameters:

- `rfc` (string, required)

Output parameters:

- `result` (string)

### `build_cross_spec_suite` (~174 tokens)

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)

Input parameters:

- `include_references` (boolean)
- `keyword` (string, required)
- `limit` (integer)
- `spec_base` (string, required)

Output parameters:

- `result` (string)

### `get_database_stats` (~16 tokens)

Database Statistics

Get comprehensive database and system statistics.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-specproof-specproof-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 61
- 2026-07-31: 60
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://mcp.specproof.ai/
- Repository: https://github.com/ibouazizi/specproof.git
- Website: https://specproof.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-specproof-specproof-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-specproof-specproof-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-specproof-specproof-mcp/mcp