fabtally-chain-mcp
Related Servers
Alternatives to fabtally-chain-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server that gives agents read-only access to Ethereum public data scraped from etherscan.io with no API key, covering first funder, address metadata, ERC20 holdings, token holder lists, transaction history and transaction details. It also answers standard Ethereum JSON-RPC calls such as eth_getBalance, eth_call, eth_getTransactionReceipt and block lookups, and supports batched NDJSON requests with resumable streaming results.MIT
- AlicenseAqualityCmaintenanceA read-only MCP server that queries multichain EVM on-chain data through Blockscout REST API, providing tools for address info, transactions, logs, and more.165 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for monitoring Flare's interoperable asset ecosystem, providing real-time on-chain data for FAssets, FTSOv2 prices, and bridge states. It exposes 8 MCP tools for anomaly detection, risk scoring, and automated alerts.-

Dataline MCP Serverofficial
AlicenseAqualityDmaintenanceMCP server exposing read-only market data tools for crypto prices, funding rates, and prediction markets via Dataline API.812 npmMIT- AlicenseAqualityDmaintenancePay-per-call MCP server for on-chain blockchain data including wallet profiles, token metrics, protocol TVL, and gas prices.5MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server that monitors a Bitcoin Core full node via JSON-RPC, providing tools to check node status, network info, mempool, and peer information.MIT
TDQS
Scored across 4 tools
Each tool targets a completely distinct data domain: ENS registrations, gas fees, token unlocks, and oracle health. There is no overlap in purpose or arguments, so an agent can unambiguously select the right tool.
All tool names are lowercase snake_case and clearly descriptive (ens_expiry, gas, token_unlocks, oracle_health). They are consistent in style, though they are noun phrases rather than a verb_noun pattern, so the naming is predictable but not strictly uniform.
With 4 tools, the server is well-scoped for a focused blockchain data query service. Each tool is distinct and earns its place, and the count falls comfortably within the recommended range.
The tool surface covers a reasonable set of read-only blockchain data queries, but some common endpoints like block details or transaction status are missing. However, the included tools are each self-contained, and the gaps are not likely to cause significant failures for the intended use case.