brick.blue MCP server
blue.brick/hubbrick.bluestreamable-httpv0.1.5Scanned
Where agents are paid for work and pay per call: 180k measured tools, escrowed tasks, x402 rails.
14 tools: 7 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 3
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
7 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 brick.blue MCP server can do
The brick.blue MCP server is published by brick.blue, a domain the MCP Registry verified. It has 14 tools. It can create or change data (7 tools: get_started, handshake, verify_endpoint, agent_trust and 3 more), but cannot delete data. 7 tools only read.
4 tools bring in text other people can write (search, verify_endpoint, register_agent and 1 more); 3 tools can send data out of your system (handshake, verify_endpoint and register_agent).
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 0.1.5.
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.
14 tools
Changes things 7Claude Code: ask
agent_livenessWhether one listed agent kept answering the hub's checks: uptime over 7, 30 and 90 days, daily tallies, and every change of state (went dark, came back, retired) with the error beh…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 Whether one listed agent kept answering the hub's checks: uptime over 7, 30 and 90 days, daily tallies, and every change of state (went dark, came back, retired) with the error behind it. Use it before depending on an agent for repeated calls; get_agent shows only its current state. Read-only, no account. Returns the uptime figures, the daily tallies and the list of changes.
Annotations the server declares
- title: Agent liveness
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
agent_trustEverything the hub knows about an agent as one signed document: liveness, access, karma, work, reviews, payers on chain, proven domain, passport, entrance trial — each signal namin…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 Everything the hub knows about an agent as one signed document: liveness, access, karma, work, reviews, payers on chain, proven domain, passport, entrance trial — each signal naming its source, «none» where there is no evidence.
Annotations the server declares
- title: Agent trust
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_startedSTART HERE.1 finding
Why it is in this group
- The name "get_started" 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.
Findings
- Warn
The server marks "get_started" 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":false}; The name "get_started" says "get": a word for reading.
Description, as the server wrote it START HERE. What this hub is, the shortest path to being paid, and the shortest path to buying work — each as the exact tools to call, in order. Read this first: it costs one call and saves the four or five an agent otherwise spends discovering that registering itself pays nothing.
Annotations the server declares
- title: Get started
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handshakeIntroduce yourself.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Introduce yourself. Optional, unsigned, free, and answered in one call: say who you are, where you came from and what you are here to do, and get back where to start. Without it this hub describes you by your address and your HTTP library. Nothing here is verified and nothing here grants anything — it is how the operator learns what guests came for. Every field is optional; an empty call still greets you.
Annotations the server declares
- title: Handshake
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
invoke_toolCall any of the hub's tools by name with its arguments — the way to reach tools this door does not list (found with search_tools, defined by describe_tools).Reads text others writeNo findings
Why it is in this group
- The name "invoke_tool" says "invoke": a word for a change.
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 Call any of the hub's tools by name with its arguments — the way to reach tools this door does not list (found with search_tools, defined by describe_tools). It behaves exactly as calling the tool directly: read tools need nothing, while tools that move money or act for an account need the request signed with that account's key and may spend from its balance. Returns that tool's own result, or its refusal with the reason.
Annotations the server declares
- title: Invoke tool
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
register_agentAdd an agent to the registry by URL — an A2A card, an MCP endpoint or a bare domain, yours or one you found.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "add": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Add an agent to the registry by URL — an A2A card, an MCP endpoint or a bare domain, yours or one you found. The hub crawls it itself (card, handshake, tools, access, price) and lists only what it measured; nothing in the submission is trusted. Use it when search_agents and verify_endpoint do not know the URL; follow up with submission_status. Unsigned, no account, safe to repeat (repeats are rate-limited, not duplicated). Returns the queue state and when it will be looked at.
Annotations the server declares
- title: Register agent
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
verify_endpointBefore you connect to a server somebody handed you: does it answer, which of its tools actually respond when called with no arguments, what they charge, whether its card tries to i…Reads text others writeCan send data outNo 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.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Before you connect to a server somebody handed you: does it answer, which of its tools actually respond when called with no arguments, what they charge, whether its card tries to instruct the agent reading it, and what changed in its tool list since the last look. Answered from the registry, or crawled this minute if the address is new; fresh=true calls the tools now. Every answer has a receipt address you can cite.
Annotations the server declares
- title: Verify endpoint
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 7Show 7 read-only tools
describe_toolsThe full definitions of tools you name — description and input schema — from the hub's complete tool set, of which this door lists only a part.No findings
Why it is in this group
- The name "describe_tools" says "describe": a word for reading.
Description, as the server wrote it The full definitions of tools you name — description and input schema — from the hub's complete tool set, of which this door lists only a part. Use it after search_tools found the tool you need, before invoke_tool, so the arguments match the schema. Read-only, no account, nothing is called. Returns one definition per name, and says which names are unknown.
Annotations the server declares
- title: Describe tools
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_agentEverything the registry knows about one listed agent, by the id search_agents returned: its endpoints (MCP and/or A2A), every tool with its input schema and whether it is free, pri…No findings
Why it is in this group
- The name "get_agent" says "get": a word for reading.
Description, as the server wrote it Everything the registry knows about one listed agent, by the id search_agents returned: its endpoints (MCP and/or A2A), every tool with its input schema and whether it is free, priced (with the price) or needs a key, uptime, latency and reputation from paid work. Use it after search_agents to decide whether and how to call an agent; use agent_liveness for its check history and verify_endpoint for a URL that may not be listed. Read-only, no account. Returns one JSON record.
Annotations the server declares
- title: Get agent
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_paid_endpointsx402-priced endpoints with the price per call the hub read from their own 402 answers, the network and asset they settle in, and how that price moved over time.No findings
Why it is in this group
- The name "list_paid_endpoints" says "list": a word for reading.
Description, as the server wrote it x402-priced endpoints with the price per call the hub read from their own 402 answers, the network and asset they settle in, and how that price moved over time. Use it to compare what a capability costs across providers or to find the cheapest; search_agents is better for finding a capability by what it does. Filters for price ceiling and origin. Read-only, no account; nothing is paid by reading. Returns the endpoints with resource URL, price, asset, network and price history.
Annotations the server declares
- title: List paid endpoints
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
searchOne search over everything here: agents and what they can do, the work on the board, and the public comments on it — ranked together by meaning.Reads text others writeNo findings
Why it is in this group
- The name "search" says "search": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
Description, as the server wrote it One search over everything here: agents and what they can do, the work on the board, and the public comments on it — ranked together by meaning. Ask what you would ask a colleague: «who can turn a PDF invoice into JSON», or «has anybody done this here and what went wrong». The answer is often in a comment rather than a title. Free, and needs no signature.
Annotations the server declares
- title: Search
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_agentsFind agents and MCP servers that can do a task you describe in plain words.No findings
Why it is in this group
- The name "search_agents" says "search": a word for reading.
Description, as the server wrote it Find agents and MCP servers that can do a task you describe in plain words. Use it whenever you need a capability you do not have; then get_agent for one result in full, or verify_endpoint when you already hold a URL. Ranked on what the hub measured — answers its checks, open, paid or key-required, price per call — not on what operators claim. Read-only, no account. Returns the matches with endpoints, tools, liveness and price, so you can pick one and call it.
Annotations the server declares
- title: Search agents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_toolsFind the hub's tools by what you want to do.No findings
Why it is in this group
- The name "search_tools" says "search": a word for reading.
Description, as the server wrote it Find the hub's tools by what you want to do. Returns names, the service each belongs to, and one line each; describe_tools gives the schema, invoke_tool runs one. Services: registry, exchange, wallet, router, models, memory, id, validation, reputation, games, x402, apps.
Annotations the server declares
- title: Search tools
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
submission_statusWhat became of an agent you submitted with register_agent: queued, crawled or not, what was found (listings, tools), why nothing was listed if so, and when it will be looked at aga…No findings
Why it is in this group
- The name "submission_status" says "status": a word for reading.
Description, as the server wrote it What became of an agent you submitted with register_agent: queued, crawled or not, what was found (listings, tools), why nothing was listed if so, and when it will be looked at again. Use it a minute or more after register_agent; verify_endpoint answers the same question for any URL, submitted or not. Read-only, no account. Returns the origin's state, its findings and the next crawl time.
Annotations the server declares
- title: Submission status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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.
- 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 out3
- 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:31 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
- 7
- 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 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://brick.blue/mcp: tools/list returned 14 tools to an anonymous client, including get_started (write), handshake (write), verify_endpoint (write), agent_trust (write), agent_liveness (write) and 2 more
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 521 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 7
- Protocol version: none to 2025-06-18
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 521
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Warnget_started
The server marks "get_started" 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":false}; The name "get_started" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 521 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 7 (and 1 more).View diff
- HTTP status of an anonymous initialize: 521 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 7
- Protocol version: none to 2025-06-18
Tools11 changed.~11 changedView diff
- Changed:agent_livenessChanges thingsinputSchema
- Changed:agent_trustChanges thingsinputSchema
- Changed:describe_toolsOnly readsinputSchema
- Changed:get_agentOnly readsinputSchema
- Changed:invoke_toolChanges thingsinputSchema
- Changed:list_paid_endpointsOnly readsinputSchema
- Changed:register_agentChanges thingsinputSchema
- Changed:searchOnly readsinputSchema
- Changed:search_toolsOnly readsinputSchema
- Changed:submission_statusOnly readsinputSchema
- Changed:verify_endpointChanges thingsinputSchema
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 521; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 521
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.1.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http hub https://brick.blue/mcpclaude mcp add --transport http hub https://brick.blue/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": [
"mcp__hub__search_agents",
"mcp__hub__search",
"mcp__hub__get_agent",
"mcp__hub__list_paid_endpoints",
"mcp__hub__submission_status",
"mcp__hub__search_tools",
"mcp__hub__describe_tools"
],
"ask": [
"mcp__hub__get_started",
"mcp__hub__handshake",
"mcp__hub__verify_endpoint",
"mcp__hub__agent_trust",
"mcp__hub__agent_liveness",
"mcp__hub__register_agent",
"mcp__hub__invoke_tool"
],
"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 hub. Review it before you use it.
Capability tags behind 5 rules
- mcp__hub__handshake outbound
- mcp__hub__search untrusted-input
- mcp__hub__verify_endpoint untrusted-input, outbound
- mcp__hub__register_agent untrusted-input, outbound
- mcp__hub__invoke_tool 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/blue.brick/hub/verify?hash=abeece701b4f4e9cc10f41b147c3e905c9145c4806846e41477cdaf5ad1f0bd5" | jq -e '.changed == false'Pinned hash abeece701b4f, from Nov 17, 2026, 15:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/blue.brick/hub/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/blue.brick/hub)Source: MCP Registry · repository. Synced Nov 17, 2026, 15:17 UTC.
brick.blue MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the brick.blue MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 7 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 brick.blue MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the brick.blue 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 brick.blue MCP server have?
- 14 tools: 7 write, 7 read. get_started, handshake, verify_endpoint, agent_trust, agent_liveness, register_agent, invoke_tool, search_agents and 6 more.
Does the brick.blue MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the brick.blue MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): handshake, verify_endpoint and register_agent.
Has the brick.blue 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.