Brickpulse MCP Server
io.github.bobross2020/brickpulse-mcp
answering
Brickpulse MCP is answering right now. Last checked 3 min ago. It exposes 5 tools.
Query LEGO set details, retirement dates, deals, and price history from BrickPulse.ai
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
39 hours of history · worst hour 50%
39 hours agonow
50.3%
Uptime 24h
92 of 183 checks
5
Tools
read from the server
308 ms
Response time
average over 24h
open, no key
Access
streamable-http
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add brickpulse-mcp --transport http https://mcp.brickpulse.ai/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"brickpulse-mcp": {
"url": "https://mcp.brickpulse.ai/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.brickpulse-mcp]
url = "https://mcp.brickpulse.ai/mcp".cursor/mcp.json
{
"mcpServers": {
"brickpulse-mcp": {
"url": "https://mcp.brickpulse.ai/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"brickpulse-mcp": {
"url": "https://mcp.brickpulse.ai/mcp"
}
}
}Available tools 5
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
deals
get_deals
Find the best current LEGO deals — sets selling below RRP at major retailers. Returns sets ranked by discount percentage.
details
get_set_details
Get full details for a specific LEGO set including current retailer prices, BrickLink market data, and retirement status.
price
get_price_history
Get price history and trends for a LEGO set across retailers over a given time period.
retiring
get_retiring_soon
Find LEGO sets retiring soon. Useful for collectors who want to buy before sets become unavailable and prices increase on the secondary market.
sets
search_sets
Search LEGO sets by name, set number, theme, year, or price range. Returns matching sets with key details.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.brickpulse.ai/mcp | streamable-http | answering | 322 ms | 3 min ago |
| https://mcp.brickpulse.ai/sse | sse | answering | 328 ms | 3 min ago |
Brickpulse MCP — questions
Answers built from our own checks of this server.
What can Brickpulse MCP do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_deals, get_price_history, get_retiring_soon, get_set_details, search_sets. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Brickpulse MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 183 checks got a reply (50.3%), average response time 308 ms. The bar chart above shows every period we have measured.
Is Brickpulse MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Brickpulse MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Brickpulse MCP need an API key?
No. Brickpulse MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Brickpulse MCP?
It answers our handshake in 308 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.