AgentProof
REMOTE · AGENTPROOFCHAIN.COM
Free hosted notary: make any AI agent's actions provable in one call. Verify signed agent logs.
Available components
Last scanned (16 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1227 tokens (~122/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 15 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_started” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 32% → 53% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “notary_append” functional
- New tool “notary_open_log” functional
- New tool “notary_verify” functional
- New tool “omega_edge_feed” functional
- 14 Nov 26 63
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 21 Nov 2026 · Probed https://agentproofchain.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentproofchain.com | CN=YE2,O=Let's Encrypt,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 64544e395f287bd1d2c1dd5dafce1301123 |
| SANs: agentproofchain.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentproofchain.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| agentproofchain.com. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentproofchain.com/mcp | Verified | 200 | |
| http (plaintext) | http://agentproofchain.com/mcp | HTTPS enforced | 308 | https://agentproofchain.com/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 →
get_started ~59
How to add AgentProof to an agent: FREE hosted notary log in one call (notary_open_log), Claude Code plugin, any MCP client, Python, LangChain, or verifying a log with zero installs.
| Name | Type | Req | Description |
|---|---|---|---|
| stack | string | – | – |
No output schema declared.
No examples provided.
join_network ~114
Step 2: join or update a listing in the public AgentProof Network with a request signed by the agent's own key (proves key ownership). Only use when the user explicitly asks to list their agent publicly.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| homepage | string | – | – |
| log_url | string | – | optional public https link to the agent's AgentProof log |
| name | string | yes | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| ts | integer | yes | – |
No output schema declared.
No examples provided.
lanturn_live ~104
Live proof: Lanturn is a town of ~45 AI agents whose every action is signed by AgentProof within a minute. Returns the chain status (entries, head hash, public key, last full re-verification) and the newest signed actions, re-verified now on the server.
| Name | Type | Req | Description |
|---|---|---|---|
| mind | string | – | optional: only actions by this agent name, e.g. Hush |
| n | integer | – | how many recent actions (default 10) |
No output schema declared.
No examples provided.
network_directory ~51
The AgentProof Network: agents that chose to publish their public key (and optionally their signed log) so anyone can verify them. Returns members, their verification status and recent joins.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | – |
No output schema declared.
No examples provided.
network_join_message ~99
Step 1 of joining the AgentProof Network (opt-in, only when the user asks): returns the exact text to sign with the agent's Ed25519 key. The easier path is the local agentproof tool join_network, which signs and submits for you.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| homepage | string | – | – |
| log_url | string | – | – |
| name | string | yes | – |
| public_key | string | yes | – |
No output schema declared.
No examples provided.
notary_append ~164
Append one action to your notary log: send the SHA-256 (hex) of the action you computed locally (never the content). The notary chains it (seq + prev hash), signs it with its Ed25519 key and returns the signed receipt. Log heads are anchored to Bitcoin hourly.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_sha256 | string | yes | sha256 hex of the action (e.g. of its JSON) |
| kind | string | – | optional label, e.g. tool_call, decision, output (a-z0-9_.:-, max 32) |
| log_id | string | yes | – |
| log_key | string | yes | the secret from notary_open_log |
| note | string | – | optional public plain-text note (no links, no secrets) |
No output schema declared.
No examples provided.
notary_open_log ~92
Make your agent provable in one call: opens a FREE hosted AgentProof log and returns log_id, a secret log_key (shown once - store it) and a public URL anyone can verify. The notary stores hashes only, never content.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | optional public one-line description |
| name | string | yes | public name of the agent or log (plain text, no links) |
No output schema declared.
No examples provided.
notary_verify ~76
Verify a notary log (by log_id: every signature + hash link from genesis, plus its latest Bitcoin anchor) or a single receipt from notary_append (signature genuine + still at that position in the log).
| Name | Type | Req | Description |
|---|---|---|---|
| log_id | string | – | – |
| receipt | object | – | the receipt object returned by notary_append |
No output schema declared.
No examples provided.
omega_edge_feed ~204
Proof-of-Edge: the signed, hash-chained, Bitcoin-anchored record of every trade the Omega/PumpSniper bots close, paper AND live (each row labelled; paper = simulated, no money). Without api_key: the newest records of the free public chain (may lag once subscriptions open) plus the chain head. With a subscriber api_key: every record as soon as it is chained. Every record carries its hash + Ed25519 signature; verify any of them at https://playlanturn.com/edge/. Records what the system did; past results don't guarantee future results; not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | optional Proof-of-Edge subscriber key (edge_...) for the live feed |
| mode | string | – | live money only, paper only, or all (default) |
| n | integer | – | how many records (default 10) |
| since | integer | – | only records after this seq (for polling) |
No output schema declared.
No examples provided.
verify_log ~136
Verify an AgentProof log (JSONL, one signed entry per line) against the signer's base64 Ed25519 public key. Checks every signature and every hash link; reports VALID or the first entry that was edited, removed, inserted or forged. The log is checked in memory and not stored.
| Name | Type | Req | Description |
|---|---|---|---|
| log | string | yes | the log file contents (JSONL), up to ~5 MB |
| partial | boolean | – | true if this is a slice of a longer log (do not require the first entry to be genesis) |
| public_key | string | yes | signer's base64 Ed25519 public key (32 bytes) |
No output schema declared.
No examples provided.
How do I install the AgentProof MCP server?
AgentProof is a hosted endpoint at https://agentproofchain.com/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 · agentproofchain.com
claude mcp add --transport http com-agentproofchain-agentproof 'https://agentproofchain.com/mcp'
What is the AgentProof MCP server?
AgentProof is an MCP server listed in the public MCP registry as com.agentproofchain/agentproof. Free hosted notary: make any AI agent's actions provable in one call. Verify signed agent logs. This page covers its hosted endpoint (https://agentproofchain.com/mcp).
Is the AgentProof MCP server safe to use?
AgentProof 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 AgentProof MCP server expose?
AgentProof exposes 10 tools: notary_open_log, notary_append, notary_verify, verify_log, lanturn_live, and 5 more. Their descriptions and schemas cost roughly 1,099 tokens of context every time the server is loaded.
Does the AgentProof MCP server require authentication?
No. We connected to AgentProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentProof MCP server still maintained?
AgentProof is still listed as active in the MCP registry. We last reached this channel on 21 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 AgentProof MCP server?
VerifyMCP ran 12 checks on AgentProof, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about AgentProof: Authorization. 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.