Skip to main content
Glama
swaltersjrtest

MicroTap-MCP

by swaltersjrtest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MicroTap-MCP

  • BlockRun MCP by BlockRunAI

    BlockRun MCPofficial

    BlockRunAI
    A
    license
    A
    quality
    A
    maintenance
    Provides Claude with real-time access to markets, research, X/Twitter, and crypto data via a unified pay-per-call system with no API keys.
    19
    556 npm
    395
    MIT

Related Servers

  • @praveen030686/data-apis-mcp

    yantrix-ai
    A
    license
    A
    quality
    D
    maintenance
    22 MCP tools for AI agents: crypto prices and trading signals (53 coins), stock prices and company financials, forex rates and conversion, and web scraping with AI summaries. All powered by x402 USDC micropayments on Base. $0.01-$0.25 per request.
    22
    19 npm
    MIT

  • StatePulse API

    Ahmed-Achtatar
    A
    license
    Not graded
    quality
    C
    maintenance
    55+ pay-per-call tools for AI agents over MCP: live telemetry, blockchain/on-chain checks, environmental, transit, finance, and network utilities. No API key or signup — agents pay per request with x402 USDC micropayments (Base and Solana).
    MIT

  • agentsvc-mcp

    jakobautomation
    F
    license
    Not graded
    quality
    F
    maintenance
    20 pay-per-call utility tools for AI agents via x402 USDC micropayments on Base. Screenshots, OCR, PDF, web scraping, weather, forex rates, crypto/stock prices, DNS, geocoding, translation, and more. $0.001–$0.008 per call. No API keys, no signup.
    1
    -

  • CorteX402

    Ooak21
    A
    license
    A
    quality
    D
    maintenance
    Pay-per-call x402 data products on Base mainnet — sanctions screening, aviation weather, mortgage rates, US property dossier, title chain, wallet balance, and agent session auth. Every call settles in USDC with an on-chain receipt, no accounts or API keys.
    7
    27 npm
    MIT
Deploy Server
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

TDQS

A3.8/5.0

Scored across 20 tools

Disambiguation4/5

Each tool maps to a fairly distinct data resource or action, with search/get pairs clearly separated by platform. However, get_crypto_price vs get_crypto_market_data and call_multichain_rpc vs get_wallet_balance create a couple of overlapping choices that agents must disambiguate from descriptions.

Naming Consistency4/5

Most tools follow a consistent verb_noun snake_case pattern (get_, search_, generate_, resolve_). The main deviation is web_search, which reverses the verb-first convention used by the other search tools; otherwise naming is predictable.

Tool Count3/5

At 20 tools, the server sits in the 16-25 range that feels heavy for a coherent MCP. The count is not absurd, but the breadth is inflated by mixing weather, text generation, prediction markets, crypto, and chain-infrastructure tools under one server.

Completeness4/5

For a read-only data API aggregator, the major advertised areas are each represented: crypto pricing/market/trends, prediction-market search/detail/divergence, DeFi TVL, onchain balance/gas/ENS/RPC, web search, weather, and text generation. Minor gaps remain, such as historical crypto data or a token-list/discovery endpoint, but intended read-only workflows are not dead ends.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources