Afterbanks API
MCP server · www.afterbanks.com · found in a public list · checked since 2026-10-20
Live, server answered · latest check
Real-time bank connection API for balances, positions and account movements.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Exchange money and banking: Convert and send currency, and bank account data (exchange rates only: finance-data/markets/exchange-rates).
GET https://www.afterbanks.comThe name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
2 passed, 0 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-20 | 2 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-20 | 2 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing a passing answer. Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Payments and money / Exchange money and banking (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-20. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/5): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, server answered HTTP 301 | 328 ms |
cloudflare:MIA |
Live, server answered HTTP 301 | 444 ms |
What these figures do not show
- A passing check means the API's server answered one plain request from us, with no key and no redirects followed (web-reach/1): a response a live API gives without credentials (2xx, a redirect, 400, 401, 403, 405, 406, 415, 422 or 429). It does not show that its operations work, what they cost, or what a key gives access to.
- Listed in APIs.guru, a collection of OpenAPI descriptions; the address, the categories and the security schemes come from its description of the API, as stated there. The description itself is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_66749673dca5d75d