Skip to main content
Glama

BRAINIAC Crypto Operations

Server Details

Paid Crypto Operations API via x402. Unpaid tool calls return 402.

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

B3.4/5.0

Scored across 2 tools

Disambiguation2/5

Both tools analyze caller-supplied source and destination bridge records matched by message id and assess consistency, so their boundaries overlap heavily. The descriptions hint at different outputs (recovery index vs. risk/status classification), but an agent cannot reliably know which tool to select for a given audit task.

Naming Consistency4/5

Both names follow the same server-prefixed kebab-case convention, making them predictable and readable. They are noun phrases rather than verb_noun patterns, but the style is consistent across the set.

Tool Count3/5

Two tools is thin for a server branded as broad 'Crypto Operations'. If the scope were explicitly bridge auditing, two could be reasonable, but as presented the surface feels underbuilt.

Completeness2/5

The server only covers bridge consistency and partial-failure auditing, with no chain queries, transaction lookup, or other crypto operations. For a general crypto-operations server, this leaves significant gaps and dead ends.

Available Tools

2 tools
crypto-operations_bridge-leg-consistencyScore bridge leg consistencyAInspect

Group caller-supplied source and destination legs by message id. A message is consistent when both legs succeeded for the same amount. The recovery index is the hardest leg: a pending destination after a successful source scores lower than two matching successes. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-operations/bridge-leg-consistency. Unpaid calls return 402 and do not run.

Inputs: legs (required).

crypto-operations_bridge-partial-failure-auditAudit bridge partial failureAInspect

Compare caller-supplied source and destination records for a cross-chain bridge. Operations are matched only by message identifier, or by the log field named in fieldMapping. Amounts are scaled with the supplied decimals, fee, and optional conversion rate. consistency_status is consistent, inconsistent, incomplete, or indeterminate. risk_level is low, medium, high, or critical. A missing record is incomplete evidence, not proof that the bridge failed. No chain is queried, and no transaction is treated as final. Price $0.05 USDC. POST /api/v1/crypto-operations/bridge-partial-failure-audit. Unpaid calls return 402 and do not run.

Inputs: source (required), destination (required), fee, conversion, +2 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
      Not graded
      quality
      C
      maintenance
      Enables AI agents and bots to buy per-call data and intelligence — token safety verdicts, prices, news, weather, web-to-text, and research dossiers — without signup or API keys, since each call is authenticated by an on-chain USDC payment on Base via the x402 protocol. Clients hit any paid endpoint, receive an HTTP 402 challenge, sign an EIP-3009 transfer authorization, and retry to get the data.
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources