Remote MCP · Endpoint
Decision Log MCP server
No. Decision Log answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.decisionlog.ai/api/mcp
The last check completed an MCP handshake.
- Registry name
- ai.decisionlog/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 142 ms
- Tools exposed
- 30 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Append-only decisions with provenance, supersession, retrieval, and audited MCP actions.
- Website
- https://www.decisionlog.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 142 ms |
| 22 hours ago | Handshake completed | 158 ms |
| 2 days ago | Handshake completed | 91 ms |
| 3 days ago | Handshake completed | 131 ms |
| 4 days ago | Handshake completed | 130 ms |
| 5 days ago | Handshake completed | 100 ms |
| 6 days ago | Handshake completed | 141 ms |
| 8 days ago | Handshake completed | 274 ms |
| 11 days ago | Handshake completed | 174 ms |
| 13 days ago | Handshake completed | 96 ms |
| 15 days ago | Handshake completed | 130 ms |
| 18 days ago | Handshake completed | 97 ms |
| 20 days ago | Handshake completed | 320 ms |
| 22 days ago | Handshake completed | 127 ms |
| 24 days ago | Handshake completed | 133 ms |
| 25 days ago | Handshake completed | 104 ms |
| 27 days ago | Handshake completed | 113 ms |
| 29 days ago | Handshake completed | 95 ms |
| 29 days ago | Handshake completed | 83 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 Decision Log and makes no claim about it beyond what these checks measured.