BRAINIAC Crypto Security
Pay-per-call crypto security checks for AI agents, settled in USDC via x402
Answered our latest tool-list check 12 hours ago with 4 tools. It will be marked verified after 3 successful checks in 7 days.
BRAINIAC Crypto Security is a paid MCP server for finance and payments. It runs as a hosted remote server, so there is nothing to install locally.
- Pricing
- Paid
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.1
- Listing updated
Similar MCP servers
Install
Run in a terminal
claude mcp add --transport http crypto-security https://www.brainiac.software/mcp/crypto-securityAdd to Settings → Connectors → Add custom connector
https://www.brainiac.software/mcp/crypto-securityAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"crypto-security": {
"url": "https://www.brainiac.software/mcp/crypto-security"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"crypto-security": {
"type": "http",
"url": "https://www.brainiac.software/mcp/crypto-security"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"crypto-security": {
"serverUrl": "https://www.brainiac.software/mcp/crypto-security"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://www.brainiac.software/mcp/crypto-securityEnter a Name (for example "BRAINIAC Crypto Security"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"crypto-security": {
"type": "http",
"url": "https://www.brainiac.software/mcp/crypto-security"
}
}
}Using several servers? Build one config file with the MCP config generator.
About BRAINIAC Crypto Security
The BRAINIAC crypto security server gives AI clients access to a paid security API. Calls are priced per request in fixed USDC amounts on the Base network, so an agent can pay for a result without creating an account first.
The MCP endpoint is served over streamable HTTP. The registry entry notes that unpaid tool calls return HTTP 402, so a client needs x402 payment support to use it.
It suits developers and autonomous agents that need a quick security check on crypto activity as one step in a larger workflow, and that prefer metered payment over a subscription.
Tools this server provides (4)
Read directly from the server.
All 4 tools say they're read-only.
From the server's own tool annotations; not verified by us.
- crypto-security_transaction-intent-verifySays read-only
- Compare an EVM transaction's calldata and native value with the action declared in the request before you sign or send a transaction. Decoding uses the ABI in the request, or the standard ERC-20 transfer, transferFrom, approve, and increaseAllowance encodings when that selector matches. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not char
- crypto-security_intent-safetySays read-only
- Read a caller-supplied EVM transaction or an EIP-712 typed-data message and describe the transfer, approval, permit, or outer call it encodes before you sign or send a transaction. Known selectors are transfer, transferFrom, approve, increaseAllowance, setApprovalForAll, permit, multicall, aggregate, and execute. The score is a local penalty count. HTTP 200 with status complete, partial, or failed
- crypto-security_proxy-upgrade-storage-auditSays read-only
- Compare the Solidity storage layout of an upgradeable implementation with a proposed replacement before you sign or send a transaction. Variables are matched by slot and offset, not by name. The types map is used for structs, mappings, dynamic arrays, and byte sizes. compatibility_status is compatible, incompatible, warnings, or indeterminate. HTTP 200 with status complete, partial, or failed is c
- crypto-security_storage-slot-gradeSays read-only
- Compare two caller-supplied storage layouts by slot, offset, and size before you sign or send a transaction. A name that moves is a shift. Different names that occupy the same bytes are a collision. The grade and the collision score come from those counts. A variable is one slice of a single slot. No chain is queried. Call with previous and next. HTTP 200 with status complete, partial, or failed i
What it does
- Pay-per-call access
- Each tool call is paid individually in fixed USDC pricing on Base, with no account setup.
- x402 payment flow
- Unpaid requests receive an HTTP 402 response, which prompts the client to complete payment.
- Streamable HTTP transport
- The server is reachable at a single remote MCP endpoint using streamable HTTP.
- Crypto security checks
- The API focuses on security screening for crypto-related activity.
Good for
- Screening a crypto counterparty or address before an agent sends funds
- Adding a paid security check to an autonomous trading or payment workflow
- Giving an AI assistant a pay-per-use crypto security lookup without a subscription
Pricing
Paid
Pay-per-call in fixed USDC on Base.
Prices change. Check brainiac.software before you buy.
BRAINIAC Crypto Security FAQ
Do I need an account to use BRAINIAC Crypto Security?
The vendor site says there is no account to set up. You pay a fixed USDC price on Base for each result.
What happens if a call is not paid?
The registry entry says unpaid tool calls return HTTP 402.
How do I add BRAINIAC Crypto Security to Claude Code?
Run this command in your terminal: claude mcp add --transport http crypto-security https://www.brainiac.software/mcp/crypto-security
What are the best alternatives to BRAINIAC Crypto Security?
The closest alternatives to BRAINIAC Crypto Security are BRAINIAC Application & Pipeline Security Checks, BRAINIAC Brand Protection, BRAINIAC Agent Execution Contract Intelligence, BRAINIAC Accessibility Intelligence and BRAINIAC Account Abstraction.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Status and tools: checked automatically by AIPoweredBot on 21 November 2026.
- Install steps: from the official MCP Registry entry.