ibanforge

Lookup BIC/SWIFT

lookup_bic

Read-onlyIdempotent

Resolve a BIC / SWIFT code into the underlying bank: name, country, city, LEI, and registered head-office address (where available). USE WHEN: the user already has a BIC/SWIFT (8 or 11 chars, alphanumeric, e.g., "UBSWCHZH80A", "DEUTDEFF") and asks which bank it belongs to, where the bank is, or its LEI for compliance/regulatory matching. DO NOT USE for IBAN inputs — call validate_iban instead, it resolves the BIC for you. BACKED BY: BIC directory, 121,000+ entries (entries, not institutions): GLEIF and national registers, refreshed monthly, plus a public copy of the SWIFT directory frozen in January 2018 that still makes up about two thirds of the rows. 39,000+ of the rows carry an LEI from GLEIF. SOURCE: source names the dataset of this row and source_name spells it out; source_as_of is present only when that dataset is a copy frozen at that month (the public copy of the SWIFT directory, frozen in January 2018). listed_in_current_source says whether this BIC8 still appears in a list refreshed this cycle (GLEIF, a national register, the EPC scheme registers, the EBA STEP2 and NBP lists): true when one of them carries it, null when it was not found in what could be read in full. It never answers false today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, which can drop a BIC they carry, so an absence is not proven. It does not prove the bank still exists under this name. COST: $0.003 per call (free with no key on this transport: 25 units a week per source address, one per call and one per IBAN in batch_validate_iban, reset on Monday 00:00 UTC. Or an ifk_ key with no e-mail at all: POST https://api.ibanforge.com/v1/keys/generate with no body for 25 REST calls/month, and POST /v1/keys/claim lifts that same key to 200 a month).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bic`	Yes	BIC/SWIFT code (8 or 11 chars)

Output Schema

TableJSON Schema

Name	Required	Description
`bic`	Yes	Echo of the input, normalized to uppercase.
`lei`	No	Legal Entity Identifier (ISO 17442) if available.
`bic8`	No	8-char form (institution-level).
`city`	No	Null, never an empty string, when the source leaves the town blank.
`bic11`	No	11-char form including branch.
`error`	No
`found`	No	True only when the row names an institution: a record is complete or not found.
`valid`	No	Set when the BIC failed format validation.
`source`	No	Code of the dataset this row comes from.
`country`	No	Same shape as REST GET /v1/bic/:code. name is the row's country name, then the ISO name, and falls back to the country code only when neither exists.
`lei_status`	No
`branch_code`	No
`branch_info`	No
`institution`	No	Bank legal name.
`is_test_bic`	No
`source_name`	No	source names the dataset of this row and source_name spells it out; source_as_of is present only when that dataset is a copy frozen at that month. listed_in_current_source says whether this BIC8 still appears in a list refreshed this cycle (GLEIF, a national register, the EPC scheme registers, the EBA STEP2 and NBP lists): true when one of them carries it, null when it was not found in what could be read in full. It never answers false today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, which can drop a BIC they carry, so an absence is not proven. It does not prove the bank still exists under this name.
`country_code`	No	DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.code.
`country_name`	No	DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which is never null: the row's country name, else the ISO name, else the code.
`source_as_of`	No	Year-month the source DATA is from, present only for a frozen copy.
`valid_format`	No
`listed_in_current_source`	No	Whether this BIC8 still appears in a list refreshed this cycle: GLEIF, the directory sources that carry no vintage, a national register, the EPC scheme registers. true when one of them carries it; null when it was not found in what could be read in full (never false by default). false is reserved for an index built from every list read in full, which is not the case today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, so this field answers true or null. It does NOT prove the bank still exists under this name: a clearing list can keep the name of a bank that was absorbed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 25, 2026

addedOutput schema / properties / city / description

Added value: +"Null, never an empty string, when the source leaves the town blank."

changedOutput schema / properties / country / description

Previous value: -"Same shape as REST GET /v1/bic/:code. name falls back to the country code when the row carries no name."New value: +"Same shape as REST GET /v1/bic/:code. name is the row's country name, then the ISO name, and falls back to the country code only when neither exists."

changedOutput schema / properties / country_name / description

Previous value: -"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which falls back to the code rather than to null."New value: +"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which is never null: the row's country name, else the ISO name, else the code."

addedOutput schema / properties / found / description

Added value: +"True only when the row names an institution: a record is complete or not found."

addedOutput schema / properties / listed_in_current_source

Added value: +{
+  "description": "Whether this BIC8 still appears in a list refreshed this cycle: GLEIF, the directory sources that carry no vintage, a national register, the EPC scheme registers. true when one of them carries it; null when it was not found in what could be read in full (never false by default). false is reserved for an index built from every list read in full, which is not the case today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, so this field answers true or null. It does NOT prove the bank still exists under this name: a clearing list can keep the name of a bank that was absorbed.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / source

Added value: +{
+  "description": "Code of the dataset this row comes from.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / source_as_of

Added value: +{
+  "description": "Year-month the source DATA is from, present only for a frozen copy.",
+  "type": "string"
+}

addedOutput schema / properties / source_name

Added value: +{
+  "description": "source names the dataset of this row and source_name spells it out; source_as_of is present only when that dataset is a copy frozen at that month. listed_in_current_source says whether this BIC8 still appears in a list refreshed this cycle (GLEIF, a national register, the EPC scheme registers, the EBA STEP2 and NBP lists): true when one of them carries it, null when it was not found in what could be read in full. It never answers false today: the EBA STEP2 and NBP lists are only read through our deduplicated directory, which can drop a BIC they carry, so an absence is not proven. It does not prove the bank still exists under this name.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed12 schema fields changedSep 2, 2026

removedOutput schema / properties / branch_info / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / branch_info / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / city / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / city / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / country_name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / country_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / institution / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / institution / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / lei / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / lei / type

Added value: +[
+  "string",
+  "null"
+]

removedOutput schema / properties / lei_status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / lei_status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed3 schema fields changedJul 28, 2026

addedOutput schema / properties / country

Added value: +{
+  "additionalProperties": false,
+  "description": "Same shape as REST GET /v1/bic/:code. name falls back to the country code when the row carries no name.",
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "name"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / country_code / description

Added value: +"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.code."

addedOutput schema / properties / country_name / description

Added value: +"DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which falls back to the code rather than to null."

Changed1 schema field changedApr 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "bic": {
+      "description": "Echo of the input, normalized to uppercase.",
+      "type": "string"
+    },
+    "bic11": {
+      "description": "11-char form including branch.",
+      "type": "string"
+    },
+    "bic8": {
+      "description": "8-char form (institution-level).",
+      "type": "string"
+    },
+    "branch_code": {
+      "type": "string"
+    },
+    "branch_info": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "city": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "country_code": {
+      "type": "string"
+    },
+    "country_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "error": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "institution": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Bank legal name."
+    },
+    "is_test_bic": {
+      "type": "boolean"
+    },
+    "lei": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Legal Entity Identifier (ISO 17442) if available."
+    },
+    "lei_status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "valid": {
+      "description": "Set when the BIC failed format validation.",
+      "type": "boolean"
+    },
+    "valid_format": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "bic"
+  ],
+  "type": "object"
+}

First observedApr 28, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark it read-only and idempotent, and the description adds rich behavioral detail: data-source provenance, a January 2018 frozen SWIFT subset, LEI coverage counts, null versus true semantics of listed_in_current_source, and the caveat that absence of a match is not proof of nonexistence. It also states the cost/rate limits, which are not in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but it is organized into labeled sections (USE WHEN, DO NOT USE, BACKED BY, SOURCE, COST), with the most decision-relevant information front-loaded. It could be trimmed slightly, but no section is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup with annotations and an output schema, the description covers accepted input format, source behavior, edge cases, and operational cost. Nothing an agent needs to call it successfully is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the single 'bic' parameter, so the baseline is 3. The description adds value by specifying '8 or 11 chars, alphanumeric', giving concrete examples, and explicitly warning that IBANs should not be passed to this parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description leads with a specific verb and resource: 'Resolve a BIC / SWIFT code into the underlying bank' and lists the returned attributes (name, country, city, LEI, address). It also distinguishes itself from validate_iban by explicitly saying it is not for IBAN inputs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides an explicit 'USE WHEN' condition (user already has a BIC/SWIFT and asks about the bank, location, or LEI) and a 'DO NOT USE' rule with the exact alternative tool (validate_iban). This leaves no ambiguity about tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ibanforge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.