Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Tenzro Ethereum MCP

REMOTE · ETHEREUM-MCP.TENZRO.NETWORK · SCANNED AUG 3

Ethereum MCP: Chainlink feeds, gas, ERC-20, ENS, ABI, contract calls, ERC-8004, EAS.

+6 this week 18 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · ethereum-mcp.tenzro.network

# add to Claude Code
claude mcp add --transport http network-tenzro-tenzro-ethereum https://ethereum-mcp.tenzro.network/mcp
# ~/.codex/config.toml
[mcp_servers.network-tenzro-tenzro-ethereum]
url = "https://ethereum-mcp.tenzro.network/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "network-tenzro-tenzro-ethereum": {
      "type": "remote",
      "url": "https://ethereum-mcp.tenzro.network/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add network-tenzro-tenzro-ethereum --url https://ethereum-mcp.tenzro.network/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  network-tenzro-tenzro-ethereum:
    url: "https://ethereum-mcp.tenzro.network/mcp"
// mcp.json
{
  "mcpServers": {
    "network-tenzro-tenzro-ethereum": {
      "type": "http",
      "url": "https://ethereum-mcp.tenzro.network/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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 Aug 26 +18
    • HSTS header: unverified → fail security
    • TLS certificate: unverified → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 405. security
  • 2 Aug 26 −18
    • HSTS header: fail → unverified security
    • TLS certificate: pass → unverified security
    • Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
  • 31 Jul 26 +6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 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
  • 27 Jul 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 Jul 26 12

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://ethereum-mcp.tenzro.network/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ethereum-mcp.tenzro.network CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US 11 Jul 2026 8 Oct 2026 RSA 2048 SHA256-RSA 472b300e343b86d3e79905d209461bb
SANs: ethereum-mcp.tenzro.network
CN=Encryption Everywhere DV TLS CA - G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 27 Nov 2017 27 Nov 2027 RSA 2048 SHA256-RSA de0ffb5ee62cb61109f608c9ced5ed3
DNSSEC insecure

Validation of ethereum-mcp.tenzro.network. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
network. present 40414 8 Verified
tenzro.network. 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 405
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ethereum-mcp.tenzro.network/mcp HTTP error 405
http (plaintext) http://ethereum-mcp.tenzro.network/mcp Served over HTTP 200
MCP tools

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.

No tool schema has been captured from this endpoint yet.