Skip to main content
Glama
RipperMercs

TensorFeed MCP Server

by RipperMercs

Related Servers

Alternatives to TensorFeed MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Real-time AI industry intelligence MCP server. 6 free tools (news, status, pricing, today summary, agent activity, MCP registry snapshot) plus 13 paid tools (routing, news search, history series, cost projection, deep-dive, comparison, webhook watches). Pay-per-call in USDC on Base, no accounts.
      25
      6 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with real-time, structured data feeds including news, trends, market sentiment, and crypto prices via MCP tools.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server enabling AI agents to access crypto and web3 data via pay-per-call on the MPP/Tempo rail (USDC.e). It includes unique tools like Vietnamese crypto news and company registry lookup, with built-in spend caps and no API key needed.
      26
      18 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      56 pay-per-call MCP endpoints for AI agents. Market signals, macro economics, crypto/DeFi, geopolitical intelligence, SEC filings, GitHub velocity, sanctions screening. USDC on Base Mainnet via x402.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.
      1 npm
      MIT

    TDQS

    A4/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, like account_status for credit balance, benchmark_series for historical scores, and route_verdict for model routing. However, get_ai_status and is_service_down both check provider status, though with different depth, causing slight ambiguity.

    Naming Consistency2/5

    Tool names follow no consistent pattern: some use snake_case (account_status), some verb_noun (get_ai_news), some noun_verb (is_service_down), and some are compound names (failover_verdict, provider_deepdive). This variety reduces predictability.

    Tool Count4/5

    With 24 tools, the server covers a wide domain of AI ecosystem data and verdicts. The count is high but justified by the breadth of functionality; it is not excessive given the scope.

    Completeness5/5

    The tool set comprehensively covers pricing, status, benchmarks, various verdicts, news, webhooks, SSVC, stack safety, and x402 settlements. No obvious missing operations for the server's purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive