Skip to main content
Glama

Server Details

Read-only machine payment preflight using dated MEO evidence, with explicit unknowns.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of confusing it with another tool. Its purpose is clearly defined and exhaustive for its singular function.

Naming Consistency5/5

The single tool name 'preflight_machine_payment' follows a clear descriptive snake_case pattern that combines an action and object. With only one tool, there are no inconsistent conventions to penalize.

Tool Count4/5

A single tool is technically thin, but the server is intentionally scoped to a specific read-only preflight operation. The count slightly under typical expectations, yet it is reasonable for this narrow, focused purpose.

Completeness5/5

The tool covers the entire stated functionality of the server—a preflight check for machine payments. It provides sufficient outputs (terms, context, freshness, unknowns) and explicitly notes what it does not do, avoiding surprising gaps within its scope.

Available Tools

1 tool
preflight_machine_paymentPreflight a machine paymentA
Read-onlyIdempotent
Inspect

Before paying an unfamiliar machine service, call this read-only tool to compare the proposed resource, payment destination, network, asset and amount with MEO's dated economic history. Returns observed payment-term matches or changes, settlement/buyer/activity context when available, evidence freshness, and explicit unknowns. It does not execute or approve payment and never interprets missing evidence as safe. Pilot scope: two services; third-party public probe observations retained by MEO, not independently verified settlements. Settlement/buyer history, current activity and payment destination history are UNKNOWN. Evidence may be stale. Invocation example: {"resource_url":"https://blockrun.ai/api/v1/exa/search","pay_to":"0x0000000000000000000000000000000000000001","network":"eip155:8453","asset":"USDC","amount":"0.011"}

Inputs: asset (required), amount (required), pay_to (required), network (required), +1 more. Returns: version, evidence, request_id, limitations, +10 more

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      A read-only MCP server that collects contract and bank-statement evidence, splits incoming platform payments per merchant, and generates explainable claiming candidates written into a fixed 13-column local template for human review. All operations are strictly read-only (no logins, uploads, imports, or reconciliation writes), and it exposes blockers with provenance evidence instead of guessing.
      5
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that performs deterministic local preflights of agent-payment boundary documents and x402 v2 PaymentRequired JSON, and prepares unsubmitted public quote-request drafts without network calls or fund movement.
      1
      -
    • A
      license
      B
      quality
      B
      maintenance
      Evaluates proposed x402 payments against a local policy and returns pay, review, or do_not_pay, while also listing and evaluating outstanding authorizations to flag double-pay or limbo risk.
      5
      5
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources