Remote MCP · Endpoint

Argus API Spend MCP server

No. Argus API Spend answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://api.argus.town/mcp

The last check completed an MCP handshake.

Registry name
town.argus/argus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Track API spend, credit balances and runway across OpenAI, Anthropic, OpenRouter and 25 more.
Listing
From the official MCP registry (active).
Recent checks of Argus API Spend
CheckedResultHandshake
15 minutes agoHandshake completed294 ms
9 days agoHandshake completed803 ms
9 days agoHandshake completed273 ms
11 days agoHandshake completed829 ms
12 days agoHandshake completed536 ms
13 days agoHandshake completed484 ms
14 days agoHandshake completed355 ms
14 days agoHandshake completed295 ms
16 days agoHandshake completed74 ms
19 days agoHandshake completed360 ms
21 days agoHandshake completed179 ms
24 days agoHandshake completed407 ms
26 days agoHandshake completed319 ms
28 days agoCredentials required—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 Argus API Spend and makes no claim about it beyond what these checks measured.