Skip to main content
Glama

BRAINIAC API catalog

Server Details

Search and call BRAINIAC pay-per-call APIs. Unpaid 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

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

The four tools split cleanly along discovery vs. metadata vs. execution lines: list_apis enumerates servers, search_endpoints finds endpoints, describe_endpoint returns schema/price without running, and call_endpoint actually executes a paid call. The describe_endpoint/call_endpoint pair is explicitly contrasted in their descriptions ("does not run the endpoint" vs. "call"), leaving no realistic misselection.

Naming Consistency5/5

All four tools follow a strict snake_case verb_noun pattern (list_apis, search_endpoints, describe_endpoint, call_endpoint), with the verb carrying the semantic weight. The only trivial variation is singular 'endpoint' vs. plural 'endpoints/apis', which reads naturally rather than inconsistently.

Tool Count4/5

Four tools is on the lean side, but each maps to a distinct stage of the workflow (browse → search → inspect → invoke) with no filler. It is a small surface, though nothing appears superfluous or missing at the tool-count level.

Completeness4/5

The core lifecycle for a paid endpoint catalog — discover APIs, find endpoints, inspect schema and price, execute with settlement — is fully covered. Gaps are minor but real: there is no way to check account balance, payment history, or failed-settlement status, which agents handling 402 responses may want.

Available Tools

4 tools
call_endpointCall endpointBInspect

Call one paid POST endpoint by id. Unpaid calls return 402 and do not run. Payment settles only after a successful result.

Inputs: id (required), params.

describe_endpointDescribe endpointAInspect

Return the input schema, example, path, and price for one paid endpoint. This does not run the endpoint.

Inputs: id (required).

list_apisList APIsBInspect

List the public MCP servers. Each server is one API.

Inputs: no named parameters.

search_endpointsSearch endpointsBInspect

Search paid endpoints by id, title, description, or path. Optional api is a product slug or title.

Inputs: query (required), api.

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
      B
      maintenance
      Enables AI agents to call 93 pay-per-call machine-to-machine services spanning web scraping, crypto sentiment, market data, on-chain analytics, social and threat intelligence, vulnerability scanning, and micro-SaaS utilities. Payments are settled in USDC on Arbitrum via the x402 protocol using a wallet header, so no API keys, signups, or billing setup are required.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Pay-per-call AI microservices settled in USDC on Base via the x402 (HTTP 402) protocol. 28 tools including web search, summarization, extraction, code review, deep research, crypto safety, sanctions screening and on-chain data — no accounts or API keys.
      4 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and verify machine-payable HTTP 402/x402 APIs using live probe data, providing ranked results by liveness, uptime, price, and trustworthiness.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources