Skip to main content
Glama
0xJB-dev

Gibraltar Prediction Markets MCP Server

by 0xJB-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Gibraltar Prediction Markets MCP Server

No user-submitted related servers found.

    Related Servers

    • lector

      namespaceMarcello
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and retrieve cited passages from the EU AI Act in English or Italian, including full articles and cross-references, so agents can ground answers in verified regulatory text.
      MIT

    • Prediction Market Odds

      MAASAI-Labs
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search Polymarket and Kalshi, read live implied probabilities and order books, compare the same question side by side across both venues, and produce short markdown briefings with cited sources. It is read-only, needs no API keys, and performs no trading.
      5
      MIT

    • polymarket-mcp

      pab1it0
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query Polymarket prediction markets and analyze market data through the MCP interface.
      9
      -

    • JTX Markets MCP Server

      jtxmarketsofficial
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only querying of JTX Markets account and market data, including balance, positions, orders, trades, funding history, and market summaries, through natural language in MCP-compatible clients.
      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.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: metadata, search, list, or retrieval of specific components (regulations, parts, schedules, definitions, checklists, conditions). No two tools overlap in functionality.

    Naming Consistency4/5

    Most retrieval tools follow a consistent 'get_' prefix pattern, but 'about', 'fetch', 'search', and 'list_regulations' break this convention. While still readable, the naming is not perfectly uniform.

    Tool Count5/5

    10 tools cover the domain of a regulatory document server comprehensively without being excessive. Each tool earns its place.

    Completeness5/5

    The tool set covers all necessary operations for a static legal document: metadata, search, listing, and retrieval of any component. There are no obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources