Remote MCP · Endpoint
Token Counter MCP server
No. Token Counter answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://apished.com/mcp/v1/tokens
The last check completed an MCP handshake.
- Registry name
- com.apished/token-counter
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 363 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 66.7% from 18 checks
- Described by its publisher as
- Counts tokens under OpenAI-compatible (tiktoken) encodings, by model or encoding name.
- Website
- https://apished.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 363 ms |
| 1 day ago | Handshake completed | 369 ms |
| 2 days ago | Handshake completed | 356 ms |
| 3 days ago | Handshake completed | 361 ms |
| 4 days ago | Handshake completed | 688 ms |
| 5 days ago | Handshake completed | 356 ms |
| 6 days ago | Handshake completed | 356 ms |
| 9 days ago | Handshake completed | 370 ms |
| 11 days ago | Handshake completed | 360 ms |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 16 days ago | Handshake completed | 393 ms |
| 18 days ago | Handshake completed | 365 ms |
| 20 days ago | Handshake completed | 367 ms |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 29.
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 Token Counter and makes no claim about it beyond what these checks measured.