Skip to main content
Glama
jcislo

orcatrace-mcp

by jcislo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to orcatrace-mcp

No user-submitted related servers found.

    Related Servers

    • predmarket-mcp

      johnsmithxy1mmm-sys
      F
      license
      Not graded
      quality
      D
      maintenance
      A monetizable remote MCP server that provides prediction-market intelligence tools for AI agents, enabling discovery, evaluation, and mispricing detection across venues like Polymarket and Kalshi with per-call payment.
      1
      -

    • x402farm-mcp

      laurenthalbrun
      A
      license
      Not graded
      quality
      F
      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.
      4 npm
      MIT

    • Agent Kiosk

      ralf9090
      A
      license
      B
      quality
      C
      maintenance
      Pay-per-call MCP and x402 v2 server on Base USDC providing 19 keyless tools for AI agents: web extraction, social and academic search, B2B lead and domain intelligence, npm/PyPI package and smart-contract security audits, OFAC compliance screening, and DeFi swap quotes
      5
      23
      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/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly distinct (get_index, get_sample, get_research, etc.), but get_latest and get_signal overlap significantly since get_signal can omit the index to return the latest item. get_track_record and get_whales are related but their descriptions clearly separate free proof from paid data.

    Naming Consistency5/5

    All tools follow a consistent get_<noun> pattern with snake_case throughout. Plurals and modifiers (get_signals, get_digest_history) fit the convention and are predictable.

    Tool Count5/5

    13 tools is well-scoped for a Polymarket intelligence API, covering free hooks, paid signals, digests, whale tracking, and research without over-expanding. Each tool has a clear role in the workflow.

    Completeness4/5

    The tool surface covers the core intelligence workflow: polling for new items, retrieving individual/batch signals, digest summaries and history, whale calibration, resolving markets, and on-demand research. Minor gaps exist (e.g., no simple market quote tool), but the domain is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources