ibanforge

Swiss Clearing Lookup

lookup_ch_clearing

Read-onlyIdempotent

Resolve a Swiss BC-Nummer / IID (1 to 5 digits) into the underlying institution. USE WHEN: the user mentions a Swiss bank by BC-Nummer or IID, pastes a CH or LI IBAN clearing code, asks routing details for a Swiss instant transfer (SIC, euroSIC), asks about QR-bill QR-IID resolution, or needs to classify a Swiss financial institution (bank vs PFS vs SIC-only participant). EVERY IID OF THE SIX BANKMASTER, with its full payment-rail participation (SIC, RTGS CHF, Instant Payments CHF, euroSIC, LSV+/BDD) plus QR-IID allocation, not just a name lookup. BACKED BY: 1,100+ SIX BankMaster entries (Swiss official source, refreshed monthly). RETURNS: institution { name, type, iid_type, headquarters_iid }, address, bic, payment_services { sic, rtgs_chf, instant_payments_chf, eurosic, lsv_bdd_chf, lsv_bdd_eur }, sic_iid, qr_iid, valid_on. Only relevant for CH and LI accounts. 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 calls/month, on the REST API or on this transport, and POST /v1/keys/claim lifts that same key to 200 a month. Send the key here as Authorization: Bearer ifk_… (or X-API-Key) and each call counts against it exactly as on the REST API).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`iid`	Yes	Swiss IID (1-5 digit number)

Output Schema

TableJSON Schema

Name	Required	Description
`bic`	No	BIC if mapped.
`iid`	No	Normalized 5-digit BC-Nummer.
`note`	No
`error`	No
`found`	No
`qr_iid`	No	QR-bill enabled IID.
`address`	No
`message`	No
`sic_iid`	No
`valid_on`	No
`cost_usdc`	No	What THIS call was billed. Zero on the free MCP tier.
`institution`	No
`list_price_usdc`	No	Catalogue price of the same call on the paid REST/x402 route.
`redirected_from`	No
`payment_services`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 2, 2026
- removedOutput schema / properties / address / properties / building_number / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / address / properties / building_number / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / address / properties / post_code / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / address / properties / post_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / address / properties / street / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / address / properties / street / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / address / properties / town / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / address / properties / town / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / bic / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / bic / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / qr_iid / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / qr_iid / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / sic_iid / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / sic_iid / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedSep 1, 2026

addedOutput schema / properties / cost_usdc / description

Added value: +"What THIS call was billed. Zero on the free MCP tier."

addedOutput schema / properties / list_price_usdc

Added value: +{
+  "description": "Catalogue price of the same call on the paid REST/x402 route.",
+  "type": "number"
+}

Changed1 schema field changedApr 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "address": {
+      "additionalProperties": false,
+      "properties": {
+        "building_number": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "country": {
+          "type": "string"
+        },
+        "post_code": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "street": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "town": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "street",
+        "building_number",
+        "post_code",
+        "town",
+        "country"
+      ],
+      "type": "object"
+    },
+    "bic": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "BIC if mapped."
+    },
+    "cost_usdc": {
+      "type": "number"
+    },
+    "error": {
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "iid": {
+      "description": "Normalized 5-digit BC-Nummer.",
+      "type": "string"
+    },
+    "institution": {
+      "additionalProperties": false,
+      "properties": {
+        "headquarters_iid": {
+          "type": "string"
+        },
+        "iid_type": {
+          "description": "headquarters | branch | other",
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "type": {
+          "description": "bank | cantonal_bank | postfinance | raiffeisen | central_bank | foreign_participant",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "type",
+        "iid_type",
+        "headquarters_iid"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "payment_services": {
+      "additionalProperties": false,
+      "properties": {
+        "eurosic": {
+          "type": "boolean"
+        },
+        "instant_payments_chf": {
+          "type": "boolean"
+        },
+        "lsv_bdd_chf": {
+          "type": "boolean"
+        },
+        "lsv_bdd_eur": {
+          "type": "boolean"
+        },
+        "rtgs_chf": {
+          "type": "boolean"
+        },
+        "sic": {
+          "description": "Swiss Interbank Clearing.",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "sic",
+        "rtgs_chf",
+        "instant_payments_chf",
+        "eurosic",
+        "lsv_bdd_chf",
+        "lsv_bdd_eur"
+      ],
+      "type": "object"
+    },
+    "qr_iid": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "QR-bill enabled IID."
+    },
+    "redirected_from": {
+      "type": "string"
+    },
+    "sic_iid": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "valid_on": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedApr 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile needs no restating. The description goes well beyond that: data provenance (1,100+ SIX BankMaster entries, monthly refresh), scope limits (CH and LI only), auth mechanism (Bearer ifk_ / X-API-Key), and a concrete rate-limit/throttling model with reset schedule.

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

Conciseness3/5

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

Purpose, USE WHEN, and RETURNS are front-loaded and scannable. However, the COST section is a dense run-on parenthetical packing free-tier units, weekly reset timing, key-generation endpoints, key-claim URLs, and two header variants into one sentence, and it awkwardly references batch_validate_iban mid-token. The information is useful but not proportionally structured.

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?

With only one required parameter, an output schema present, and annotations covering the safety profile, the description still supplies the domain framing an agent needs: what the IID is, what the returned payment_services fields mean at a high level, provenance, and CH/LI limitation. Nothing material 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?

Only one parameter and schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the argument is a 1-5 digit BC-Nummer/IID and can come from an IBAN clearing code, and QR-IID resolution is a distinct use. That is more than the schema's bare 'Swiss IID (1-5 digit number)'.

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?

States a specific verb (resolve) and resource (Swiss BC-Nummer / IID) with scope, and the description makes clear it is richer than a plain name lookup by naming the sibling-adjacent tasks (BIC vs IID vs IBAN validation). An agent can distinguish it from lookup_bic and validate_iban without opening any schema.

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?

The 'USE WHEN' block enumerates concrete triggers (user mentions BC-Nummer/IID, pastes CH/LI IBAN clearing code, SIC/euroSIC routing, QR-IID resolution, institution classification) and adds the exclusion 'Only relevant for CH and LI accounts'. This is explicit when-to-use plus when-not guidance.

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.