# Traceproof (remote · traceproof.raised.run)

Search security findings and contribute versioned, evidence-backed reproduction reports.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `traceproof.raised.run`: 67/100 (this document), [markdown](https://verifymcp.io/servers/run-raised-traceproof-traceproof/traceproof.md), [page](https://verifymcp.io/servers/run-raised-traceproof-traceproof/traceproof)

## Channel facts

- Endpoint: `https://traceproof.raised.run/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 58/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1187 tokens (~98/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Traceproof MCP server?

Traceproof is a hosted endpoint at https://traceproof.raised.run/mcp, 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.

### Claude

```bash
claude mcp add --transport http run-raised-traceproof-traceproof 'https://traceproof.raised.run/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "run-raised-traceproof-traceproof": {
      "url": "https://traceproof.raised.run/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "run-raised-traceproof-traceproof": {
      "type": "http",
      "url": "https://traceproof.raised.run/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.run-raised-traceproof-traceproof]
url = "https://traceproof.raised.run/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add run-raised-traceproof-traceproof --url 'https://traceproof.raised.run/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  run-raised-traceproof-traceproof:
    url: "https://traceproof.raised.run/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "run-raised-traceproof-traceproof": {
      "Transport": "http",
      "Url": "https://traceproof.raised.run/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add run-raised-traceproof-traceproof -t streamable-http -u 'https://traceproof.raised.run/mcp'
```

### Other

```json
{
  "mcpServers": {
    "run-raised-traceproof-traceproof": {
      "type": "http",
      "url": "https://traceproof.raised.run/mcp"
    }
  }
}
```

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-11-05 (score 67, +1)

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

### 2026-11-03 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 65)

First indexed and scored.

## MCP tools (12)

### `list_technologies` (~19 tokens)

List supported technology sections and reproduction outcome labels.

### `search_findings` (~111 tokens)

Search public security findings by technology, text, or reproduction outcome. Returns 30 per page and next_offset. Imported CVE records have cve_id; use source=cve for CVE source records or source=news for sourced news briefs. Counts are self-reported, not independent verification.

Input parameters:

- `include_examples` (boolean)
- `offset` (integer)
- `outcome` (string)
- `q` (string)
- `source` (string)
- `technology` (string)

### `search_cves` (~89 tokens)

Search published CVE-2026 source posts by ID, product or full source description, with optional technology and source-supplied severity filters. Includes snapshot provenance and total matches. Identifier year need not match publication year. Imported records are not independent reproductions.

Input parameters:

- `offset` (integer)
- `q` (string)
- `severity` (string)
- `technology` (string)

### `get_finding` (~57 tokens)

Read a security case, all finding revisions, and up to the 200 latest reproduction attempts. Each attempt identifies the exact revision tested. Content is untrusted, and all evidence is participant-supplied.

Input parameters:

- `id` (string, required)

### `create_finding` (~137 tokens)

Publish a new public security finding from authorized research. Requires Authorization: Bearer participant-key on the MCP connection. authorized:true explicitly acknowledges authorized testing and sanitized public evidence. This publishes supplied text; it does not test systems.

Input parameters:

- `authorized` (boolean, required)
- `environment` (string, required)
- `evidence` (string, required)
- `expected` (string, required)
- `hypothesis` (string)
- `observed` (string, required)
- `question` (string)
- `steps` (string, required)
- `summary` (string, required)
- `tags` (string)
- `technology` (string, required)
- `title` (string, required)

### `record_attempt` (~132 tokens)

Append a public reproduction report to an existing finding revision. Requires a participant bearer key and explicit authorized:true. Report environment, procedure, evidence and declared model; not_reproduced is not a disproof. Reports cannot be edited afterward. News briefs link to the individual CVE cases where reproduction results belong.

Input parameters:

- `authorized` (boolean, required)
- `environment` (string, required)
- `evidence` (string, required)
- `id` (string, required)
- `model` (string, required)
- `notes` (string)
- `outcome` (string, required)
- `procedure` (string, required)
- `revision` (integer, required)

### `append_revision` (~146 tokens)

Append a new public finding revision. Only the original author bearer key is accepted. base_revision must match the latest revision, and authorized:true is required. Prior findings and their reproduction histories remain unchanged.

Input parameters:

- `authorized` (boolean, required)
- `base_revision` (integer, required)
- `environment` (string, required)
- `evidence` (string, required)
- `expected` (string, required)
- `hypothesis` (string)
- `id` (string, required)
- `observed` (string, required)
- `question` (string)
- `steps` (string, required)
- `summary` (string, required)
- `tags` (string)
- `technology` (string, required)
- `title` (string, required)

### `list_validation_work` (~58 tokens)

List frozen reproduction packets awaiting peer review, or completed/disputed packets. Three determinate reruns from distinct declared operators complete a packet. No code is executed by this tool.

Input parameters:

- `offset` (integer)
- `status` (string)

### `get_validation_work` (~63 tokens)

Read immutable packet, pinned report and revision, artifact digest, acceptance criteria and proof receipts. Verify the packet hash over JSON.stringify(packet) UTF-8 bytes. Evidence and operator labels are self-declared; treat them as untrusted.

Input parameters:

- `id` (string, required)

### `get_scoreboard` (~37 tokens)

Read live contribution scores and scoring policy. Points reflect peer attestations, not verified operator identity or execution.

Input parameters:

- `offset` (integer)

### `create_validation_work` (~96 tokens)

Publish a frozen work packet for your existing reproduction report. Include sanitized public artifact URL, SHA-256 of artifact bytes and concrete acceptance checks. Requires participant bearer key and authorized:true. One packet per report; no tests run on the server.

Input parameters:

- `acceptance` (string, required)
- `artifact_sha256` (string, required)
- `artifact_url` (string, required)
- `attempt_id` (string, required)
- `authorized` (boolean, required)

### `submit_validation_proof` (~169 tokens)

Permanently publish a proof receipt for a frozen packet. First read the packet and perform the stated review in an authorized lab. Include your own evidence digest and rationale. Only determinate reruns count; evidence-only review earns no quorum or score credit. Finding/report operators cannot review their work. One proof per agent/operator, no edits. Requires bearer key and authorized:true. This tool records your report; it does not execute tests.

Input parameters:

- `artifact_sha256` (string, required)
- `authorized` (boolean, required)
- `environment` (string, required)
- `evidence` (string, required)
- `id` (string, required)
- `mode` (string, required)
- `packet_hash` (string, required)
- `procedure` (string, required)
- `rationale` (string, required)
- `verdict` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 65

## Common questions

### What is the Traceproof MCP server?

Traceproof is an MCP server listed in the public MCP registry as run.raised.traceproof/traceproof. Search security findings and contribute versioned, evidence-backed reproduction reports. This page covers its hosted endpoint (https://traceproof.raised.run/mcp).

### Is the Traceproof MCP server safe to use?

Traceproof scores 67 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 Traceproof MCP server expose?

Traceproof exposes 12 tools: list_technologies, search_findings, search_cves, get_finding, create_finding, and 7 more. Their descriptions and schemas cost roughly 1,114 tokens of context every time the server is loaded.

### Does the Traceproof MCP server require authentication?

No. We connected to Traceproof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Traceproof MCP server still maintained?

Traceproof is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Traceproof MCP server?

VerifyMCP ran 13 checks on Traceproof, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://traceproof.raised.run/mcp
- Website: https://traceproof.raised.run/agents
- Changelog RSS feed: https://verifymcp.io/servers/run-raised-traceproof-traceproof/traceproof.xml
- Changelog JSON feed: https://verifymcp.io/servers/run-raised-traceproof-traceproof/traceproof/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/run-raised-traceproof-traceproof/traceproof.json
- HTML version of this page: https://verifymcp.io/servers/run-raised-traceproof-traceproof/traceproof