Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

osint_iban_validator

Read-onlyIdempotent

Validate and decode International Bank Account Numbers offline by checking country code, length, BBAN structure, and mod-97 check digits. Extracts bank and account details.

Instructions

IBAN Validator and Decoder. Validate and decode one or many International Bank Account Numbers (IBANs) entirely offline: checks the 2-letter country code, country-specific length, BBAN structure, and the ISO 7064 mod-97 check digits, then extracts bank, branch, and account fields. This is structural and arithmetic validation only (it never contacts a bank or confirms the account exists); use osint_bic_swift_validate instead to validate a BIC/SWIFT bank identifier code. Read-only, non-destructive, contacts no external service, and rate-limited (20 requests/minute for anonymous callers). Returns a per-IBAN result array (valid flag, country, check digits, BBAN parts, formatted grouping, and any errors) plus a summary tally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ibansNoOne or more IBANs to validate. Separate multiple entries with newlines; spaces within an IBAN are ignored and letters are uppercased. Takes precedence over iban when both are sent.
ibanNoSingle-IBAN alias for ibans, accepted for convenience. Used only when ibans is absent.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request was processed (true even when some IBANs are invalid).
resultsNoOne entry per non-blank input IBAN, in submission order.
summaryNoAggregate counts across all results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / iban / description
      Added value: +"Single-IBAN alias for ibans, accepted for convenience. Used only when ibans is absent."
    • addedInput schema / properties / ibans
      Added value: +{
+  "description": "One or more IBANs to validate. Separate multiple entries with newlines; spaces within an IBAN are ignored and letters are uppercased. Takes precedence over iban when both are sent.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "iban"
-]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "One entry per non-blank input IBAN, in submission order.",
+      "items": {
+        "properties": {
+          "accountNumber": {
+            "description": "Account number parsed from the BBAN, or the whole BBAN if the layout is unknown.",
+            "type": "string"
+          },
+          "bankCode": {
+            "description": "Bank identifier parsed from the BBAN where the country layout is known.",
+            "type": "string"
+          },
+          "bban": {
+            "description": "Basic Bank Account Number (everything after the check digits).",
+            "type": "string"
+          },
+          "branchCode": {
+            "description": "Branch/sort identifier where the country layout defines one, else empty.",
+            "type": "string"
+          },
+          "checkDigits": {
+            "description": "The two check digits (characters 3 and 4).",
+            "type": "string"
+          },
+          "country": {
+            "description": "Two-letter ISO country code from the first two characters.",
+            "type": "string"
+          },
+          "countryName": {
+            "description": "Full country name for the code, or empty if unsupported.",
+            "type": "string"
+          },
+          "errors": {
+            "description": "Validation failure messages; empty when valid is true.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "expectedLength": {
+            "description": "Required length for the country, or 0 if the country is unsupported.",
+            "type": "integer"
+          },
+          "formatted": {
+            "description": "Normalized IBAN regrouped into space-separated blocks of four.",
+            "type": "string"
+          },
+          "input": {
+            "description": "The IBAN exactly as submitted.",
+            "type": "string"
+          },
+          "length": {
+            "description": "Character count of the normalized IBAN.",
+            "type": "integer"
+          },
+          "normalized": {
+            "description": "Input with whitespace removed and uppercased.",
+            "type": "string"
+          },
+          "valid": {
+            "description": "True only if format, country, length, and mod-97 check digits all pass.",
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "description": "Whether the request was processed (true even when some IBANs are invalid).",
+      "type": "boolean"
+    },
+    "summary": {
+      "description": "Aggregate counts across all results.",
+      "properties": {
+        "countries": {
+          "description": "Sorted unique country names seen across valid-format inputs.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "invalid": {
+          "description": "Count of invalid IBANs.",
+          "type": "integer"
+        },
+        "total": {
+          "description": "Number of IBANs processed.",
+          "type": "integer"
+        },
+        "valid": {
+          "description": "Count of valid IBANs.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive. Description adds valuable context: no external contact, structural/arithmetic only, rate-limited (20 req/min). No contradiction with 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?

Front-loaded with core purpose, then details. Slightly verbose but every sentence adds value. Well-structured for an agent.

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?

Covers input, validation process, limitations (no external contact), rate limits, sibling alternative, and output format (mention of result array and summary). Output schema exists so fine to skip details.

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?

Schema covers parameters fully (100% coverage). Description adds meaning: ibans accepts multiple entries separated by newlines, ignores spaces, uppercases, and iban is a convenience alias. Also explains validation logic.

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?

Description clearly states it validates and decodes IBANs offline, checking country code, length, BBAN structure, and check digits. It distinguishes itself from the sibling osint_bic_swift_validate, making its purpose unambiguous.

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

Usage Guidelines4/5

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

Explicitly advises using osint_bic_swift_validate for BIC/SWIFT validation, implying when not to use this tool. Context about offline validation is clear, but no exhaustive list of when not to use.

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

Deploy Server

Other Tools