Docs/Sources/IFSC Code Grounding Data

IFSC Code Grounding Data

Get IFSC code information

OperationalCredits 10 per callp50 1289msFinance

Overview

Pass any valid 11-character IFSC code to fetch registered branch information. The lookup checks weekly updated banking records to return the institution name, branch address, contact details, city, district, and state. Paid plans also return MICR, SWIFT codes, and payment rail flags including IMPS, RTGS, NEFT, and UPI.

Live Test IFSC Code Grounding Data Source →

The tool

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

Tool call
{
  "name": "IFSCCodeGroundingData",
  "arguments": {
    "ifsc": "SBIN0005943"
  }
}

You do not name the tool yourself; the model picks it. Asking about SBIN0005943 in the terms this source covers is enough for it to reach for IFSCCodeGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source 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.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, 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. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
ifscRequiredstringThe IFSC code to get information about

What the model gets back

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

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "bank": "State Bank of India",
    "ifsc": "SBIN0005943",
    "branch": "KASTURBA GANDHI MARG,NEW DELHI",
    "address": "23, HIMALAYA HOUSE KASTURBA GANDHI MARG NEW DELHI ,PIN - 110001",
    "contact": "",
    "city": "NEW DELHI",
    "district": "NEW DELHI",
    "state": "DELHI",
    "imps": true,
    "rtgs": true,
    "neft": true,
    "upi": true,
    "micr": "110002062",
    "swift": ""
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
bankstringState Bank of IndiaName of the bank institution
ifscstringSBIN0005943IFSC code of the branch
branchstringKASTURBA GANDHI MARG,NEW DELHIBranch name and address location
addressstring23, HIMALAYA HOUSE KASTURBA GANDHI MARG NEW DELHI ,PIN - 110001Street address of the branch
contactstringContact information for the branch
citystringNEW DELHICity where the branch is located
districtstringNEW DELHIDistrict of the branch location
statestringDELHIState where the branch is located
impsPremiumbooleantrueWhether IMPS transactions are supported
rtgsPremiumbooleantrueWhether RTGS transactions are supported
neftPremiumbooleantrueWhether NEFT transactions are supported
upiPremiumbooleantrueWhether UPI transactions are supported
micrPremiumstring110002062MICR code for the branch
swiftPremiumstringSWIFT code for international transactions

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at bank: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This source is not part of VerveContext. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Vendor Payout Verification
When onboarding Indian vendors, accounts payable teams confirm the bank name and branch location against supplied payout details before issuing wire transfers.
Checkout Routing
Fintech checkout forms auto-populate branch, city, and state values as soon as a customer enters their IFSC code.
Payroll Account Auditing
Audit employee direct deposit submissions by validating branch addresses and districts to reduce payout rejections from incorrect bank routing codes.
Merchant Settlement Setup
Payment gateways check branch credentials during merchant onboarding to verify account legitimacy before enabling settlement processing.

Other ways to use IFSC Code Grounding Data

Set up IFSC Code Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext 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.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Finance:

Was this page helpful?