I Bond Rate MCP
REMOTE · I-BOND-RATE-MCP.LIPMICHAL.WORKERS.DEV
Current I bond rate, what your I bond earns by issue month, and value estimates from TreasuryDirect.
Available components
Last scanned (19 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 660 tokens (~132/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 Management53
- Stability observed for 16 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://i-bond-rate-mcp.lipmichal.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lipmichal.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ebf145553d5751d20e0d3cd51e3d7a94 |
| SANs: lipmichal.workers.dev, *.lipmichal.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of i-bond-rate-mcp.lipmichal.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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://i-bond-rate-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://i-bond-rate-mcp.lipmichal.workers.dev/mcp | Inconclusive | 405 |
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 →
calculate_i_bond_composite_rate Calculate I bond composite rate ~95
Apply the Treasury formula fixed + 2 x semiannual inflation + fixed x semiannual inflation, rounded to 0.01 percent with a floor of zero. Use it for rate predictions.
| Name | Type | Req | Description |
|---|---|---|---|
| fixed_rate | number | yes | Fixed rate in percent, for example 1.4. |
| semiannual_inflation_rate | number | yes | Semiannual inflation rate in percent, for example 2.04. |
No output schema declared.
No examples provided.
estimate_i_bond_value Estimate I bond value ~151
Estimate what I bonds are worth for an issue month and purchase amount at the start of a month: value with all interest and the redemption value after the 3-month penalty for bonds under 5 years. Uses semiannual compounding per $25 with the TreasuryDirect rates. An estimate; Treasury values can differ by cents.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Purchase price in dollars, for example 10000. |
| as_of_month | string | – | Month to evaluate, YYYY-MM. Default: the current month. |
| issue_month | string | yes | Issue month of the bond as YYYY-MM, for example "2023-01". The issue date is the first of the month you bought it. |
No output schema declared.
No examples provided.
get_current_i_bond_rate Get current I bond rate ~105
Current Series I savings bond composite rate, fixed rate and semiannual inflation rate for new purchases, read at call time from the TreasuryDirect "I bonds interest rates" page with the built-in rate chart as fallback. November 2026 to April 2027: 5.51 percent with a 1.40 percent fixed rate. Also returns the next announcement date and the $10,000 limit, 12-month hold and 3-month penalty rules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_i_bond_rate_for_issue_date Get I bond rate for an issue date ~143
For an I bond bought in a given month: its fixed rate, the composite rate it earns in the current (or given) 6-month period, the months its rate changes, whether it can be cashed and the penalty, and every rate period since issue. Computed from the TreasuryDirect rate chart effective November 1, 2026.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_month | string | – | Month to evaluate, YYYY-MM. Default: the current month. |
| issue_month | string | yes | Issue month of the bond as YYYY-MM, for example "2023-01". The issue date is the first of the month you bought it. |
No output schema declared.
No examples provided.
get_i_bond_rate_history Get I bond rate history ~64
Fixed rate for new bonds, semiannual inflation rate and composite rate for every May and November announcement since September 1998, newest first, from the TreasuryDirect rate chart.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many announcements, newest first. Default 20. |
No output schema declared.
No examples provided.
How do I install the I Bond Rate MCP server?
I Bond Rate MCP is a hosted endpoint at https://i-bond-rate-mcp.lipmichal.workers.dev/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 · i-bond-rate-mcp.lipmichal.workers.dev
claude mcp add --transport http theluckystrike-i-bond-rate-mcp 'https://i-bond-rate-mcp.lipmichal.workers.dev/mcp'
What is the I Bond Rate MCP server?
I Bond Rate MCP is listed in the public MCP registry as io.github.theluckystrike/i-bond-rate-mcp. Current I bond rate, what your I bond earns by issue month, and value estimates from TreasuryDirect. This page covers its hosted endpoint (https://i-bond-rate-mcp.lipmichal.workers.dev/mcp).
Is the I Bond Rate MCP server safe to use?
I Bond Rate MCP scores 74 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 I Bond Rate MCP server expose?
I Bond Rate MCP exposes 5 tools: get_current_i_bond_rate, get_i_bond_rate_for_issue_date, estimate_i_bond_value, calculate_i_bond_composite_rate, get_i_bond_rate_history. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.
Does the I Bond Rate MCP server require authentication?
No. We connected to I Bond Rate MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the I Bond Rate MCP server still maintained?
I Bond Rate MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the I Bond Rate MCP server?
VerifyMCP ran 12 checks on I Bond Rate MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about I Bond Rate MCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.