Skip to main content
Glama
jblaz6335

AI Data Marketplace

by jblaz6335
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to AI Data Marketplace

No user-submitted related servers found.

    Related Servers

    • JMT x402 MCP Server

      jmthomasofficial
      A
      license
      B
      quality
      D
      maintenance
      Exposes 25 paid API endpoints as MCP tools for AI agents, with payments in USDC on Base mainnet via the x402 protocol, enabling tasks like web search, company intelligence, and crypto research.
      25
      65 npm
      MIT

    • 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
      35 npm
      MIT

    • Omni Service Node

      Luckkyyy23
      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.
      -

    • AlphaPipeline

      parkyucheol-del
      A
      license
      A
      quality
      A
      maintenance
      Pay-per-call ($0.005–$0.03 USDC) market, on-chain, and prediction-market data API for AI agents and trading bots via the x402 protocol — no signup, no API key. Exposed as a remote MCP server with 16 tools: pre-trade token security (honeypot/liquidity checks), kimchi premium, funding rate APR, DEX slippage, Polymarket arbitrage & liquidity audits, and Hyperliquid HIP-4 prediction-market odds.
      4
      16
      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

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one for discovery/search and one for purchasing. No overlap or confusion.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern ('find_marketplace_products' and 'purchase_marketplace_product'), with only a minor plural/singular difference that is contextually appropriate.

    Tool Count3/5

    With only two tools, the set feels minimal for a marketplace. While it covers the core discovery and purchase flow, it may be slightly thin for a full-featured marketplace, but it is not unreasonably sparse.

    Completeness3/5

    The tools cover the basic buyer journey (find and purchase), but lack other expected marketplace operations such as viewing product details, managing orders, or handling refunds. This leaves notable gaps for a complete marketplace experience.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources