itemnumbers MBS schedule
REMOTE · ITEMNUMBERS.APP
Read-only Medicare Benefits Schedule lookup: items, history, relationships and combinations.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 736 tokens (~147/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +49
- HTTPS: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.17 ▲ functional
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 +47
- HTTPS: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 29 Oct 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://itemnumbers.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=itemnumbers.app | CN=YE2,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d96088323cc43ddeb52f3812e48057f3c2 |
| SANs: *.itemnumbers.app, itemnumbers.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of itemnumbers.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| itemnumbers.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://itemnumbers.app/mcp | Verified | 200 | |
| http (plaintext) | http://itemnumbers.app/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_item_combination Check item combination ~171
Compare a set of MBS items for one occasion with the rules written in their descriptors, as schedule reference information: pairs the schedule says are not claimable together, time tiers met or missed, flags for assistant, anaesthetic and hospital-only items, and the multiple operation rule for Group T8 items with the resulting total of schedule fees (a schedule figure, not a patient charge). It reports what the descriptors say and never drops an item; it does not decide what should be billed. Rules the schedule words in ways that are not coded, such as exempt items, are not checked.
| Name | Type | Req | Description |
|---|---|---|---|
| durations | array | – | Minutes the service lasted, only for items whose descriptor has a time tier. |
| item_numbers | array | yes | The items performed on one occasion, 1 to 15 item numbers. |
No output schema declared.
No examples provided.
get_item_history Get item history ~89
Show how one MBS item's descriptor and schedule fee changed across the schedule releases held here, newest first. Use it to answer what an item paid or said on an earlier date. Only the releases ingested are listed; it is not a complete history of the item.
| Name | Type | Req | Description |
|---|---|---|---|
| item_number | string | yes | An MBS item number, 1 to 6 digits, for example 30445. |
No output schema declared.
No examples provided.
get_item_relationships Get item relationships ~100
Show how the schedule itself ties one item to others: items its descriptor (or another item's descriptor) says are not claimable with it, add-on items performed in association with it, and the neighbouring items filed in the same group and subgroup. Each link quotes the descriptor wording and names the item whose descriptor says it.
| Name | Type | Req | Description |
|---|---|---|---|
| item_number | string | yes | An MBS item number, 1 to 6 digits, for example 30445. |
No output schema declared.
No examples provided.
get_mbs_item Get MBS item ~98
Get one MBS item as published: full descriptor, fees and benefits, item type, dates, EMSN cap if any, and what the descriptor itself says: assistant and anaesthetic flags, hospital-only, time tier, and the items it excludes. Every figure comes from the schedule, never from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| item_number | string | yes | An MBS item number, 1 to 6 digits, for example 30445. |
No output schema declared.
No examples provided.
search_mbs_items Search MBS items ~140
Find Medicare Benefits Schedule (MBS) items by item number or by words describing the procedure or service. Returns each match's descriptor, schedule fee and Medicare benefits from the current schedule. Use it first when you have a procedure but not an item number. Never put patient identifiers in the query.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return, 1 to 20. Default 10. |
| query | string | yes | An item number or its start (for example 3038), or a few words naming the procedure or service (for example gallbladder removal). Never include patient names, dates of birth or other identifying deta… |
No output schema declared.
No examples provided.
How do I install the itemnumbers MBS schedule MCP server?
itemnumbers MBS schedule is a hosted endpoint at https://itemnumbers.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · itemnumbers.app
claude mcp add --transport http app-itemnumbers-itemnumbers-mbs 'https://itemnumbers.app/mcp'
What is the itemnumbers MBS schedule MCP server?
itemnumbers MBS schedule is an MCP server listed in the public MCP registry as app.itemnumbers/itemnumbers-mbs. Read-only Medicare Benefits Schedule lookup: items, history, relationships and combinations. This page covers its hosted endpoint (https://itemnumbers.app/mcp).
Is the itemnumbers MBS schedule MCP server safe to use?
itemnumbers MBS schedule scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the itemnumbers MBS schedule MCP server expose?
itemnumbers MBS schedule exposes 5 tools: search_mbs_items, get_mbs_item, get_item_relationships, check_item_combination, get_item_history. Their descriptions and schemas cost roughly 598 tokens of context every time the server is loaded.
Does the itemnumbers MBS schedule MCP server require authentication?
No. We connected to itemnumbers MBS schedule without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the itemnumbers MBS schedule MCP server still maintained?
itemnumbers MBS schedule is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.