Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
openapi: 3.2.0
info:
title: Ibanforge MCP API
version: 1.4.3
contact:
url: https://ibanforge.com
description: 'Operations tagged MCP across 2 of this provider''s published API definitions: ibanforge-mcp-api-openapi.yml, ibanforge-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.ibanforge.com
description: Production
- url: http://localhost:3000
description: Local development
tags:
- name: MCP
description: Model Context Protocol endpoint for AI agents (Streamable HTTP)
paths:
/mcp:
servers:
- url: https://api.ibanforge.com
description: Production
- url: http://localhost:3000
description: Local development
post:
operationId: mcpStreamableHttp
summary: MCP endpoint for AI agents (Streamable HTTP)
description: 'Model Context Protocol endpoint — Streamable HTTP transport, JSON-RPC 2.0 over POST. Exposes the same capabilities as this REST API as 5 MCP tools: validate_iban, batch_validate_iban, lookup_bic, check_compliance, lookup_ch_clearing. Flow: POST an `initialize` request, then `tools/list` and `tools/call` (include the returned Mcp-Session-Id header on follow-up calls). Also available as a stdio server via `npx -y ibanforge-mcp`. This path speaks MCP, not the REST conventions documented elsewhere in this spec.'
tags:
- MCP
externalDocs:
description: MCP setup guide (Claude Desktop, Cursor, HTTP transport)
url: https://ibanforge.com/docs/mcp
requestBody:
required: true
content:
application/json:
schema:
type: object
description: JSON-RPC 2.0 request (initialize, tools/list, tools/call, ...) per the MCP specification
required:
- jsonrpc
- method
properties:
jsonrpc:
type: string
enum:
- '2.0'
id:
oneOf:
- type: string
- type: integer
method:
type: string
example: tools/list
params:
type: object
responses:
'200':
description: JSON-RPC 2.0 response (application/json or text/event-stream, depending on Accept header)
'400':
description: Malformed JSON-RPC request
components:
securitySchemes:
x402Payment:
type: apiKey
in: header
name: X-Payment
description: x402 USDC micropayment token
apiKey:
type: http
scheme: bearer
description: API key (Bearer ifk_xxx) — 200 free requests/month, or custom quota for paid keys
externalDocs:
description: Agent-oriented overview (llms.txt) with copy-paste examples
url: https://api.ibanforge.com/llms.txt
x-refined-from:
- ibanforge-mcp-api-openapi.yml
- ibanforge-openapi.yml