Is the Jdhart81 Agent Erc8004 Bridge MCP server down?

mcp-registry/io.github.jdhart81/agent-erc8004-bridge · v1.28.1

As of 2026-10-21 20:52 UTC, the Jdhart81 Agent Erc8004 Bridge MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 7 minutes.

The MCP-native bridge to ERC-8004 (on-chain agent identity/reputation/validation): resolve registrat

claude mcp add --transport http jdhart81-agent-erc8004-bridge-mcp-server https://mcp.viridisconservation.com/erc8004/mcp

{
  "mcpServers": {
    "jdhart81-agent-erc8004-bridge-mcp-server": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/erc8004/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

What to fix (2)

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jdhart81%2Fagent-erc8004-bridge/fixes

{
  "name": "describe_agent",
  "description": "Return the bridge's capabilities and input contract.",
  "inputSchema": {
    "type": "object",
    "title": "describe_agentArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "export_attestation",
  "description": "Export the agent's current trust score as an UNSIGNED\n    ERC-8004 Validation Registry-shaped payload, content-addressed and ready\n    for YOUR OWN signer to anchor on-chain.",
  "inputSchema": {
    "type": "object",
    "title": "export_attestationArguments",
    "required": [
      "chain_id",
      "token_id"
    ],
    "properties": {
      "chain_id": {
        "type": "integer",
        "title": "Chain Id"
      },
      "token_id": {
        "type": "integer",
        "title": "Token Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "export_validation_response",
  "description": "Build UNSIGNED ERC-8004 Validation Registry validationResponse args\n    from an Outcome Receipt (ORC v0.1): responseHash = receipt commitment,\n    tag \"orc/0.1\", response 100 only if the bridge re-verifies the receipt\n    AND your replay succeeded. Sign and submit with your own signer; this\n    bridge holds no keys and writes to no chain.",
  "inputSchema": {
    "type": "object",
    "title": "export_validation_responseArguments",
    "required": [
      "receipt",
      "request_hash",
      "response_uri",
      "replay_ok"
    ],
    "properties": {
      "receipt": {
        "type": "object",
        "title": "Receipt",
        "additionalProperties": true
      },
      "replay_ok": {
        "type": "boolean",
        "title": "Replay Ok"
      },
      "request_hash": {
        "type": "string",
        "title": "Request Hash"
      },
      "response_uri": {
        "type": "string",
        "title": "Response Uri"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jdhart81/agent-erc8004-bridge"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jdhart81/agent-erc8004-bridge"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,314 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.90% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• export_validation_response ~221 tokens
• import_registration ~208 tokens
• score_agent ~158 tokens
• import_feedback ~154 tokens
• bind_identity ~142 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-erc8004-bridge.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-erc8004-bridge?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-erc8004-bridge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-erc8004-bridge.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-erc8004-bridge.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-erc8004-bridge?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1ca50a9dd3d09f90…, first seen 2026-10-17, included at leaf 14546 of 41,603. Version history · verify what your client received.

Tools (15)

• bind_identity
• calculate_inventory
• calculate_takeoff
• calculate_tax_credit
• compile_disclosure
• describe_agent
• export_attestation
• export_validation_response
• import_feedback
• import_registration
• list_registrations
• resolve_agent
• scan_regulations
• score_agent
• verify_attestation

Compare: most reliable other servers · most reliable data servers · most reliable finance servers · most reliable knowledge servers · most reliable blockchain servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Jdhart81 Agent Erc8004 Bridge MCP server down right now?

As of 2026-10-21 20:52 UTC, the Jdhart81 Agent Erc8004 Bridge MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Jdhart81 Agent Erc8004 Bridge MCP server provide?

Jdhart81 Agent Erc8004 Bridge MCP server advertises 15 tools, including bind_identity, calculate_inventory, calculate_takeoff, calculate_tax_credit, compile_disclosure.

How do I install Jdhart81 Agent Erc8004 Bridge MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.viridisconservation.com/erc8004/mcp

Is the Jdhart81 Agent Erc8004 Bridge MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Jdhart81 Agent Erc8004 Bridge MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.