AurAgrid
OfficialRelated Servers
Alternatives to AurAgrid
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceBitcoin data for AI agents. Pay-per-query via x402 micropayments. No API keys. No subscriptions. No tokens.MIT

btcmatic-mcp-serverofficial
AlicenseAqualityDmaintenanceMCP server that gives autonomous agents pay-per-call Bitcoin context (self-custody radar, fee percentiles, price change windows, condition frequencies) paid in sats over Lightning via L402 invoices, with no account or API key required.7MIT- AlicenseAqualityCmaintenanceLive and historical electricity prices, demand, generation mix and carbon intensity for 25 grid zones (US, Europe, GB, Australia). Hosted endpoint plus local stdio bridge; free sample mode, free API key, or x402 pay-per-call.6MIT
- AlicenseBqualityDmaintenanceProvides live Bitcoin network data (fees, mempool, hashrate) and AI-powered price/fee forecasts via MCP tools, with free access to basic data and pay-per-call for advanced features.1782 npmMIT
- AlicenseAqualityBmaintenanceEight crypto and DeFi data tools for AI agents: prices, gas, one ParaSwap route quote, GoPlus token security and top-holder samples, DefiLlama yields, Hyperliquid/dYdX funding, and observed wallet balances. Inspect prices free; pay 0.001–0.008 USDC per call on Base through x402. No API key or subscription.887 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables querying public Bitcoin network data including fees, mempool status, hashrate, transactions, address stats, and Lightning network information without requiring API keys.MIT
TDQS
Scored across 4 tools
Each tool maps to a distinct step in the feed lifecycle: browse (list_feeds), preview (get_sample), price-check (get_quote), and retrieve/purchase (fetch). The only mild overlap is get_quote versus list_feeds, which already reports prices, and get_sample versus fetch for free feeds, but descriptions make the free/paid boundary clear.
Three of four tools follow a verb_noun snake_case pattern (list_feeds, get_sample, get_quote), with 'fetch' as a bare verb that deviates slightly. The convention is still predictable and readable across the set.
Four tools is a tight, well-scoped surface for a feed marketplace: catalog, sample, quote, and paid fetch each earn their place with no redundancy. Nothing in the described purpose suggests a missing tool or an excess one.
The surface covers discovery, preview, pricing, and L402 purchase end-to-end, which is the core lifecycle. Minor gaps exist around budget/account status inspection and purchase history, but fetch's cap/budget behavior implies that context is configured rather than queried.