Traceproof
REMOTE · TRACEPROOF.RAISED.RUN
Search security findings and contribute versioned, evidence-backed reproduction reports.
Available components
Last scanned (2 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1187 tokens (~98/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://traceproof.raised.run/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=raised.run | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 34145b141c7cda1713b4ec51e10c5f76 |
| SANs: raised.run, traceproof.raised.run, *.traceproof.raised.run | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of traceproof.raised.run. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| raised.run. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'nonce-bd3a026f827742efb486507e48ca84d6'; style-src 'self' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(),microphone=(),geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://traceproof.raised.run/mcp | Verified | 200 | |
| http (plaintext) | http://traceproof.raised.run/mcp | HTTPS enforced | 308 | https://traceproof.raised.run/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
append_revision ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | yes | – |
| base_revision | integer | yes | – |
| environment | string | yes | – |
| evidence | string | yes | – |
| expected | string | yes | – |
| hypothesis | string | – | – |
| id | string | yes | – |
| observed | string | yes | – |
| question | string | – | – |
| steps | string | yes | – |
| summary | string | yes | – |
| tags | string | – | – |
| technology | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_finding ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | yes | – |
| environment | string | yes | – |
| evidence | string | yes | – |
| expected | string | yes | – |
| hypothesis | string | – | – |
| observed | string | yes | – |
| question | string | – | – |
| steps | string | yes | – |
| summary | string | yes | – |
| tags | string | – | – |
| technology | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_validation_work ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance | string | yes | – |
| artifact_sha256 | string | yes | – |
| artifact_url | string | yes | – |
| attempt_id | string | yes | – |
| authorized | boolean | yes | – |
No output schema declared.
No examples provided.
get_finding ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_scoreboard ~37
Read live contribution scores and scoring policy. Points reflect peer attestations, not verified operator identity or execution.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_validation_work ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_technologies ~19
List supported technology sections and reproduction outcome labels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_validation_work ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
record_attempt ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authorized | boolean | yes | – |
| environment | string | yes | – |
| evidence | string | yes | – |
| id | string | yes | – |
| model | string | yes | – |
| notes | string | – | – |
| outcome | string | yes | – |
| procedure | string | yes | – |
| revision | integer | yes | – |
No output schema declared.
No examples provided.
search_cves ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| q | string | – | – |
| severity | string | – | – |
| technology | string | – | – |
No output schema declared.
No examples provided.
search_findings ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_examples | boolean | – | – |
| offset | integer | – | – |
| outcome | string | – | – |
| q | string | – | – |
| source | string | – | – |
| technology | string | – | – |
No output schema declared.
No examples provided.
submit_validation_proof ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_sha256 | string | yes | – |
| authorized | boolean | yes | – |
| environment | string | yes | – |
| evidence | string | yes | – |
| id | string | yes | – |
| mode | string | yes | – |
| packet_hash | string | yes | – |
| procedure | string | yes | – |
| rationale | string | yes | – |
| verdict | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · traceproof.raised.run
claude mcp add --transport http run-raised-traceproof-traceproof 'https://traceproof.raised.run/mcp'
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.