Remote MCP · Endpoint
Brasspage MCP server
No. Brasspage answered an MCP handshake 39 minutes ago.
UpLast checked 39 minutes ago
Server URL
https://brasspage.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.brasspage/brasspage
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 159 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Free small business website check, free redesign form link, Tack Board pin link, live numbers
- Website
- https://brasspage.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 39 minutes ago | Handshake completed | 159 ms |
| 3 days ago | Handshake completed | 226 ms |
| 13 days ago | Handshake completed | 420 ms |
| 13 days ago | Handshake completed | 314 ms |
| 15 days ago | Handshake completed | 240 ms |
| 16 days ago | Handshake completed | 257 ms |
| 17 days ago | Handshake completed | 316 ms |
| 18 days ago | Handshake completed | 195 ms |
| 18 days ago | Handshake completed | 277 ms |
| 20 days ago | Handshake completed | 296 ms |
| 22 days ago | Handshake completed | 441 ms |
| 25 days ago | Handshake completed | 261 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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.
Listing data comes from the official MCP registry. Glide is not affiliated with Brasspage and makes no claim about it beyond what these checks measured.