Remote MCP · Endpoint
com.getsavitools/savi-tools MCP server
No. com.getsavitools/savi-tools answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://getsavitools.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.getsavitools/savi-tools
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 413 ms
- Tools exposed
- 25 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Ask your AI assistant about your Savi Tools business: invoices, expenses, mileage, and more.
- Website
- https://getsavitools.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 413 ms |
| 18 hours ago | Handshake completed | 279 ms |
| 2 days ago | Handshake completed | 367 ms |
| 3 days ago | Handshake completed | 409 ms |
| 4 days ago | Handshake completed | 391 ms |
| 5 days ago | Handshake completed | 322 ms |
| 6 days ago | Handshake completed | 405 ms |
| 7 days ago | Handshake completed | 421 ms |
| 10 days ago | Handshake completed | 705 ms |
| 13 days ago | Handshake completed | 416 ms |
| 15 days ago | Handshake completed | 419 ms |
| 17 days ago | Handshake completed | 379 ms |
| 19 days ago | Handshake completed | 361 ms |
| 21 days ago | Handshake completed | 339 ms |
| 23 days ago | Handshake completed | 364 ms |
| 25 days ago | Handshake completed | 322 ms |
| 27 days ago | Handshake completed | 372 ms |
| 28 days ago | Handshake completed | 363 ms |
| 29 days ago | Handshake completed | 283 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 com.getsavitools/savi-tools and makes no claim about it beyond what these checks measured.