Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.bobross2020/brickpulse-mcp

REMOTE · MCP.BRICKPULSE.AI · 2 COMPONENTS · SCANNED AUG 3

Query LEGO set details, retirement dates, deals, and price history from BrickPulse.ai

+3 this week 67 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 519 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.brickpulse.ai

# add to Claude Code
claude mcp add --transport http bobross2020-brickpulse-mcp https://mcp.brickpulse.ai/mcp
# ~/.codex/config.toml
[mcp_servers.bobross2020-brickpulse-mcp]
url = "https://mcp.brickpulse.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bobross2020-brickpulse-mcp": {
      "type": "remote",
      "url": "https://mcp.brickpulse.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bobross2020-brickpulse-mcp --url https://mcp.brickpulse.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  bobross2020-brickpulse-mcp:
    url: "https://mcp.brickpulse.ai/mcp"
// mcp.json
{
  "mcpServers": {
    "bobross2020-brickpulse-mcp": {
      "type": "http",
      "url": "https://mcp.brickpulse.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.brickpulse.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=brickpulse.ai CN=WE1,O=Google Trust Services,C=US 15 Jun 2026 13 Sept 2026 ECDSA 256 ECDSA-SHA256 64d83cba24a3edc00e656f17d5df8b45
SANs: brickpulse.ai, *.brickpulse.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of mcp.brickpulse.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
brickpulse.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.brickpulse.ai/mcp Verified 200
http (plaintext) http://mcp.brickpulse.ai/mcp HTTPS enforced 301 https://mcp.brickpulse.ai/mcp
MCP tools — 5 exposed · ~437 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
get_deals ~95

Find the best current LEGO deals — sets selling below RRP at major retailers. Returns sets ranked by discount percentage.

NameTypeReqDescription
limitnumberNumber of results (max 25)
minDiscountnumberMinimum discount percentage (default 10%)
retailerstringFilter by retailer (e.g. 'Amazon', 'Walmart', 'Target')
themestringFilter by theme name

No output schema declared.

No examples provided.

get_price_history ~78

Get price history and trends for a LEGO set across retailers over a given time period.

NameTypeReqDescription
daysnumberLookback period in days (default 90)
retailerstringFilter to a specific retailer
setNumstringyesSet number (e.g. '75313' or '75313-1')

No output schema declared.

No examples provided.

get_retiring_soon ~79

Find LEGO sets retiring soon. Useful for collectors who want to buy before sets become unavailable and prices increase on the secondary market.

NameTypeReqDescription
daysAheadnumberHow many days ahead to look (default 180)
limitnumberNumber of results (max 50)
themestringFilter by theme name

No output schema declared.

No examples provided.

get_set_details ~55

Get full details for a specific LEGO set including current retailer prices, BrickLink market data, and retirement status.

NameTypeReqDescription
setNumstringyesSet number (e.g. '75313' or '75313-1')

No output schema declared.

No examples provided.

search_sets ~130

Search LEGO sets by name, set number, theme, year, or price range. Returns matching sets with key details.

NameTypeReqDescription
limitnumberNumber of results (max 25)
maxPricenumberMaximum RRP in USD
maxYearnumberMaximum release year
minPricenumberMinimum RRP in USD
minYearnumberMinimum release year
querystringSearch by set name or set number
themestringFilter by theme name (e.g. 'Star Wars', 'Technic')

No output schema declared.

No examples provided.