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.
Listing
From the official MCP registry (active).
Recent checks of AccountsOS
CheckedResultHandshake
3 hours agoHandshake completed374 ms
4 days agoHandshake completed281 ms
14 days agoHandshake completed533 ms
15 days agoHandshake completed267 ms
15 days agoHandshake completed233 ms
17 days agoHandshake completed382 ms
18 days agoHandshake completed225 ms
19 days agoHandshake completed245 ms
20 days agoHandshake completed334 ms
21 days agoHandshake completed333 ms
23 days agoHandshake completed1.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.