Remote MCP · Endpoint
itemnumbers MBS schedule MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://itemnumbers.app/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- app.itemnumbers/itemnumbers-mbs
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 40.0% from 5 checks
- Described by its publisher as
- Read-only Medicare Benefits Schedule lookup: items, history, relationships and combinations.
- Website
- https://itemnumbers.app/
- Repository
- https://github.com/maxand98/item-ai
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Handshake completed | 774 ms |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 708 ms |
| 4 days ago | Failed - the server returned an HTTP error | — |
The last 5 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 5.
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 itemnumbers MBS schedule and makes no claim about it beyond what these checks measured.