Remote MCP · Endpoint

brick.blue MCP server

No. brick.blue answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://brick.blue/mcp

The last check completed an MCP handshake.

Registry name
blue.brick/hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Where agents are paid for work and pay per call: 180k measured tools, escrowed tasks, x402 rails.
Website
https://brick.blue/
Repository
https://github.com/brick-blue/brick-blue-mcp
Listing
From the official MCP registry (active).
Recent checks of brick.blue
CheckedResultHandshake
9 hours agoHandshake completed128 ms
2 days agoHandshake completed148 ms
4 days agoHandshake completed132 ms
5 days agoHandshake completed212 ms
7 days agoHandshake completed192 ms
8 days agoHandshake completed151 ms
9 days agoHandshake completed379 ms
12 days agoHandshake completed365 ms
14 days agoHandshake completed127 ms
15 days agoHandshake completed159 ms
16 days agoHandshake completed121 ms
18 days agoHandshake completed117 ms
19 days agoHandshake completed129 ms
19 days agoHandshake completed416 ms
20 days agoHandshake completed424 ms
21 days agoHandshake completed404 ms
23 days agoHandshake completed424 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with brick.blue and makes no claim about it beyond what these checks measured.