BRAINIAC Restaking Risk MCP server
software.brainiac/restaking-riskbrainiac.softwarestreamable-httpv1.0.1Scanned
Paid Restaking Risk 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
- No findings
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 Restaking Risk MCP server can do
The BRAINIAC Restaking Risk 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: restaking-risk_cross-network-slashing-exposure, restaking-risk_slashing-correlation and restaking-risk_exit-window), but cannot delete data. 1 tool only reads.
4 tools bring in text other people can write (restaking-risk_cross-network-slashing-exposure, restaking-risk_slashing-correlation, restaking-risk_slashing-window-feasibility and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
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
restaking-risk_cross-network-slashing-exposureCalculate unique collateral, gross exposure, and overlap when caller-supplied vault collateral is reused across networks.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 Calculate unique collateral, gross exposure, and overlap when caller-supplied vault collateral is reused across networks. Simultaneous scenarios slash the starting balance and cap the combined percent at 100%. Sequential scenarios reduce the remaining balance after each event. audit_status is calculated, warnings, incomplete, or invalid. Amounts are integers in the caller-supplied unit. Prices and conversion rates are used only when supplied. No balance or price is fetched. Price $0.05 USDC. POST /api/v1/restaking-risk/cross-network-slashing-exposure. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Calculate cross-network slashing exposure
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
restaking-risk_exit-windowSubtract the unbonding time and the withdrawal delay from the soonest caller-supplied slash horizon.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 Subtract the unbonding time and the withdrawal delay from the soonest caller-supplied slash horizon. The buffer is that remainder in hours. The feasibility score is the buffer divided by the soonest horizon, and it is zero when the buffer is negative. No queue is read from a network. Price $0.04 USDC. POST /api/v1/restaking-risk/exit-window. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Score exit timing before a slash
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
restaking-risk_slashing-correlationCap each operator's network weights at 100 percent of its stake, then weight that exposure by stake.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 Cap each operator's network weights at 100 percent of its stake, then weight that exposure by stake. The correlation score is the share of stake that sits on more than one network. Weights are the caller's risk weights. No stake is fetched. Price $0.04 USDC. POST /api/v1/restaking-risk/slashing-correlation. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Score cross-network slashing correlation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
restaking-risk_slashing-window-feasibilityCompare caller-supplied slashing stages with an available window.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 caller-supplied slashing stages with an available window. Each duration is an integer in seconds, or in epochs when its unit is epochs. Epoch length is seconds. Stages run in detection, evidence, submission, veto, execution, and finality order. Consecutive stages listed in parallel start together and the timeline uses the longest. A missing stage is incomplete and is not treated as zero. feasibility_status is feasible, margin_exceeded, infeasible, incomplete, or invalid. A fit is arithmetic only. No protocol parameters are fetched. Price $0.05 USDC. POST /api/v1/restaking-risk/slashing-window-feasibility. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Check slashing window feasibility
- 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, 19:34 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/restaking-risk: tools/list returned 4 tools to an anonymous client, including restaking-risk_cross-network-slashing-exposure (write), restaking-risk_slashing-correlation (write), restaking-risk_slashing-window-feasibility (write), restaking-risk_exit-window (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:restaking-risk_cross-network-slashing-exposureChanges thingsinputSchemaannotations
- Changed:restaking-risk_exit-windowChanges thingsinputSchemaannotations
- Changed:restaking-risk_slashing-correlationChanges thingsinputSchemaannotations
- Changed:restaking-risk_slashing-window-feasibilityOnly readsinputSchemaannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http restaking-risk https://www.brainiac.software/mcp/restaking-riskclaude mcp add --transport http restaking-risk https://www.brainiac.software/mcp/restaking-riskRun 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__restaking-risk__restaking-risk_slashing-window-feasibility"
],
"ask": [
"mcp__restaking-risk__restaking-risk_cross-network-slashing-exposure",
"mcp__restaking-risk__restaking-risk_slashing-correlation",
"mcp__restaking-risk__restaking-risk_exit-window"
],
"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 restaking-risk. Review it before you use it.
Capability tags behind 4 rules
- mcp__restaking-risk__restaking-risk_cross-network-slashing-exposure untrusted-input
- mcp__restaking-risk__restaking-risk_slashing-correlation untrusted-input
- mcp__restaking-risk__restaking-risk_slashing-window-feasibility untrusted-input
- mcp__restaking-risk__restaking-risk_exit-window 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/restaking-risk/verify?hash=f680a5e1499f4a1dca8c2d462a918c185fa7cb3604b429dcadc7fae160f1d661" | jq -e '.changed == false'Pinned hash f680a5e1499f, from Nov 20, 2026, 01:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/software.brainiac/restaking-risk/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/software.brainiac/restaking-risk)Source: MCP Registry. Synced Nov 20, 2026, 01:18 UTC.
BRAINIAC Restaking Risk MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BRAINIAC Restaking Risk MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings 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 Restaking Risk 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 Restaking Risk 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 Restaking Risk MCP server have?
- 4 tools: 3 write, 1 read. restaking-risk_cross-network-slashing-exposure, restaking-risk_slashing-correlation, restaking-risk_exit-window and restaking-risk_slashing-window-feasibility.
Does the BRAINIAC Restaking Risk MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BRAINIAC Restaking Risk 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 Restaking Risk 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.