# BRAINIAC API Catalog (MCP) [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://www.brainiac.software/mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/brainiac-api-catalog-mcp

## Description
Find and call 1,150+ BRAINIAC pay-per-call APIs from one MCP server (x402 USDC on Base). One MCP server to find and call every BRAINIAC pay-per-call API: list_apis, search_endpoints, describe_endpoint (input schema, example, price) and call_endpoint across 1,100+ compliance, security, procurement, finance and crypto endpoints.

## Tools
Capabilities this server exposes over MCP:

- **list_apis** — List the public MCP servers. Each server is one API.
- **search_endpoints** — Search paid endpoints by id, title, description, or path. Optional api is a product slug or title.
- **describe_endpoint** — Return the input schema, example, path, and price for one paid endpoint. This does not run the endpoint.
- **call_endpoint** — Call one paid POST endpoint by id. Unpaid calls return 402 and do not run. Payment settles only after a successful result.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "brainiac-api-catalog-mcp": {
    "url": "https://www.brainiac.software/mcp"
  }
}
```

## Documentation

## What BRAINIAC API Catalog (MCP) does

BRAINIAC API Catalog (MCP) brings a large catalog of paid APIs into one MCP connection. Each catalog entry represents an API, and the available endpoints span areas including compliance, security, procurement, finance, and crypto. Rather than configuring a separate MCP server for each product, an agent can discover endpoint metadata and invoke the selected API through the catalog.

The service is intended for workflows where an agent needs to find a suitable external API at runtime, inspect how to call it, and pay for the request when execution is required. The catalog contains more than 1,150 pay-per-call APIs.

## How it works

MCP clients connect to the hosted endpoint at `https://www.brainiac.software/mcp`. The client can first call `list_apis` to see the public MCP servers represented in the catalog. It can then use `search_endpoints` to look for paid endpoints by endpoint ID, title, description, or path. Searches can optionally be narrowed to an API by product slug or title.

Before making a request, `describe_endpoint` returns the selected endpoint's input schema, an example, its path, and its price. This inspection step does not execute the endpoint. When the agent is ready, `call_endpoint` invokes a paid POST endpoint by ID.

Payments use x402 with USDC on Base. An unpaid call receives HTTP 402 and the endpoint is not run. Payment is settled only after the endpoint returns a successful result.

## Setup and configuration

Use the hosted MCP endpoint rather than running a local server: `https://www.brainiac.software/mcp`. Add that endpoint to an MCP-compatible client, then use the discovery tools to identify an API and endpoint. The service is exposed as an MCP server, so the client is responsible for establishing the MCP connection and presenting the available tools.

## Tools and capabilities

- `list_apis` lists the public MCP servers in the catalog, with each server representing one API.
- `search_endpoints` searches paid endpoints by ID, title, description, or path, with an optional API filter.
- `describe_endpoint` shows an endpoint's required input schema, example request information, path, and price without running it.
- `call_endpoint` calls a paid POST endpoint by endpoint ID.
- x402 payment handling uses USDC on Base and prevents unpaid requests from executing.

## Limitations and notes

The catalog is centered on paid API calls. Endpoint discovery and inspection are separate from execution, but invoking an endpoint can require payment. A request that has not been paid returns 402 and does not run; successful calls settle payment only after a successful result. Endpoint-specific input requirements and prices should be checked with `describe_endpoint` before calling.

_Full upstream README: https://allmcps.com/mcp/brainiac-api-catalog-mcp/readme_

