G
global-solo/banking-access-index-mcp
An MCP server over the Global Solo Banking Access Index: what 19 US business banking providers
updated 2026-11-17
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · global-solo/banking-access-index-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
global-solo/banking-access-index-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Banking Access Index — MCP server
Excerpted from the repository README (abridged)
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.
bash
# 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:
bash
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:
| Status | Meaning |
| explicit_accept | The provider publishes a statement that covers applicants in this country. |
| explicit_restrict | The provider publishes a restriction that covers this country. |
| no_published_restriction | The country is absent from the published restriction list, and no acceptance statement was located. Absence is not an answer. |
| unknown | No 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
| Tool | What it returns |
| check_banking_access | Per-provider published status for one country, with evidence URLs, access dates, and both discriminators. Optionally narrowed to one provider. |
| get_provider | The 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. |
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.
bash
# 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:
bash
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:
| Status | Meaning |
| explicit_accept | The provider publishes a statement that covers applicants in this country. |
| explicit_restrict | The provider publishes a restriction that covers this country. |
| no_published_restriction | The country is absent from the published restriction list, and no acceptance statement was located. Absence is not an answer. |
| unknown | No 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
| Tool | What it returns |
| check_banking_access | Per-provider published status for one country, with evidence URLs, access dates, and both discriminators. Optionally narrowed to one provider. |
| get_provider | The 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. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/global-solo-banking-access-index-mcp/)
- Source
- awesome · https://github.com/global-solo/banking-access-index-mcp
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.