BRAINIAC Contract Security
Server Details
Paid Contract Security API via x402. Unpaid tool calls return 402.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
Both tools compare two caller-supplied EVM bytecodes and report similarity, so an agent could hesitate between them for a basic comparison request. The descriptions do distinguish structural/instruction-level diffing from byte-level exact/normalized comparison, but the boundary is not as crisp as it could be.
Both names use the same `contract-security_` prefix and kebab-case descriptive style, with no mixed casing or verb-style inconsistency. The main weakness is that `diff` and `compare` are near-synonyms, making the names less self-differentiating.
Two tools is thin for a server branded 'Contract Security', even if the intended scope is bytecode comparison. The pair is focused, but there is little supporting surface such as single-contract inspection or reporting.
For pairwise bytecode comparison, exact, normalized, and structural/opcode-level modes are reasonably covered. However, broader contract-security coverage is missing: no single-bytecode analysis, no disassembly/opcode report, no selector extraction, and no vulnerability heuristics beyond risk-opcode counts.
Available Tools
2 toolscontract-security_bytecode-structure-diffDiff bytecode structureBInspect
Decode two caller-supplied EVM bytecodes, or two instruction lists, into opcodes and compare the instruction sequence. Similarity ignores PUSH immediates. The risk delta counts CALL, SSTORE, CREATE, DELEGATECALL, CALLCODE, and SELFDESTRUCT. A high similarity is not proof that the contracts behave the same. No chain is queried. Price $0.04 USDC. POST /api/v1/contract-security/bytecode-structure-diff. Unpaid calls return 402 and do not run.
Inputs: left (required), right (required).
contract-security_contract-bytecode-compareCompare contract bytecodeAInspect
Compare two caller-supplied EVM bytecodes. mode exact compares every byte. An omitted mode is exact. mode normalized masks only the supplied immutable ranges and a trailing Solidity CBOR metadata suffix when bytecodeKind is not creation and that suffix is present on both bytecodes. comparison_status is identical, different, partially_comparable, or invalid. Hashes are keccak256 of the supplied bytes. Similarity is the share of equal compared bytes, truncated to 4 decimal places. A difference is not a judgment that either bytecode is malicious, and similar bytecode is not equivalent behavior. No source code is verified and no chain is queried. Price $0.05 USDC. POST /api/v1/contract-security/contract-bytecode-compare. Unpaid calls return 402 and do not run.
Inputs: candidate (required), reference (required), mode, bytecodeKind, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Paid Crypto Security API via x402. Unpaid tool calls return 402.
1Paid Contract Operations API via x402. Unpaid tool calls return 402.
1Paid Account Abstraction API via x402. Unpaid tool calls return 402.
1Paid Crypto Operations API via x402. Unpaid tool calls return 402.
1
Related MCP Servers
FlicenseNot gradedqualityDmaintenance33 crypto security tools via x402 micropayments. Auto-refund guarantee. $0.01-$0.15/call.-- FlicenseNot gradedqualityDmaintenance33 crypto security tools via x402 micropayments. Auto-refund guarantee. $0.01-$0.15/call.-
- AlicenseAqualityBmaintenancePay-per-call smart-contract & token security via x402 — scans, simulations, honeypot/tax checks, attested verdicts.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables paid, per-request access to raw on-chain token security data (honeypot, taxes, holders, liquidity) on Arc mainnet via x402 payments, without scores or advice.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.