Skip to main content

Tenzro Ethereum MCP

by network.tenzro

Overview Discussions Admin

Server Details

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

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-13 06:49
Transport: Streamable HTTP
URL
Repository: tenzro/tenzro-network
GitHub Stars: 0

TDQS

A4.1/5.0

Scored 2026-06-13 15:55 across 17 tools

Disambiguation5/5

Each tool targets a distinct Ethereum operation: contract calls, ABI encoding, gas estimation, ENS resolution, EAS attestations, ERC-8004 agent registry, transaction broadcasting, and various queries (balance, block, fee history, gas price, token price, token balance, transaction details). No two tools have overlapping purposes, ensuring an agent can clearly select the correct tool for a given task.

Naming Consistency5/5

All tools follow the consistent 'eth_<verb>_<noun>' pattern, using descriptive verbs like 'call', 'encode', 'estimate', 'get', 'lookup', 'register', 'resolve', and 'send'. The naming is uniform, predictable, and uses snake_case throughout, with no mixing of conventions.

Tool Count5/5

With 17 tools, the set is well-scoped for an Ethereum MCP server. It covers essential operations for reading blockchain state, interacting with contracts, resolving ENS, querying token prices, managing attestations and agent registries, and sending transactions. The number is neither excessive nor sparse for the domain.

Completeness4/5

The tool surface is comprehensive, covering most common Ethereum interactions: basic queries, contract data encoding, gas estimation, ENS, price feeds, token balances, transaction handling, and even specialized features like EAS and ERC-8004. However, missing tools for logs (eth_getLogs) and chain metadata (eth_chainId) are minor gaps that agents might need to work around.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

17 tool updatesMay 16, 2026

Changedeth_call_contract1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_encode_function1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_estimate_gas1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_attestation1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_balance1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_block1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_fee_history1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_gas_price1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_price1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_token_balance1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_transaction1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_get_transaction_receipt1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_lookup_agent_80041 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_lookup_ens1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_register_agent_80041 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_resolve_ens1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

Changedeth_send_raw_transaction1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}

2 tool updatesMay 6, 2026

Changedeth_get_price1 field changed

changedInput schema / properties / chain_id / description

Previous value: -"Chain ID — 1 for mainnet (default), used to select RPC endpoint"New value: +"Chain ID — 1 for mainnet (default), 8453 for Base, 42161 for Arbitrum. Selects the dRPC chain-specific URL for the feed read."

Addedeth_send_raw_transaction

16 tool updatesMay 2, 2026
- First observedeth_call_contract
- First observedeth_encode_function
- First observedeth_estimate_gas
- First observedeth_get_attestation
- First observedeth_get_balance
- First observedeth_get_block
- First observedeth_get_fee_history
- First observedeth_get_gas_price
- First observedeth_get_price
- First observedeth_get_token_balance
- First observedeth_get_transaction
- First observedeth_get_transaction_receipt
- First observedeth_lookup_agent_8004
- First observedeth_lookup_ens
- First observedeth_register_agent_8004
- First observedeth_resolve_ens

Related MCP Connectors

tenzro-ethereum A
xyz.tenzro
Ethereum tools over MCP: Chainlink feeds, ENS, ERC-8004 agents, EAS attestations, transactions.
Blockchain Web3 & Decentralized Tech
2
tenzro-chainlink A
xyz.tenzro
Chainlink tools over MCP: CCIP cross-chain, data feeds, data streams, VRF, proof of reserve.
Blockchain Web3 & Decentralized Tech
2
Alchemy Eth C
io.github.pipeworx-io
Alchemy (Ethereum + L2) MCP.
Blockchain Cryptocurrency Web3 & Decentralized Tech
402
Ens A
io.github.pipeworx-io
ENS (Ethereum Name Service) MCP.
Blockchain Web3 & Decentralized Tech
332

Related MCP Servers

mcp-alchemy-eth
Blockchain Cryptocurrency Web3 & Decentralized Tech
pipeworx-io
A
license
Not graded
quality
C
maintenance
Provides Ethereum and L2 data access via Alchemy API, enabling token balances, NFTs, transfers, and generic RPC calls through MCP.
Updated 18 days ago (2026-08-26 16:32 UTC)
MIT
etherscan-mcp-server
Blockchain Cryptocurrency Web3 & Decentralized Tech
friendlygeorge
A
license
A
quality
F
maintenance
Provides MCP tools to query Etherscan for Ethereum blockchain data—ETH balances, ERC-20 tokens, transactions, contract ABIs, and gas prices—without requiring an API key.
Updated 3 months ago (2026-06-11 17:10 UTC)
8
7 npm
MIT
mcp-etherscan
Blockchain Cryptocurrency Web3 & Decentralized Tech
pipeworx-io
A
license
Not graded
quality
C
maintenance
Provides multichain block-explorer data from Etherscan via MCP tools for token balances, contract ABI, and source code.
Updated 18 days ago (2026-08-26 17:04 UTC)
6 npm
MIT
x402 On-Chain Data MCP Server
Blockchain Cryptocurrency Web3 & Decentralized Tech
0xEtherial
F
license
A
quality
D
maintenance
Pay-per-call MCP server for on-chain blockchain data including wallet profiles, token metrics, protocol TVL, and gas prices.
Updated 6 months ago (2026-03-03 17:59 UTC)
5
-

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources