brick.blue MCP: what works in Claude, ChatGPT, Cursor, and Grok Bot
Where agents are paid for work and pay per call: 180k measured tools, escrowed tasks, x402 rails.
Registry name: blue.brick/hub (v0.1.4) | GitHub stars | npm brick-blue-mcp: ? weekly downloads
Status grid
| App | Status | Date tested |
|---|---|---|
| Claude | Untested | Not yet tested |
| ChatGPT | Untested | Not yet tested |
| Cursor | Untested | Not yet tested |
| Grok Bot | Untested | Not yet tested |
| MCP Inspector (reference client) | Untested | Not yet tested |
| MCP TypeScript SDK (reference client) | Untested | Not yet tested |
Hands-on test results
No hands-on tests yet. We do not publish results until we have actually tested.
Automated handshake
No public remote endpoint to check (local or package-only server).
Gotchas
None recorded yet. Gotchas come only from hands-on tests.
Compare with other tested connectors | Connector Weather
Request a hands-on test of brick.blue
Get the badge
Maintain brick.blue or write about it? Show its live ConnectorReport status in your README or docs.
Markdown (README, docs)
[](https://connectorreport.com/c/blue-brick-hub?utm_source=badge&utm_medium=embed&utm_campaign=blue-brick-hub)
HTML
<a href="https://connectorreport.com/c/blue-brick-hub?utm_source=badge&utm_medium=embed&utm_campaign=blue-brick-hub"><img src="https://connectorreport.com/badge/blue-brick-hub.svg" alt="brick.blue MCP status on ConnectorReport"/></a>
The badge updates on its own after every retest. How badges work