I-Bond Rate SkillI-Bond Rate Skill

OnlineCredit Usage:1 per callTool:I-BondRateSkill

The tool

Give your agent I-Bond rates. Call it as an MCP tool to read current and historical Series I savings bond rates from the US Treasury.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as I-BondRateSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "I-BondRateSkill",
  "arguments": {}
}

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
periodPremiumstring2024-11Specific issue period to lookup (YYYY-MM format, e.g., 2024-11). Omit for current rates.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "iBonds": {
      "currentRate": 5.27,
      "fixedRate": 1.3,
      "inflationRate": 1.97,
      "purchaseLimit": 10000
    },
    "eeBonds": {
      "currentRate": 2.7,
      "guaranteedDoubling": "20 years (guaranteed to double in value)",
      "purchaseLimit": 10000
    },
    "recommendation": "I Bonds",
    "recommendationReason": "I Bonds currently offer 5.27% vs EE Bonds at 2.70%",
    "nextRateChange": "2024-05-01",
    "lastUpdated": "2024-02-01T00:00:00.000Z"
  }
}

Fields

FieldTypeExampleDescription
iBondsobject{…}
iBonds.currentRatenumber5.27
iBonds.fixedRatenumber1.3Fixed rate component (set at purchase, never changes)
iBonds.inflationRatenumber1.97Inflation rate component (adjusts every 6 months)
iBonds.purchaseLimitnumber10000Annual electronic purchase limit per person in dollars
eeBondsobject{…}
eeBonds.currentRatenumber2.7
eeBonds.guaranteedDoublingstring20 years (guaranteed to double in value)
eeBonds.purchaseLimitnumber10000Annual electronic purchase limit per person in dollars
recommendationstringI Bonds
recommendationReasonstringI Bonds currently offer 5.27% vs EE Bonds at 2.70%
nextRateChangestring2024-05-01Date of next scheduled I-Bond rate announcement
lastUpdatedstring2024-02-01T00:00:00.000ZISO 8601 timestamp of last data refresh

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use I-Bond Rate Skill

Set up I-Bond Rate Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use I-BondRateSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?