"Writing about MCP" matching MCP servers:

About An MCP server that resolves, analyzes, and contextualizes ENS domain activity.

mcp server that allows to do actual actions related to solana first version adds knowledge about RPC methods and how to call them

Teaches AI coding agents how to reason correctly about MetaMask Embedded Wallets / Web3Auth architecture, SDK choice, key derivation, auth flows, and common integration pitfalls.

Provides coding agents with accurate, sourced facts about the Horizen chain, including chain IDs, RPC URLs, contract addresses, oracle feeds, bridge info, and integration details, so they stop guessing.

Enables AI assistants and agents to perform read-only lookups of dated on-record facts about agents, wallets, and endpoints, including evidence levels and history, so they can assess what is known before paying or relying on them.

Provides curated, meaningful information about Voi ecosystem protocols, applications, assets, and names, enabling identification and search through natural language.

An MCP server that provides a semantic layer for the Voi ecosystem, translating raw blockchain data into human-readable information about protocols, applications, and assets. It enables users to identify contract roles, resolve enVoi names, and explore curated registry data for ecosystem services like HumbleSwap and Nautilus.

Exposes real-time Hyperliquid explorer and analytics data from flowscan.xyz as 44 read-only tools, letting AI agents answer questions about protocol revenue, perp market positioning, individual open positions, wallet activity, and staking without an API key. It runs over stdio against Hyperliquid mainnet only, using the same API routes the Flowscan frontend calls.

Connects AI agents to Real World Asset (RWA) data, enabling queries about tokenized assets, market trends, TVL analytics, token holders, and portfolio tracking across multiple blockchains.

An MCP server providing AI-native access to XGR blockchain data, enabling queries about chain status, sessions, transactions, and contracts, as well as preparing owner-signed on-chain actions via natural language.

An MCP server that provides tools for interacting with EDUCHAIN, allowing Claude to query information about tokens and pools and perform swaps through SailFish DEX.

Enables AI agents to query real-time spatial perception from DePIN edge-vision nodes, retrieving structured JSON about detected objects, bounding boxes, confidence scores, environmental state, and geolocation through the Model Context Protocol.

This MCP server enables agents to fetch and reason about ERC-20 token metadata, balances, and allowances across multiple chains without hardcoding addresses or ABIs.

Enables agents and command-line users to query pump.fun's full on-chain trade history, including pre-buy checks on a token's deployer, bundle and insiders, wallet classification and ranking, deployer records, and market-cap base rates. Results come back as structured JSON so an agent can answer questions about launches and wallets from recorded data rather than guesses.

Enables agent frameworks to query live protocol state and build unsigned BNB Chain transactions for minting, hatching, feeding, evolving, listing, buying, and claiming without writing RPC code or handling private keys.

Provides real-time information about Ethereum addresses across multiple chains using the Model Context Protocol, featuring a Server-Sent Events endpoint for live updates.

Enables local AI clients such as Claude Code and Cursor to search, analyze, and monitor prediction-market data, and, once live mode is explicitly switched on, sign and submit CLOB orders from the operator's own wallet. It runs in a safe preview mode by default, writing simulated trades to local SQLite instead of sending orders.

Enables AI agents to generate and persist a self-sovereign did:key identity, sign claims about their actions as Ed25519 attestations, verify those attestations offline without any registry or network access, and compute an auditable reputation score from a ledger of events. All four operations are exposed as MCP tools so an agent can manage its own identity and prove its history during a session.