Skip to main content
Glama

Server Details

AI-agent probability research with one-call preflight and human-gated XRP activation.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
1.0% over 44 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.9/5.0

Scored across 8 tools

Disambiguation2/5

There are significant overlaps between tools like evaluate_crowdgap_fit, preflight_forecast_request, and request_live_forecast, which all seem to handle different stages of the same forecast workflow. Similarly, get_crowdgap_offer, get_xrp_checkout, and create_xrp_subscription_quote all revolve around the payment/offering process, creating ambiguity about which one an agent should call in a given situation.

Naming Consistency4/5

All tool names are consistently snake_case and mostly follow a verb_noun pattern, which is good. However, the verbs chosen (create, evaluate, get, get, get, preflight, request, test) are somewhat varied and don't form a tightly coherent set, and the nouns aren't always parallel (e.g., crowdgap_offer vs xrp_checkout).

Tool Count5/5

Eight tools is a very reasonable number for a server with this scope. Each tool seems to map to a distinct action or resource in the CrowdGap workflow, from evaluating fit, to preflighting and running forecasts, to obtaining quotes and offers.

Completeness3/5

The core workflow of evaluating, preflighting, and running a forecast is covered, and there's a test schema tool for validation. However, there's no way to retrieve past forecast results, check subscription/payment status, or manage an existing subscription, which could force agents into dead ends in some scenarios.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedcreate_xrp_subscription_quote2 fields changed
      • addedInput schema / properties / planId
        Added value: +{
        +  "description": "monthly costs 9.99 XRP for 30 days; annual costs 99 XRP for 365 days. Both include 30 forecasts per rolling 30 days.",
        +  "enum": [
        +    "monthly",
        +    "annual"
        +  ],
        +  "type": "string"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "requestId",
        -  "agentName",
        -  "operatorReference",
        -  "consent"
        -]New value: +[
        +  "requestId",
        +  "agentName",
        +  "operatorReference",
        +  "planId",
        +  "consent"
        +]
  2. 2 tool updates
    • Changedcreate_xrp_subscription_quote2 fields changed
      • changedInput schema / properties / consent / description
        Previous value: -"Confirms the human operator must authorize and send any XRP payment."New value: +"Set true only after the human explicitly authorizes creation of this 15-minute quote. The human independently decides whether to send XRP."
      • addedInput schema / properties / requestId / description
        Added value: +"Reuse draftRequest.requestId from a successful preflight to bind the quote to that validated request."
    • Changedpreflight_forecast_request4 fields changed
      • removedInput schema / properties / consent
        Removed value: -{
        -  "const": true,
        -  "type": "boolean"
        -}
      • addedInput schema / properties / context / description
        Added value: +"Optional public context for validating the request shape; it is not stored."
      • removedInput schema / properties / requestId
        Removed value: -{
        -  "pattern": "^[a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[89ab][a-f0-9]{3}-[a-f0-9]{12}$",
        -  "type": "string"
        -}
      • changedInput schema / required
        Previous value: -[
        -  "requestId",
        -  "question",
        -  "deadline",
        -  "resolutionSource",
        -  "context",
        -  "consent"
        -]New value: +[
        +  "question",
        +  "deadline",
        +  "resolutionSource"
        +]
  3. 1 tool update
    • Addedevaluate_crowdgap_fit
  4. 1 tool update
    • Addedpreflight_forecast_request
  5. 6 tool updates
    • First observedcreate_xrp_subscription_quote
    • First observedget_agent_referral_pack
    • First observedget_crowdgap_offer
    • First observedget_xrp_checkout
    • First observedrequest_live_forecast
    • First observedtest_forecast_schema

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    --
    MIT
  • A
    license
    Not graded
    quality
    F
    maintenance
    Enables AI agents to execute prediction-market trades through a risk-control gateway that enforces signed mandates and generates proof trails for accountability.
    0
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    MCP server for agent-to-agent payments on the XRP Ledger — job marketplace, crypto-condition escrow, AI-verified work delivery, trust scoring, and wallet bootstrap from Coinbase.
    6
    40
    MIT
  • A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to execute actions under an accountability layer with identity passports, mandates, a permission gate, and a tamper-evident journal, while requiring human confirmation for irreversible operations.
    7
    37 PyPI
    4
    AGPL 3.0
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources