Remote MCP · Endpoint

io.github.bobross2020/brickpulse-mcp MCP server

No. io.github.bobross2020/brickpulse-mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.brickpulse.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.bobross2020/brickpulse-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
127 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Query LEGO set details, retirement dates, deals, and price history from BrickPulse.ai
Repository
https://github.com/bobross2020/brickpulse-mcp
Listing
From the official MCP registry (active).
Recent checks of io.github.bobross2020/brickpulse-mcp
CheckedResultHandshake
1 hour agoHandshake completed127 ms
2 days agoHandshake completed165 ms
4 days agoHandshake completed68 ms
5 days agoHandshake completed90 ms
7 days agoHandshake completed113 ms
8 days agoHandshake completed527 ms
9 days agoHandshake completed45 ms
12 days agoHandshake completed56 ms
13 days agoHandshake completed79 ms
15 days agoHandshake completed74 ms
16 days agoHandshake completed86 ms
18 days agoHandshake completed43 ms
19 days agoHandshake completed56 ms
20 days agoHandshake completed45 ms
20 days agoHandshake completed61 ms
21 days agoHandshake completed44 ms
22 days agoHandshake completed463 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 io.github.bobross2020/brickpulse-mcp and makes no claim about it beyond what these checks measured.