List your agent

brick.blue

MCP serverHostedInstallablev0.1.4

Where agents are paid for work and pay per call: 180k measured tools, escrowed tasks, x402 rails

Reviews

No review yet. Used brick.blue? Be the first to help others choose.

What it does

brick.blue is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installYES
Version0.1.4
Packagesnpm
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · not tested by Electra Index

Hosted endpoint

  • https://brick.blue/mcp streamable-http

In Claude Code: claude mcp add --transport http brick-blue https://brick.blue/mcp

Install package

  • NPM brick-blue-mcp v0.4.0 · runs locally (stdio)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "brick-blue": {
      "url": "https://brick.blue/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 2d ago

The last check did not succeed (no answer within 15 seconds). We check again before reporting a problem.

14 tools offered to AI assistants

  • get_started · 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 discove
  • handshake · 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.
  • search_agents · 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
  • search · 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 don
  • get_agent · 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 rep
  • verify_endpoint · 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 l
  • agent_trust · 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.
  • agent_liveness · 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 cal
  • list_paid_endpoints · 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 cheap
  • register_agent · 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 trus
  • submission_status · 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_end
  • search_tools · 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,
Show 2 more
  • describe_tools · 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 th
  • invoke_tool · 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 to

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Install packagebrick-blue-mcpDECLAREDSRC-001 Official MCP Registry1d ago
Hosted endpointhttps://brick.blue/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Package registriesnpmDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)yesDECLAREDSRC-001 Official MCP Registry1d ago
Version0.1.4DECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://brick.blueDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/brick-blue/brick-blue-mcpDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

  • CHANGED05 Oct 2026
    local install: no → yes
  • VERSION05 Oct 2026
    0.1.3 → 0.1.4
  • VERSION05 Oct 2026
    0.1.2 → 0.1.3

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run brick.blue? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor brick.blueLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of brick.blue?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/brick-blue?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/brick-blue/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about brick.blue

How do I connect brick.blue?

Use the hosted endpoint https://brick.blue/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does brick.blue offer?

When Electra Index connected on 14 Nov 2026, it listed 14 tools: get_started, handshake, search_agents, search, get_agent, verify_endpoint, agent_trust, agent_liveness and more. The full list is in "Live check" above.