Routing Number Lookup SkillRouting Number Lookup Skill

OnlineCredit Usage:5 per callTool:RoutingNumberLookupSkill

The tool

Let your agent resolve US bank routing numbers. Call it as an MCP tool to return the bank name, state and location for any ABA number.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as RoutingNumberLookupSkill. 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": "RoutingNumberLookupSkill",
  "arguments": {
    "routing": "121000358"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about 121000358 in the terms this source covers is enough for it to reach for RoutingNumberLookupSkill on its own.

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
routingRequiredstring121000358The routing number to lookup information about

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": {
    "routing_number": "121000358",
    "office_code": "O",
    "record_type_code": "1",
    "new_routing_number": "000000000",
    "bank": "BANK OF AMERICA, N.A.",
    "address": "8001 VILLA PARK DRIVE",
    "city": "HENRICO",
    "state": "VA",
    "zip": "23228",
    "zip_extension": "0000",
    "country": "US",
    "federal_reserve_district": "San Francisco",
    "routing_type": "primary",
    "is_valid_checksum": true,
    "routing_analysis": {
      "is_head_office": true,
      "is_branch": false,
      "is_federal_reserve_bank": false,
      "is_active": true,
      "replaced_by": null
    }
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
routing_numberstring121000358The ABA routing number for the bank
office_codePremiumstringOOffice code designating the main office or branch location
record_type_codePremiumstring1Record type code indicating transaction type classification
new_routing_numberPremiumstring000000000New routing number if the bank has been updated
bankstringBANK OF AMERICA, N.A.Name of the financial institution or bank
addressPremiumstring8001 VILLA PARK DRIVEStreet address of the bank's main office location
cityPremiumstringHENRICOCity where the bank is located
statestringVATwo-letter state abbreviation of bank location
zipPremiumstring23228Five-digit postal code of bank location
zip_extensionPremiumstring0000Four-digit ZIP code extension for more precise location
countrystringUSCountry code (ISO 3166-1 alpha-2 format)
federal_reserve_districtstringSan FranciscoFederal Reserve district (e.g. San Francisco) derived from the routing number's first two digits; null for government or traveler's-cheque prefixes
routing_typestringprimaryRouting category derived from the routing number prefix: primary, thrift, electronic, government, or travelers_cheque
is_valid_checksumbooleantrueWhether the routing number passes the ABA mod-10 checksum
routing_analysisPremiumobject{…}Plain-language interpretation of the FRB office and record-type codes: head office vs branch, whether it is a Federal Reserve Bank, active vs superseded, and the replacement routing number if the institution was reassigned
routing_analysis.is_head_officebooleantrue
routing_analysis.is_branchbooleanfalse
routing_analysis.is_federal_reserve_bankbooleanfalse
routing_analysis.is_activebooleantrue
routing_analysis.replaced_byobjectnull

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 Routing Number Lookup Skill

Set up Routing Number Lookup 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 RoutingNumberLookupSkill?

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?

5 credits 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?