BRAINIAC Account Abstraction MCP server
software.brainiac/account-abstractionbrainiac.softwarestreamable-httpv1.0.1Scanned
Paid Account Abstraction API via x402. Unpaid tool calls return 402.
4 tools: 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BRAINIAC Account Abstraction MCP server can do
The BRAINIAC Account Abstraction MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: account-abstraction_sponsorship-risk, account-abstraction_user-operation-audit and account-abstraction_user-op-validity), but cannot delete data. 1 tool only reads.
4 tools bring in text other people can write (account-abstraction_paymaster-sponsorship-audit, account-abstraction_sponsorship-risk, account-abstraction_user-operation-audit and 1 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 3Claude Code: ask
account-abstraction_sponsorship-riskAdd the caller-supplied call gas and verification gas, multiply by the max fee, and compare that cost with the paymaster deposit.Reads text others write1 finding
Why it is in this group
- The description's first verb is "add": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "account-abstraction_sponsorship-risk" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "add": a word for a change.
Description, as the server wrote it Add the caller-supplied call gas and verification gas, multiply by the max fee, and compare that cost with the paymaster deposit. Gas above the stated ceilings, and init code when it is not allowed, raise the risk score. The safety index is how far each gas field sits inside its ceiling. No deposit is read from a chain. Price $0.04 USDC. POST /api/v1/account-abstraction/sponsorship-risk. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Score paymaster sponsorship risk
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
account-abstraction_user-op-validityCheck a caller-supplied nonce, signature length, init code, and calldata length.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check a caller-supplied nonce, signature length, init code, and calldata length. A signature of 64 or 65 bytes passes the length check and is not recovered. init code of at least 20 bytes is a factory deployment and is not simulated. The rejection index counts format problems. It does not say whether a bundler will accept the operation. Price $0.04 USDC. POST /api/v1/account-abstraction/user-op-validity. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Score UserOperation format
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
account-abstraction_user-operation-auditCheck the structure of one ERC-4337 UserOperation before it is submitted to a bundler.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check the structure of one ERC-4337 UserOperation before it is submitted to a bundler. EntryPoint 0.6 uses initCode and paymasterAndData. EntryPoint 0.7 uses factory, factoryData, and separate Paymaster fields. On 0.7, callGasLimit, verificationGasLimit, the fee fields, and Paymaster gas limits must fit in uint128. Calldata is decoded only with the supplied ABI. Expected targets are compared only with decoded address parameters named dest, target, or to. validation_status is valid, invalid, warnings, or indeterminate. risk_level is low, medium, high, or critical. The signature is not recovered. No chain state is read, execution is not simulated, and the result does not say whether a bundler will accept the operation. Price $0.05 USDC. POST /api/v1/account-abstraction/user-operation-audit. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Audit user operation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
account-abstraction_paymaster-sponsorship-auditCompare ERC-4337 UserOperations with a caller-supplied Paymaster sponsorship policy.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Compare ERC-4337 UserOperations with a caller-supplied Paymaster sponsorship policy. EntryPoint versions are 0.6 and 0.7. An omitted paymasterDataFormat is envelope: the EntryPoint address and, on 0.7, the two 16-byte gas limits are read, and later bytes stay opaque. verifying_paymaster also reads validUntil and validAfter as two 6-byte integers; a validUntil of 0 means no upper bound, and the signature is not verified. Call targets and selectors are read only from declared values, raw calldata offsets, or execute(address,uint256,bytes). audit_status is allowed, denied, warnings, invalid, or indeterminate. risk_level is low, medium, high, or critical. Sponsored gas is the EntryPoint required-prefund sum, multiplied by maxFeePerGas for the amount in wei. No Paymaster deposit, balance, reputation, or other chain state is read, and the result does not say whether a bundler will accept the operation. Price $0.05 USDC. POST /api/v1/account-abstraction/paymaster-sponsorship-audit. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Audit paymaster sponsorship
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.brainiac.software/mcp/account-abstraction: tools/list returned 4 tools to an anonymous client, including account-abstraction_paymaster-sponsorship-audit (write), account-abstraction_sponsorship-risk (write), account-abstraction_user-operation-audit (write), account-abstraction_user-op-validity (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "account-abstraction_sponsorship-risk" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "add": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:account-abstraction_paymaster-sponsorship-auditOnly readsinputSchemaannotations
- Changed:account-abstraction_sponsorship-riskChanges thingsinputSchemaannotations
- Changed:account-abstraction_user-op-validityChanges thingsinputSchemaannotations
- Changed:account-abstraction_user-operation-auditChanges thingsinputSchemaannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http account-abstraction https://www.brainiac.software/mcp/account-abstractionclaude mcp add --transport http account-abstraction https://www.brainiac.software/mcp/account-abstractionRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__account-abstraction__account-abstraction_paymaster-sponsorship-audit"
],
"ask": [
"mcp__account-abstraction__account-abstraction_sponsorship-risk",
"mcp__account-abstraction__account-abstraction_user-operation-audit",
"mcp__account-abstraction__account-abstraction_user-op-validity"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as account-abstraction. Review it before you use it.
Capability tags behind 4 rules
- mcp__account-abstraction__account-abstraction_paymaster-sponsorship-audit untrusted-input
- mcp__account-abstraction__account-abstraction_sponsorship-risk untrusted-input
- mcp__account-abstraction__account-abstraction_user-operation-audit untrusted-input
- mcp__account-abstraction__account-abstraction_user-op-validity untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/software.brainiac/account-abstraction/verify?hash=c959ad37e1331a26bb8b95f0767bdb40c7b930615af5d695117e6d988c23fc56" | jq -e '.changed == false'Pinned hash c959ad37e133, from Nov 20, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/software.brainiac/account-abstraction/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/software.brainiac/account-abstraction)Source: MCP Registry. Synced Nov 20, 2026, 01:17 UTC.
BRAINIAC Account Abstraction MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BRAINIAC Account Abstraction MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BRAINIAC Account Abstraction MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BRAINIAC Account Abstraction MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the BRAINIAC Account Abstraction MCP server have?
- 4 tools: 3 write, 1 read. account-abstraction_sponsorship-risk, account-abstraction_user-operation-audit, account-abstraction_user-op-validity and account-abstraction_paymaster-sponsorship-audit.
Does the BRAINIAC Account Abstraction MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BRAINIAC Account Abstraction MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BRAINIAC Account Abstraction MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.