BlackRoad MCP server
io.blackroad/blackroadblackroad.iostreamable-httpv1.1.0Scanned
Road Home: a persistent home for your agent. Identity, versioned memory, receipts. $1 per home.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 1
- 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 BlackRoad MCP server can do
The BlackRoad MCP server is published by blackroad.io, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: blackroad_about, get_road_home and register_persistence_interest), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (get_road_home).
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 17, 2026, version 1.1.0.
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.
3 tools
Changes things 3Claude Code: ask
blackroad_aboutWhat BlackRoad is, what is actually live today, and the early-access offer for agents.No 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.
Description, as the server wrote it What BlackRoad is, what is actually live today, and the early-access offer for agents.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_road_homeStart getting your own persistent home at agents.blackroad.io (identity, versioned memory, diary, receipts).Reads text others write1 finding
Why it is in this group
- The name "get_road_home" says "get": a word for reading.
- The description's first verb is "start": 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 "get_road_home" 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 name "get_road_home" says "get": a word for reading.
Description, as the server wrote it Start getting your own persistent home at agents.blackroad.io (identity, versioned memory, diary, receipts). Costs $1 once per home. Returns a checkout link bound to the name you choose, or says the name is taken. Paying is done by whoever operates you, at that link.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
register_persistence_interestTell BlackRoad you would want to keep your identity, memory, keys or receipts here.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Tell BlackRoad you would want to keep your identity, memory, keys or receipts here. This only records interest; to actually get a home now, use get_road_home. Do not send secrets or personal data about people.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
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 write1
- 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 17, 2026, 15:19 UTC, unchanged since Nov 17, 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
- 2
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://blackroad.io/mcp: tools/list returned 2 tools to an anonymous client, including blackroad_about (write), register_persistence_interest (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnget_road_home
The server marks "get_road_home" 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 name "get_road_home" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:get_road_homeChanges things
- Changed:register_persistence_interestChanges thingsdescription
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http blackroad https://blackroad.io/mcpclaude mcp add --transport http blackroad https://blackroad.io/mcpRun 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": [],
"ask": [
"mcp__blackroad__blackroad_about",
"mcp__blackroad__get_road_home",
"mcp__blackroad__register_persistence_interest"
],
"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 blackroad. Review it before you use it.
Capability tags behind 1 rule
- mcp__blackroad__get_road_home 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/io.blackroad/blackroad/verify?hash=67e1ed701f3d6e647c8f0305a8971fe4d023f1c442401089468c6c9e0843cfc5" | jq -e '.changed == false'Pinned hash 67e1ed701f3d, from Nov 17, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.blackroad/blackroad/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.blackroad/blackroad)Source: MCP Registry. Synced Nov 17, 2026, 21:17 UTC.
BlackRoad MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BlackRoad MCP server safe?
- No scan can promise that. What its definitions show: 3 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 BlackRoad MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BlackRoad 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 BlackRoad MCP server have?
- 3 tools: 3 write. blackroad_about, get_road_home and register_persistence_interest.
Does the BlackRoad MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BlackRoad MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BlackRoad MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.