Remote MCP · Endpoint
io.github.DataLeadsPRO/ai-model-pricing MCP server
No. io.github.DataLeadsPRO/ai-model-pricing answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://data.dataleads.pro/mcp/ai-model-pricing
The last check completed an MCP handshake.
- Registry name
- io.github.DataLeadsPRO/ai-model-pricing
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 322 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Live pricing data for AI models across vendors: input/output prices per 1k tokens as JSON.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 322 ms |
| 1 day ago | Handshake completed | 355 ms |
| 2 days ago | Handshake completed | 329 ms |
| 3 days ago | Handshake completed | 324 ms |
| 4 days ago | Handshake completed | 355 ms |
| 5 days ago | Handshake completed | 333 ms |
| 6 days ago | Handshake completed | 287 ms |
| 9 days ago | Handshake completed | 292 ms |
| 11 days ago | Handshake completed | 291 ms |
| 14 days ago | Handshake completed | 283 ms |
| 16 days ago | Handshake completed | 458 ms |
| 18 days ago | Handshake completed | 285 ms |
| 20 days ago | Handshake completed | 310 ms |
| 22 days ago | Handshake completed | 312 ms |
| 24 days ago | Handshake completed | 388 ms |
| 26 days ago | Handshake completed | 280 ms |
| 27 days ago | Handshake completed | 345 ms |
| 29 days ago | Handshake completed | 318 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 io.github.DataLeadsPRO/ai-model-pricing and makes no claim about it beyond what these checks measured.