Banking Access Index

What 19 US business banking providers (banks and fintechs) publish about applicants who own a US LLC but are not US tax residents, across 8 countries: India, China, UK, Canada, Pakistan, Nigeria, Turkey and Brazil. Every cell carries the source URL it came from and the date that URL was read. A provider or country the index does not cover is marked "not assessed" and is not counted as a refusal. The server has four read-only tools and runs locally with npx github:global-solo/banking-access-index-mcp, no API key needed. Code is MIT; the data is CC BY 4.0 (Zenodo DOI 10.5281/zenodo.21336393).

दस्तावेज़

Banking Access Index — MCP server

An MCP server over the Global Solo Banking Access Index: what 19 US business banking providers publish about applicants who are not US tax residents but own a US LLC, across 8 countries (India, China, UK, Canada, Pakistan, Nigeria, Turkey, Brazil).

Every cell carries the source URL it came from and the date that URL was read.

# from GitHub, no npm account involved
npx github:global-solo/banking-access-index-mcp

Install as a plugin

The plugin in plugins/banking-access-index is a skill, not this server: it teaches the agent to read the public dataset and report its status vocabulary. Use the npx line above for tool calls.

Claude Code:

/plugin install banking-access-index --marketplace global-solo/banking-access-index-mcp

Codex:

codex plugin marketplace add global-solo/banking-access-index-mcp
codex plugin add banking-access-index@global-solo

Why this exists as a dataset

A model answering "can someone in India open a Mercury account" is drawing on provider marketing pages absorbed at training time, undated. When the underlying index was built, an adversarial re-verification pass re-fetched every source and discarded the claims whose quotes were absent, misread, or overreached: 239 of 268 mined claims survived. The 29 that did not were not edge cases. They were provider statements that read as settled until someone opened the page again.

So the thing this server adds is not coverage. It is a date next to each claim, and a refusal to convert silence into a yes.

The status vocabulary

Country cells are tri-state, plus unknown. The distinction the whole dataset rests on:

StatusMeaning
explicit_acceptThe provider publishes a statement that covers applicants in this country.
explicit_restrictThe provider publishes a restriction that covers this country.
no_published_restrictionThe country is absent from the published restriction list, and no acceptance statement was located. Absence is not an answer.
unknownNo published position was located.

Two discriminators travel alongside, because one label was hiding materially different evidence:

  • restrict_kind — named_on_prohibited_list · absent_from_closed_eligibility_list · blanket_rule_no_country_named. The outcome for the reader is identical across all three. The provenance is not, and this dataset is about the provenance.
  • unknown_kind — no_policy_published · mentioned_for_other_purpose · absent_from_non_exhaustive_list · conflicting_sources.

Both are carried through the MCP boundary rather than flattened into the status.

Tools

ToolWhat it returns
check_banking_accessPer-provider published status for one country, with evidence URLs, access dates, and both discriminators. Optionally narrowed to one provider.
get_providerThe full record for one provider across every dimension held in the index (entity, residency, rails, receive, card, phone/2FA, FDIC, onboarding, marketplace), each with its own evidence.
list_providersFilter by provider type, non-resident stance, SSN/ITIN handling, or by the status carried in a named country.
dataset_infoScope, verification date, the methodology prose, evidence tiers, and dimension_provenance.

Every response carries the status glossary, the limits below, and a provenance block.

Freshness

The server fetches the live dataset from https://www.globalsolo.global/data/banking-access-index.json at startup and falls back to the snapshot bundled in this package if that fetch doesn't complete. Which one answered is reported in every response as provenance.origin, rather than being hidden behind a single answer.

Limits

  • Each cell reports what a provider publishes, not what it does at underwriting. An application can be declined on grounds no published page covers.
  • A claim can go stale between its access date and now. The date is in the response for that reason.
  • Coverage is 19 providers × 8 countries. A provider or country absent here was not assessed, which is a different thing from assessed-and-negative.
  • dimension_provenance lists the dimensions added after the adversarial pass. Those are single-pass research and do not sit at the same confidence as the core.

Source, licence, citation

Server code: MIT. Dataset: CC BY 4.0.