BANKSapi Docs

io.banksapiPublished by banksapi.ioOfficial publisherv0.1.0Updated Oct 29, 2026

Search and read the BANKSapi developer docs and OpenAPI specs for Open Banking integrations.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant search and read BANKSapi developer documentation and OpenAPI specs for Open Banking integrations.

What you can do
  • Search the BANKSapi developer documentation
  • Read documentation pages and OpenAPI specifications for Open Banking integrations
  • No tool list is published, so exact operations are not documented beyond search and reading docs.
When to use it
Useful when building or debugging an Open Banking integration against BANKSapi and you want the assistant to look up API endpoints, schemas and guidance from the official docs and specs instead of guessing.
Requirements
A remote streamable HTTP endpoint at banksapi.io; no packages, environment variables or headers are declared. Network access to that endpoint is needed.
Before you install
The manifest declares no authentication, so treat the endpoint as public and do not paste credentials or customer data into queries. Content returned is third-party documentation; verify API details against the official specs before relying on them.

Installation

In SourceWeft

  1. Open BANKSapi Docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.banksapi%2Fdocs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "banksapi-docs": {
      "type": "http",
      "url": "https://banksapi.io/docs-mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.