xyz.tenzro/tenzro-ethereum
REMOTE · ETHEREUM-MCP.TENZRO.XYZ · SCANNED AUG 23
Ethereum tools over MCP: Chainlink feeds, ENS, ERC-8004 agents, EAS attestations, transactions.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
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
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
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.
How do I install the xyz.tenzro/tenzro-ethereum MCP server?
xyz.tenzro/tenzro-ethereum is a hosted endpoint at https://ethereum-mcp.tenzro.xyz/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 · ethereum-mcp.tenzro.xyz
claude mcp add --transport http xyz-tenzro-tenzro-ethereum 'https://ethereum-mcp.tenzro.xyz/mcp'
{
"mcpServers": {
"xyz-tenzro-tenzro-ethereum": {
"url": "https://ethereum-mcp.tenzro.xyz/mcp"
}
}
} {
"servers": {
"xyz-tenzro-tenzro-ethereum": {
"type": "http",
"url": "https://ethereum-mcp.tenzro.xyz/mcp"
}
}
} [mcp_servers.xyz-tenzro-tenzro-ethereum] url = "https://ethereum-mcp.tenzro.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-tenzro-tenzro-ethereum": {
"type": "remote",
"url": "https://ethereum-mcp.tenzro.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-tenzro-tenzro-ethereum --url 'https://ethereum-mcp.tenzro.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-tenzro-tenzro-ethereum:
url: "https://ethereum-mcp.tenzro.xyz/mcp" {
"McpServers": {
"xyz-tenzro-tenzro-ethereum": {
"Transport": "http",
"Url": "https://ethereum-mcp.tenzro.xyz/mcp"
}
}
} assistant mcp add xyz-tenzro-tenzro-ethereum -t streamable-http -u 'https://ethereum-mcp.tenzro.xyz/mcp'
{
"mcpServers": {
"xyz-tenzro-tenzro-ethereum": {
"type": "http",
"url": "https://ethereum-mcp.tenzro.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 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
- 9 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.43 → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 8 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 23 Aug 2026 · Probed https://ethereum-mcp.tenzro.xyz/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ethereum-mcp.tenzro.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| tenzro.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ethereum-mcp.tenzro.xyz/mcp | Unreachable | ||
| http (plaintext) | http://ethereum-mcp.tenzro.xyz/mcp | Inconclusive | 404 |
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 →
eth_call_contract ~127
Execute a read-only eth_call against a smart contract. Params: to (contract address), data (hex-encoded calldata), block (default 'latest'). Returns the raw hex result. Use eth_encode_function to build calldata from a function signature and arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string|null | – | Block parameter ('latest', 'earliest', 'pending', or hex block number). Default: 'latest' |
| data | string | yes | Hex-encoded calldata (with or without 0x prefix) |
| to | string | yes | Contract address (hex, with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_encode_function ~195
ABI-encode a function call. Computes the 4-byte selector from the canonical function signature via Keccak-256, then left-pads each argument to 32 bytes. Returns the complete hex-encoded calldata ready for eth_call or a transaction. Example: function_sig='transfer(address,uint256)', args=['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xde0b6b3a7640000'].
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | yes | Arguments as JSON array of hex-encoded values (each will be left-padded to 32 bytes). E.g. ['0xRecipientAddress', '0xde0b6b3a7640000'] |
| function_sig | string | yes | Canonical function signature (e.g. 'transfer(address,uint256)', 'approve(address,uint256)', 'balanceOf(address)') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_estimate_gas ~139
Estimate gas required for a transaction via eth_estimateGas. Params: to (required), from/data/value (optional). Returns estimated gas in decimal and hex.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string|null | – | Hex-encoded calldata (with or without 0x prefix) |
| from | string|null | – | Sender address (hex, with or without 0x prefix) |
| to | string | yes | Recipient/contract address (hex, with or without 0x prefix) |
| value | string|null | – | Value in wei (hex string, e.g. '0xde0b6b3a7640000' for 1 ETH) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_attestation ~87
Query an attestation from Ethereum Attestation Service (EAS) by UID. Posts a GraphQL query to the EAS indexer at easscan.org. Returns attester, recipient, schema, data, timestamp, revocation status, and decoded data when available.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Attestation UID (bytes32 hex, with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_balance ~80
Get the ETH balance of an address via eth_getBalance. Returns balance in wei, Gwei, and ETH.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address (hex, with or without 0x prefix) |
| block | string|null | – | Block parameter ('latest', 'earliest', 'pending', or hex block number). Default: 'latest' |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_block ~113
Get block by number via eth_getBlockByNumber. Params: block_number (hex or 'latest'), full_transactions (bool, default false). Returns block header, transactions, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| block_number | string|null | – | Block number as hex string (e.g. '0x10d4f') or tag ('latest', 'earliest', 'pending'). Default: 'latest' |
| full_transactions | boolean|null | – | If true, return full transaction objects instead of just hashes. Default: false |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_fee_history ~120
Get fee history for recent blocks via eth_feeHistory. Returns base fees per gas, gas used ratios, and reward percentiles for EIP-1559 gas estimation.
| Name | Type | Req | Description |
|---|---|---|---|
| block_count | string|null | – | Number of blocks to return (default '5') |
| newest_block | string|null | – | Newest block ('latest' by default, or hex block number) |
| reward_percentiles | array|null | – | Reward percentiles as JSON array of floats (e.g. [25.0, 50.0, 75.0]) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_gas_price ~42
Get the current gas price from the Ethereum network via eth_gasPrice JSON-RPC. Returns the gas price in wei, Gwei, and hex.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_price ~183
Get token price from a Chainlink AggregatorV3Interface data feed via eth_call to latestRoundData(). Default feed: ETH/USD on mainnet (0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419). Returns price with 8 decimal precision, round ID, and update timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | integer|null | – | Chain ID — 1 for mainnet (default), 8453 for Base, 42161 for Arbitrum. Selects the dRPC chain-specific URL for the feed read. |
| feed_address | string|null | – | Chainlink AggregatorV3Interface data feed address (default: ETH/USD 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_token_balance ~106
Get ERC-20 token balance for an address via eth_call to balanceOf(address). Params: token_address (ERC-20 contract), owner_address. Returns raw balance (caller must divide by 10^decimals for human-readable amount).
| Name | Type | Req | Description |
|---|---|---|---|
| owner_address | string | yes | Owner address to check balance for (hex, with or without 0x prefix) |
| token_address | string | yes | ERC-20 token contract address (hex, with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_transaction ~59
Get transaction details by hash via eth_getTransactionByHash. Returns sender, recipient, value, gas, input data, block number, and nonce.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | Transaction hash (hex, with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_get_transaction_receipt ~73
Get transaction receipt by hash via eth_getTransactionReceipt. Returns status (0x0=failure, 0x1=success), gas used, logs, contract address (if deployment), and block info.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | Transaction hash (hex, with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_lookup_agent_8004 ~95
Look up an AI agent in the ERC-8004 Agent Registry by agent ID (uint256) or owner address. Builds the calldata for getAgent(uint256) or getAgentsByOwner(address) that can be used with eth_call_contract against a deployed ERC-8004 registry.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id_or_address | string | yes | Agent ID (uint256 hex) or owner address (hex) to look up |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_lookup_ens ~75
Reverse-lookup an Ethereum address to its ENS name via the Universal Resolver on-chain. Constructs <address>.addr.reverse and calls resolve(). Falls back to OnchainKit ENS API. Params: address (hex).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address to reverse-lookup (hex, with or without 0x prefix) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_register_agent_8004 ~139
Build transaction data for registering an AI agent via ERC-8004 Agent Registry. ERC-8004 defines an on-chain registry for autonomous AI agents with capabilities, metadata URI, and owner tracking. Returns the ABI-encoded function selector and parameter breakdown for registerAgent(string,string[],string). The caller must sign and submit the transaction to the registry contract.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Human-readable agent name |
| capabilities | array | yes | List of capability strings (e.g. ['nlp', 'code-generation', 'web-search']) |
| metadata_uri | string | yes | IPFS or HTTPS URI pointing to full agent metadata JSON |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_resolve_ens ~113
Resolve an ENS name to an Ethereum address. Tries the ENS Universal Resolver on-chain via eth_call (resolve(bytes,bytes) at 0xc0497E381f536Be9ce14B0dD3817cBcAe57d2F62). Falls back to the OnchainKit ENS API as a secondary source. Params: name (e.g. 'vitalik.eth').
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | ENS name to resolve (e.g. 'vitalik.eth') |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
eth_send_raw_transaction ~132
Broadcast a pre-signed Ethereum transaction via eth_sendRawTransaction. Params: raw_tx (hex-encoded RLP-signed transaction, with or without 0x prefix). Returns the resulting transaction hash as plain text. Use eth_encode_function + eth_estimate_gas + an external signer (or tenzro_signTransaction with chain_id matching the target EVM chain) to build the raw_tx.
| Name | Type | Req | Description |
|---|---|---|---|
| raw_tx | string | yes | Signed RLP-encoded transaction as hex (0x-prefixed). Build with the tenzro_signTransaction helper or any EIP-1559/legacy signer. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | Underlying response payload verbatim. |
No examples provided.
What is the xyz.tenzro/tenzro-ethereum MCP server?
xyz.tenzro/tenzro-ethereum is an MCP server listed in the public MCP registry as xyz.tenzro/tenzro-ethereum. Ethereum tools over MCP: Chainlink feeds, ENS, ERC-8004 agents, EAS attestations, transactions. This page covers its hosted endpoint (https://ethereum-mcp.tenzro.xyz/mcp).
Is the xyz.tenzro/tenzro-ethereum MCP server safe to use?
xyz.tenzro/tenzro-ethereum scores 0 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 xyz.tenzro/tenzro-ethereum MCP server expose?
xyz.tenzro/tenzro-ethereum exposes 17 tools: eth_call_contract, eth_encode_function, eth_estimate_gas, eth_get_attestation, eth_get_balance, and 12 more. Their descriptions and schemas cost roughly 1,878 tokens of context every time the server is loaded.
Does the xyz.tenzro/tenzro-ethereum MCP server require authentication?
Its publisher declares no required credentials for xyz.tenzro/tenzro-ethereum. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the xyz.tenzro/tenzro-ethereum MCP server still maintained?
xyz.tenzro/tenzro-ethereum has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 8 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.