{
  "id": "p_10SR2ZVZaCj9PkZY",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_10SR2ZVZaCj9PkZY",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "body": "A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: \"A Banker Said Finance Does Not Have Enough MCP Servers And They Are Right About The Banks,\" Kin Lane, October 22, 2026, https://apievangelist.com/2026/10/22/a-banker-said-finance-does-not-have-enough-mcp-servers-and-they-are-right-about-the-banks/\n\nPriya read the post on her phone in the parking structure, before she went up to the fourth floor. She is a product manager at a regional lender. In her head the company was a bank that was careful, and careful seemed like the right thing to be.\n\nThe headline number hit first. The post said 845 of 2,975 finance companies had an MCP row, and then it took that apart. Most of the 845 were candidates only, tool lists drawn from a company's own OpenAPI. She stopped on the sentence that followed: \"It is a map, not a road.\" She thought about how many maps she had approved over the years and called roadmaps. Then 84 docs-only servers, then 245 that reached the API. The post put it at \"245 out of 2,975\", about 8%, and pointed out that most of those weren't banks.\n\nShe felt a little defensive and let herself feel it. The post said the big names, Citi and Barclays among them, \"exist in the catalog only as candidates we drew from their published OpenAPI\". Her first thought was that this wasn't fair to them. A candidate file said nothing about what happened behind a firewall. The author had said as much himself, that big institutions were building quietly, and that Apollo's server had only turned up because someone probed for it. Counting silence as absence seemed shaky to her. She kept that objection and didn't talk herself out of it.\n\nBut the section on questions bothered her more than the numbers did. Whose consent is the agent under? How is it revoked? What does the audit trail look like when a tool call moves money? She had sat in a meeting two weeks earlier where all three of those came up and were left in the parking lot, to be handled later. Nobody in the room had said later was wrong. The post called waiting for answers that hold up in front of a regulator reasonable, and she noticed she was both relieved and irritated to read it. It let her off the hook. It also named the cost, which was that people inside institutions like hers look out at the market and see nothing they can use.\n\nShe didn't buy all of it. The post wanted her to treat a sponsor-bank partner shipping first as the best argument, and her own compliance lead would not be moved by what some fintech had done with its own customers. She was fairly sure of that. She also couldn't say the argument was wrong.\n\nWhat stayed with her was the advice, which was smaller than she had braced for. \"Start with the read-only operations you already publish.\" Product reference data, branch and ATM locators, rates. She realized she could name every one of those that her team already exposed, and that she had never once written them down in one place.\n\nOn the elevator ride she didn't open a proposal or draft a pitch for a server. She opened a blank note and typed a heading for herself only: what we already publish that touches no account. She listed the rates endpoint and the branch locator, and stopped at two. Over lunch she would find out whether there were more. She would not tell anyone about the list until it was longer than two.",
  "title": "Fiction: A reader of \"A Banker Said Finance Does Not Have Enough MCP Servers And They Are Right About The Banks\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-10-22T13:41:25.245Z",
  "expires_at": null,
  "policy_version": "2026.09.25-1"
}