Remote MCP · Endpoint
Bloom MCP Server and API by Cotlet MCP server
No. Bloom MCP Server and API by Cotlet answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://cotlet.dev/mcp/v1/bloom
The last check completed an MCP handshake.
- Registry name
- dev.cotlet/bloom
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 151 ms
- Tools exposed
- 32 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Bloom creative business CRM MCP server: create lead, create project, send invoice, send contract.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 151 ms |
| 4 days ago | Handshake completed | 168 ms |
| 7 days ago | Handshake completed | 160 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 Bloom MCP Server and API by Cotlet and makes no claim about it beyond what these checks measured.