BRAINIAC Token Security & Risk Intelligence

What BRAINIAC Token Security & Risk Intelligence does

BRAINIAC Token Security & Risk Intelligence exposes Base token-security checks through MCP and provides a directory of public and paid MCP endpoints. Its risk output keeps three kinds of information distinct: verified or reported facts, detected signals, and checks that could not be completed. This structure helps an agent avoid treating an unavailable check as evidence of safety or risk.

Token analysis includes pause and blacklist indicators, ownership signals, and DEX liquidity signals. The service also supports endpoint discovery, so an agent can inspect available APIs and determine the requirements and price of a paid endpoint before calling it.

How it works

MCP clients connect to the hosted endpoint at https://www.brainiac.software/mcp. The server exposes catalog operations for finding APIs and endpoint operations for inspecting or invoking them.

Listing public MCP servers, searching endpoints, and describing an endpoint do not run the paid operation. A description includes the endpoint's input schema, an example, its path, and its price. When an agent submits a paid POST request through call_endpoint, payment uses x402 USDC on Base. An unpaid call returns HTTP 402 and does not execute; payment settles only after a successful result.

No API key is required. The calling environment must still support the MCP connection and the payment flow for paid endpoint calls.

Tools and capabilities

• list_apis lists the public MCP servers available through the catalog. Each server represents one API.
• search_endpoints searches paid endpoints by ID, title, description, or path. The optional api filter accepts a product slug or title.
• describe_endpoint returns one paid endpoint's input schema, example, path, and price without executing it.
• call_endpoint invokes one paid POST endpoint by ID. Calls that have not been paid for return 402 instead of running.
• Base token checks provide an evidence-based risk verdict with facts, signals, and unavailable checks kept separate.
• Token-security signals cover ownership, DEX liquidity, and pause or blacklist indicators.

Setup and configuration

Add the hosted MCP URL, https://www.brainiac.software/mcp, to an MCP-compatible client. No API key or environment variable is needed for the connection. Before using a paid endpoint, use describe_endpoint to retrieve its schema and price, then provide the required input to call_endpoint.

Listing and discovery are suitable for finding available APIs without incurring endpoint-call charges. Paid operations require x402 USDC on Base and return a payment error rather than executing when payment is absent.

Limitations and notes

The catalog and token checks have different roles: catalog tools discover and invoke endpoints, while token-security checks provide the risk-oriented information for Base tokens. A missing or unavailable check remains distinct from a positive or negative signal, so downstream agents should account for incomplete evidence. Paid calls begin at the published endpoint price, with the listing describing the exact cost before execution.