# `ai.specproof/specproof-mcp` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://anlyon.dev/servers/ai.specproof/specproof-mcp
- JSON: https://anlyon.dev/api/v1/servers/ai.specproof/specproof-mcp
- Version: 1.0.0 (active)
- Publisher: ai.specproof (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Repository: https://github.com/ibouazizi/specproof.git
- Metadata from the official MCP Registry, synced 2026-10-21T17:43:28.986Z

Title and description, as the publisher wrote them:

```untrusted-server-text
SpecProof
SpecProof: Search standards specs with MCP-ready precision.
```

Scanned 2026-10-21T18:31:07.500Z over streamable-http.

**17 tools: 2 change things and 15 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 2 | ask |
| Only reads | read | 15 | allow |

## Exfil surface

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

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | `mcp__specproof__get_database_stats` `mcp__specproof__get_document_content` `mcp__specproof__get_series_overview` `mcp__specproof__list_documents` `mcp__specproof__search_specifications` |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

- **warn** Annotations that disagree with the tool in `generate_tests` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

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

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


## Changes things (2)

Creates or changes something that can be changed back. Claude Code: ask.

### `build_cross_spec_suite`

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

```untrusted-server-text
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)
    
```

### `generate_tests`

- 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 annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

## Only reads (15)

Looks things up and changes nothing. Claude Code: allow.

### `diff_spec_versions`

- The name "diff_spec_versions" says "diff": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

### `get_database_stats`

- The name "get_database_stats" says "get": a word for reading.
- Tag private-data: The name "get_database_stats" says "get" and "database": it reads databases. The description's first sentence says "get" and "database": it reads databases.

Description, as the server wrote it:

```untrusted-server-text
Get comprehensive database and system statistics.
```

### `get_document_content`

- The name "get_document_content" says "get": a word for reading.
- Tag private-data: The name "get_document_content" says "get" and "document": it reads documents. The description's first sentence says "get" and "document": it reads documents.

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

### `get_most_referenced_specs`

- The name "get_most_referenced_specs" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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_graph`

- The name "get_relationship_graph" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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_requirements`

- The name "get_requirements" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

### `get_rfc_lineage`

- The name "get_rfc_lineage" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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"
    
```

### `get_schema_definitions`

- The name "get_schema_definitions" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

### `get_series_overview`

- The name "get_series_overview" says "get": a word for reading.
- Tag private-data: The description's first sentence says "get" and "document": it reads documents.

Description, as the server wrote it:

```untrusted-server-text
Get an overview of all specification series with document counts, reference statistics, and working group assignments.
```

### `get_spec_dependents`

- The name "get_spec_dependents" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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_metadata`

- The name "get_spec_metadata" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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_references`

- The name "get_spec_references" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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_documents`

- The name "list_documents" says "list": a word for reading.
- Tag private-data: The name "list_documents" says "list" and "document": it reads documents. The description's first sentence says "list" and "document": it reads documents.

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

### `search_specifications`

- The name "search_specifications" says "search": a word for reading.
- Tag private-data: The description's first sentence says "search" and "document": it reads documents.

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

### `semantic_search`

- The name "semantic_search" says "search": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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)
    
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `specproof`:

```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": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

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

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-10-22T14:21:17.530Z, unchanged since 2026-10-22T14:21:17.530Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://anlyon.dev/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| 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 | `none` |
| 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` |

- **warn** Tools that change things, listed to anyone ([unauth-remote-writes](https://anlyon.dev/methodology#unauth-remote-writes))

```untrusted-server-text
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.

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