---
title: "MCP endpoint for AI agents (Streamable HTTP)"
method: POST
path: "/mcp"
tags: ["MCP"]
---

# MCP endpoint for AI agents (Streamable HTTP)

`POST /mcp`

Model Context Protocol endpoint — Streamable HTTP transport, JSON-RPC 2.0 over POST. Exposes the same capabilities as this REST API as 7 MCP tools: validate_iban, batch_validate_iban, lookup_bic, check_compliance, lookup_ch_clearing, validate_payment_reference and check_postal_address (both free), plus send_feedback. 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.

## Request body

- object — JSON-RPC 2.0 request (initialize, tools/list, tools/call, ...) per the MCP specification
  - `jsonrpc` '2.0', required
  - `id` union
    - string
    - integer
  - `method` string, required
  - `params` object

## Response `200`

JSON-RPC 2.0 response (application/json or text/event-stream, depending on Accept header)

## Other responses

- `400` — Malformed JSON-RPC request

---

[API](https://skmtc.dev/ibanforge/apis/ibanforge-api.md) · [All operations](https://skmtc.dev/ibanforge/apis/ibanforge-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ibanforge/ibanforge-api/revisions/9499dba434ea/schema)