Remote MCP · Endpoint
AccountsOS MCP server
No. AccountsOS answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://accounts-os.com/api/mcp/plugin
The last check completed an MCP handshake.
- Registry name
- io.github.paulgosnell/accountsos-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 374 ms
- Tools exposed
- 86 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Query your live AccountsOS books: balances, transactions, VAT, deadlines, invoices.
- Website
- https://accounts-os.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 374 ms |
| 4 days ago | Handshake completed | 281 ms |
| 14 days ago | Handshake completed | 533 ms |
| 15 days ago | Handshake completed | 267 ms |
| 15 days ago | Handshake completed | 233 ms |
| 17 days ago | Handshake completed | 382 ms |
| 18 days ago | Handshake completed | 225 ms |
| 19 days ago | Handshake completed | 245 ms |
| 20 days ago | Handshake completed | 334 ms |
| 21 days ago | Handshake completed | 333 ms |
| 23 days ago | Handshake completed | 1.88 s |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 AccountsOS and makes no claim about it beyond what these checks measured.