brickpulse
Registry code: 8cf1461d4b1c850b
BrickPulse provides real-time LEGO set data, pricing from major retailers (Amazon, Walmart, Target, LEGO.com), BrickLink secondary market data, deals, and retirement info. Use search_sets to find sets, get_set_details for full info on a specific set, get_deals for current discounts, get_retiring_soon for sets about to retire, and get_price_history for price trends.
- endpoint
- https://mcp.brickpulse.ai/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is brickpulse live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is brickpulse free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does brickpulse have?
- 5 tools: search_sets, get_price_history, get_set_details, get_deals, get_retiring_soon.
- Is brickpulse safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- degraded → live
- unknown → live
- used for
- search lego sets
- find lego deals
- get lego price history
- find lego sets retiring soon
- takes → gives
- text → data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_deals reads open 19h ago
Find the best current LEGO deals — sets selling below RRP at major retailers. Returns sets ranked by discount percentage.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "default": 10, "maximum": 25, "minimum": 1, "description": "Number of results (max 25)" }, "theme": { "type": "string", "description": "Filter by theme name" }, "retailer": { "type": "string", "description": "Filter by retailer (e.g. 'Amazon', 'Walmart', 'Target')" }, "minDiscount": { "type": "number", "default": 10, "maximum": 90, "minimum": 1, "description": "Minimum discount percentage (default 10%)" } }, "additionalProperties": false }arguments 29 linesget_retiring_soon reads open 19h ago
Find LEGO sets retiring soon. Useful for collectors who want to buy before sets become unavailable and prices increase on the secondary market.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "default": 15, "maximum": 50, "minimum": 1, "description": "Number of results (max 50)" }, "theme": { "type": "string", "description": "Filter by theme name" }, "daysAhead": { "type": "number", "default": 180, "maximum": 365, "minimum": 1, "description": "How many days ahead to look (default 180)" } }, "additionalProperties": false }arguments 25 linessearch_sets reads unknown never probed
Search LEGO sets by name, set number, theme, year, or price range. Returns matching sets with key details.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "default": 10, "maximum": 25, "minimum": 1, "description": "Number of results (max 25)" }, "query": { "type": "string", "description": "Search by set name or set number" }, "theme": { "type": "string", "description": "Filter by theme name (e.g. 'Star Wars', 'Technic')" }, "maxYear": { "type": "number", "description": "Maximum release year" }, "minYear": { "type": "number", "description": "Minimum release year" }, "maxPrice": { "type": "number", "description": "Maximum RRP in USD" }, "minPrice": { "type": "number", "description": "Minimum RRP in USD" } }, "additionalProperties": false }arguments 38 linesget_price_history reads unknown 19h ago
Get price history and trends for a LEGO set across retailers over a given time period.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "setNum" ], "properties": { "days": { "type": "number", "default": 90, "maximum": 365, "minimum": 1, "description": "Lookback period in days (default 90)" }, "setNum": { "type": "string", "description": "Set number (e.g. '75313' or '75313-1')" }, "retailer": { "type": "string", "description": "Filter to a specific retailer" } }, "additionalProperties": false }arguments 25 linesget_set_details reads unknown never probed
Get full details for a specific LEGO set including current retailer prices, BrickLink market data, and retirement status.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "setNum" ], "properties": { "setNum": { "type": "string", "description": "Set number (e.g. '75313' or '75313-1')" } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8cf1461d4b1c850b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8cf1461d4b1c850b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8cf1461d4b1c850b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.