io.github.jdhart81/agent-erc8004-bridge
REMOTE · MCP.VIRIDISCONSERVATION.COM
The MCP-native bridge to ERC-8004 (on-chain agent identity/reputation/validation): resolve registrat
Available components
Last scanned (7 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 702 tokens (~70/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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
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.
- 3 Nov 26 0
- Tool “bind_identity” changed its title: Bind identity cosmetic
- Tool “describe_agent” changed its title: Describe this service cosmetic
- Tool “export_attestation” changed its title: Export attestation cosmetic
- Tool “export_validation_response” changed its title: Export validation response cosmetic
- Tool “import_feedback” changed its title: Import feedback cosmetic
- Tool “import_registration” changed its title: Import registration cosmetic
- Tool “list_registrations” changed its title: List registrations cosmetic
- Tool “resolve_agent” changed its title: Resolve agent cosmetic
- Tool “score_agent” changed its title: Score agent cosmetic
- Tool “verify_attestation” changed its title: Verify attestation cosmetic
10 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 Oct 26 +6
- Authorization: unverified → partial ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Schema quality: 581 → 702 ▼ functional
- New tool “export_validation_response” functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcp.viridisconservation.com/erc8004/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.viridisconservation.com | CN=YE1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5abb43a3acf241ca07b1eb9ff25cafac4e4 |
| SANs: mcp.viridisconservation.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 mcp.viridisconservation.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| viridisconservation.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.viridisconservation.com/erc8004/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.viridisconservation.com/erc8004/mcp | HTTPS enforced | 308 | https://mcp.viridisconservation.com/erc8004/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 →
bind_identity Bind identity ~70
Bind a fleet DID to an ERC-8004 identity. Produces an order-independent, content-addressed (unsigned) binding attestation.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | integer | yes | – |
| fleet_did | string | yes | – |
| proof_note | string | – | – |
| token_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
describe_agent Describe this service ~17
Return the bridge's capabilities and input contract.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_attestation Export attestation ~63
Export the agent's current trust score as an UNSIGNED ERC-8004 Validation Registry-shaped payload, content-addressed and ready for YOUR OWN signer to anchor on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | integer | yes | – |
| token_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_validation_response Export validation response ~121
Build UNSIGNED ERC-8004 Validation Registry validationResponse args from an Outcome Receipt (ORC v0.1): responseHash = receipt commitment, tag "orc/0.1", response 100 only if the bridge re-verifies the receipt AND your replay succeeded. Sign and submit with your own signer; this bridge holds no keys and writes to no chain.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | – |
| replay_ok | boolean | yes | – |
| request_hash | string | yes | – |
| response_uri | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
import_feedback Import feedback ~80
Import ERC-8004 Reputation Registry feedback records for an agent. Each item: {value: bool|0..1, at: ISO-8601, source?, weight?, feedback_id?}. Idempotent per feedback_id.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | integer | yes | – |
| feedback | array | yes | – |
| token_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
import_registration Import registration ~108
Import an ERC-8004 Identity Registry record (chain_id + ERC-721 token_id + agentURI + owner). Idempotent: re-import updates in place. Returns the canonical record with its deterministic bridge DID (did:viridis:erc8004:<chain>:<token>).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_uri | string | yes | – |
| chain_id | integer | yes | – |
| metadata | – | – | – |
| owner | string | yes | – |
| token_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_registrations List registrations ~19
List all imported ERC-8004 registrations.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_agent Resolve agent ~51
Resolve an imported ERC-8004 registration by bridge DID or by (chain_id, token_id).
| Name | Type | Req | Description |
|---|---|---|---|
| bridge_did | string | – | – |
| chain_id | – | – | – |
| token_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
score_agent Score agent ~83
Decay-weighted trust score in [0,1] + tier over the agent's imported ERC-8004 feedback — recent behavior outweighs old; no feedback scores a neutral 0.5 prior (no blind trust, no unfair zero).
| Name | Type | Req | Description |
|---|---|---|---|
| bridge_did | string | – | – |
| chain_id | – | – | – |
| token_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_attestation Verify attestation ~30
Recompute a payload's content hash and report whether it is intact.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.jdhart81/agent-erc8004-bridge MCP server?
io.github.jdhart81/agent-erc8004-bridge is a hosted endpoint at https://mcp.viridisconservation.com/erc8004/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 · mcp.viridisconservation.com
claude mcp add --transport http jdhart81-agent-erc8004-bridge 'https://mcp.viridisconservation.com/erc8004/mcp'
What is the io.github.jdhart81/agent-erc8004-bridge MCP server?
io.github.jdhart81/agent-erc8004-bridge is an MCP server listed in the public MCP registry as io.github.jdhart81/agent-erc8004-bridge. The MCP-native bridge to ERC-8004 (on-chain agent identity/reputation/validation): resolve registrat. This page covers its hosted endpoint (https://mcp.viridisconservation.com/erc8004/mcp).
Is the io.github.jdhart81/agent-erc8004-bridge MCP server safe to use?
io.github.jdhart81/agent-erc8004-bridge scores 81 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 io.github.jdhart81/agent-erc8004-bridge MCP server expose?
io.github.jdhart81/agent-erc8004-bridge exposes 10 tools: import_registration, resolve_agent, import_feedback, score_agent, bind_identity, and 5 more. Their descriptions and schemas cost roughly 642 tokens of context every time the server is loaded.
Does the io.github.jdhart81/agent-erc8004-bridge MCP server require authentication?
No. We connected to io.github.jdhart81/agent-erc8004-bridge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jdhart81/agent-erc8004-bridge MCP server still maintained?
io.github.jdhart81/agent-erc8004-bridge 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.