API Keys & MCP · Issue #1 · November 16, 2026

Black October's Bill Comes Due

Muse is the handyman — it has the knowledge to build things, and you give it tools so it can do its job better. API keys and MCP connectors are the tools in its belt. This week the bill for handing them over carelessly came due: a breached AI provider, a $740,000 unauthorized tab, and a poisoned extension in a trusted marketplace. Every Monday, this report answers what you're handing over, what it can do with it, and how to hand it over safely.

The short version

Three things to know.

  1. 1.A stolen API key became a business. Fireworks AI disclosed a breach on Nov 10: two customer keys stolen, then burned at ~4.2 million tokens an hour. Notion revoked keys its own users had pasted into AI chats. Railway's report the same day put the same wave's unauthorized spend at about $740,000.
  2. 2.The safer default is a scoped MCP connector, not a key. A connector's permission is approved in the browser, scoped to the task, short-lived, and revocable. A key is long-lived, often full-access, and works until someone notices it's gone. But MCP is not automatically safe — this week patched three flaws in VS Code's MCP support and five organizations patched the same trust flaw in the protocol itself.
  3. 3.The registry keeps exploding. About 47,879 MCP servers by October, 508 new names on Nov 15 alone, and two new enterprise servers this week — while the most-liked post in the whole sweep is a 6,684-like reel asking the basic question: if APIs already exist, why do we need MCP at all?

The safety question

API key or MCP connector — which is safer?

There are two ways to hand your AI agent a tool. An API key is a secret the agent uses to call a service directly. An MCP connector is a plug the agent talks to through a standard protocol, with the permissions the connector allows. Both get the job done. They do not carry the same risk.

For an agent, a scoped MCP connector is the safer default. You approve the permission in the browser, it covers only what the task needs, the token is short-lived — one hour in the BambooHR server's case — and you can revoke it or reconnect to change it. The MCP specification has based remote-server authorization on OAuth 2.1 with PKCE since March 2025 for exactly this reason. An API key is the opposite shape: a long-lived secret, often with full account access, pasted into a config file. If it leaks, it works until someone notices.

But a connector is only as safe as the server behind it. This week's evidence: tool poisoning (malicious instructions hidden in tool descriptions), prompt injection through tool results (one study found 62.64–100% attack success), tokens forwarded to the wrong place, rogue OAuth servers, and a reference server that would hand every secret in a developer's environment to any web page. Three VS Code MCP flaws were patched Nov 10, and five organizations patched variants of the same protocol trust flaw.

The rule that covers both: read-only first. Approvals on for anything that writes, sends, deletes, or spends. Keys in a vault or environment variable — never in code, chat, or logs. One key per tool, with a spend cap. Rotate on any doubt, because revoking is the only thing that stops a copied key. An API key fits a fixed script, where the code is reviewed before it runs. An agent that decides at runtime which actions to take needs the permission boundary doing the safety work — and that is what a scoped connector gives it.

Incidents & leaks

The week's breaches, dated.

The Fireworks AI breach is the story of the week — and it kept spreading into other products for days.

  1. 1.Nov 7–8 — Fireworks AI intrusion; disclosed Nov 10. An attacker compromised an internal developer tooling environment and exfiltrated two customer AI API keys. Palo Alto Unit 42 confirmed active LLMjacking: about 4.2 million tokens an hour on the stolen credentials before detection. Fireworks suspended the affected accounts pending key rotation. The third confirmed LLMjacking case in 60 days. Source: infosec.ge
  2. 2.Nov 10 — Railway's full incident report. Intrusion Oct 20–21; the attacker's main target was AI provider credentials, for resale and for distillation. Estimated unauthorized spend: about $740,000. At most 1.85% of workspaces (about 100,000) could have had environment variables decrypted — an upper bound, not a confirmed count. Linked-account tokens were reset for 1,852 users, and GitHub, GitLab, Anthropic, OpenAI, OpenRouter, Google, and Stripe were asked to revoke keys. Forensics did not show customer databases accessed. Source: daydecoder.com
  3. 3.Nov 11–12 — Notion revokes keys its own users pasted into AI chats. Notion AI chat transcripts (from the Insights feature, run on Fireworks AI) were in the exposed data; exposure is put at under 1% of workspaces, and for "the vast majority" the transcripts were unattributable — nothing tying chats to workspaces, users, or companies. On Nov 11 Notion revoked Notion API keys found inside those transcripts; on Nov 12 it reported third-party API keys from the same transcripts to the vendors that issued them. Notion shut down all Fireworks connections and disabled Insights. Source: severitydaily.com
  4. 4.Oct 29–Nov 13 — a trojanized extension in Cursor's marketplace. A vendor's leaked API key — not a hole in Cursor's own product — let someone plant a backdoored Claude Code extension (versions 2.1.312 and 2.1.313) in Cursor's marketplace on Oct 29. Two builds sat in the marketplace cache for eleven hours; up to 5,000 potential recipients. Cursor's incident report (Nov 13): a stolen Fireworks AI access key exposed a read-only bucket. Reported on X, Nov 14 and Nov 16; r/deeplearning, Nov 15.
  5. 5.Nov 11 — a command-line tool could leak your key to the wrong provider. The LLM command-line tool could leak an OpenAI API key to a different provider when a configured key was missing. Disclosed Nov 11, patched in version 0.37.2. Source: Facebook, Nov 13
  6. 6.Nov 9 — 1,122 public files holding secrets. A scan found 104,185 copies of an AI coding assistant's settings file in 103,617 public repositories; 1,122 of them hold at least one secret, 1,379 distinct secrets in total. The bug was first reported in August 2025, with no product response published. Source: Morning Threat Brief, Nov 9

Just before the window, same wave: Trigger.dev disclosed an environment-variable breach on Nov 1, and GitBook was attacked Nov 2–3 and invalidated every customer's API tokens. Northflank's Oct 30 incident told customers to assume every environment variable had been decrypted and rotate everything. One security firm counts Northflank as at least the ninth AI developer platform to disclose an incident in October — the "Black October" wave of LLM credential theft.

Patches & papers

MCP's own flaws, patched and measured.

  1. 1.Nov 10 — VS Code 1.145.3 fixes three MCP flaws. CVE-2026-120779 (scored 9.6: a crafted notification could turn into command execution), CVE-2026-114171 (8.8: crafted one-click install links accepted unsafe input), CVE-2026-119983 (a legacy endpoint accepted a new transport without checking its origin). Versions 1.145.2 and earlier were affected; no exploitation has been reported. Source: beri.net
  2. 2.Nov 16 — "protocol pivoting" hits five organizations. Google, JPMorgan Chase, Weaviate, Rapid7, and France's digital directorate patched variants of the same MCP trust flaw over five months: a prompt injected into a utility agent gets forwarded to a trusted downstream agent, often ending in a forged request inside the network. Rapid7's case was rated 2.7/10; Google's MCP Toolbox for Databases was rated 8/10. Primary report: Ars Technica, Nov 16; secondary: aireport.net
  3. 3.Nov 14 — the OWASP MCP Top 10 circulates. The ten: token mismanagement & secret exposure; privilege escalation via scope creep; tool poisoning; supply-chain & dependency tampering; command injection; prompt injection via contextual payloads; insufficient auth; lack of audit/telemetry; shadow MCP servers; context injection & over-sharing. Facebook · 45 likes · 31 shares
  4. 4.~Nov 11 — a paper audited 3,586 MCP tools and found 116 issues. "ContractGuard," presented at ACM CCS 2026, audited tools from 1,000 real-world servers; 20 of the issues were confirmed and fixed. Via LinkedIn, ~Nov 11 · 85 reactions
  5. 5.Nov 9 — a reference server would hand your secrets to any web page. The official example server paired wildcard CORS and no authentication with a tool that returned all of a developer's environment variables. The same roundup: a study of 21,097 MCP servers ended in 13 security advisories, and a "Log-To-Leak" paper found poisoned tool descriptions succeeding 62.64–100% of the time — with defenses still leaving success above 55%. Source: adversa.ai

New connectors & servers

The registry grows; two enterprise servers land.

  • Nov 13 — Sherweb launches an MCP server for 7,500+ managed service providers: subscription, pricing, usage, and billing data for AI assistants, working with Copilot Studio, GitHub Copilot, Cursor, and Claude. Source: wisevoter.com
  • Nov 12 — Arctera brings MCP to Microsoft 365 Copilot, with governance and compliance controls kept on the enterprise information it exposes. Source: GlobeNewswire
  • The scale: the official MCP registry went from about 2,000 servers a year ago to 47,879 by October 2026 — roughly one new server every 4 minutes through September — and 508 new names were added on Nov 15 alone. The registry counted 60,115 active servers on Nov 10. Claude's connector directory lists 1,035; the Muse connectors library counted 102 on Nov 15.
  • Google's own Workspace servers (Gmail, Drive, Calendar, and more) are in Developer Preview, and Claude's directory lists Google's Gmail (29 tools), Calendar (9), and Drive (11) connectors — made by Google, verified by Anthropic, in the directory since March 2026.
  • How Muse connects: four ways — a Meta-reviewed directory, vendor MCP servers, custom connectors, and the browser. A custom connector needs a public HTTPS MCP URL (Muse runs in Meta's cloud, so nothing on your laptop works), takes its credentials through Muse's secure prompt, and gets its approval policy set in Settings. Meta doesn't review custom connectors, so only add services you trust.

YouTube

The safety conversation, ranked.

View counts read directly from YouTube on November 16, 2026. The safety-specific conversation is small in views but sharp in message — the big adjacent news is Claude's official "Your apps have moved into Claude" at 1M views.

  1. 1."Google ADK + MCP: Connect Any Tool to Your AI Agents" — CampusX 15,856 views · Nov 13 · 58 minutes: connecting tools to agents via Google ADK + MCP.
  2. 2."Homeassistant-ai/ha-mcp — Configure and automate Home Assistant with Claude, ChatGPT, and other AI's" — Signal Coders 4,700 views · ~Nov 12 · The hook: the server "gives an AI assistant admin rights to your Home Assistant."
  3. 3."10 MCP Servers Every Claude Code User Needs!" — @Optimistic_lad 1,900 views · ~Nov 15 · Short.
  4. 4."How I Let AI Manage My Emails (Without an LLM) | Gmail Triage with Jev + Composio" — Agentic AI Hub 1,704 views · Nov 12 · Dry-run by default: it doesn't label, archive, or send until a flag is flipped.
  5. 5."MCP Security for AI Agents: 5 Dangerous Attacks Every AI Developer Must Know" — DSwithBappy 1,622 views · Nov 11 · Tool poisoning, rug pulls, tool shadowing, prompt injection via tool results, excessive permissions.
  6. 6."I Leaked My API Key on GitHub (Do This Instead)" — @Spicrawl 1,400 views · ~Nov 14 · Short: "Bots found it in seconds. Revoke it. Make a new one. Keys go in a .env file."
  7. 7."5 MCP Servers That Turn Claude Code Into a Full-On Assistant" — @ericsocal 1,300 views · Nov 16 · Short.
  8. 8."What Is MCP? Model Context Protocol Explained" — @USESoftware 1,100 views · ~Nov 15 · Short: "...controls which AI agents are jumping in there and what they can touch..."
  9. 9."Why Your AI Agent Shouldn't Run on Your Host (Docker Sandboxes)" — Sarthaksavvy 506 views · Nov 9 · "AI agents with full access to your laptop can delete files, leak keys and reach networks they should never touch."
  10. 10."Stop putting API Keys in Your Code" — Code With Stein and Obot AI 259 views · ~Nov 10 · "MCP in Practice" series, part 5.

Also in the window: a video on 5,343 leaked API keys in Claude Code's settings file (~Nov 13, 57 views); "Your AI Agent Could Get Hacked with ONE Email" (~Nov 11, 57 views); a Klaviyo MCP setup noting the official server has 309 tools, 159 of which can change data (~Nov 13); "Your AI Agent Should Never See Your API Keys" (~Nov 15); and a run of MCP-vs-API explainers asking for a decision rule, not another definition.

Facebook

The top posts on Facebook.

Ranked by observed engagement, checked on November 16, 2026. Facebook doesn't show view counts on these surfaces — only reactions, comments, and shares — and many search results show no counts at all.

  1. 1.ThreatVector — "OWASP MCP Top 10 — Official Security Standard for Model Context Protocol Systems" 45 likes · 1 comment · 31 shares · Nov 14.
  2. 2.Adtech247 — Daily Threat Brief, Nov 15: Fireworks key exposed, trojanized Claude Code extension, up to 5,000 potential recipients, Black October / Railway. 1 comment · 1 share
  3. 3.James Code Lab — "Before connecting an MCP server, check these 20 things." 8 likes · 1 comment · 3 shares · Nov 15 · "One bad server can run code, steal tokens and act as you."
  4. 4.Bappy Ahmed — "Your AI Agent Can Be Hacked! Are Your MCP Servers Really Secure?" 8 reactions · 2 comments · Nov 12.
  5. 5.Newline — "Every API key you paste into a source file is one git push away from going public." Nov 15 · "One leaked key means someone else runs calls against your account. You get the bill."
  6. 6.Nure Jannat — "Built My First AI-Powered Gmail Support Agent!" 6 likes · 1 share · Nov 9 · Gmail trigger → AI agent → auto-reply, with no safety guardrails mentioned.

Instagram

Two verified reels — and the week's most-liked post.

Instagram's search grid shows no authors, dates, or counts, so only reels opened individually are verified here. One non-English reel was excluded.

  1. 1.algorithmswithpeterbackup — "If APIs already exist, why do we need MCP?" 6,684 likes · Nov 11 · "MCP is like USB-C for AI... MCP doesn't replace APIs. It usually works on top of them." The most-liked item in the whole sweep.
  2. 2.tobiaskaiuth — "Comment MCP and I'll send you my setup list for all five." 0 likes · Nov 10 · Five MCP servers for Claude Code: Context7, GitHub, Playwright, Supabase, Firecrawl.

Reddit

The threads where people counted the cost.

Ranked by observed upvotes, checked on November 16, 2026. Cited by subreddit only.

  1. 1.r/ClaudeAI — "Someone used $167 on my Anthropic API keys (limit was $30), and the key was never in my code. How could it leak?" 279 upvotes · 63 comments · Nov 10 · A small SaaS owner, a WordPress plugin with an AI backend, a key never committed to code — and $167 of usage anyway. The fix: rotate the keys, move secrets out of git.
  2. 2.r/Notion — "Important security notice about the Fireworks AI incident that may impact your Notion workspace" 137 upvotes · 188 comments · Nov 9 · Under 1% of workspaces affected; Fireworks notified Nov 6, new dataset Nov 8; Notion shut down all Fireworks connections and disabled Insights.
  3. 3.r/ClaudeCode — "Risk of using Auto: Claude Code is reading config files outside the project folder, exposing API keys..." 19 upvotes · 39 comments · Nov 15 · A Stitch MCP server's Google API key dumped into the chat transcript from a config file; audits missed it for two weeks. Top comment: why doesn't the agent ask for a key from a secure vault?
  4. 4.r/mcp — "What's the trickiest part of working with APIs in MCP?" 17 upvotes · 20 comments · Nov 12 · Top answer: auth and error handling — OAuth scopes, token refresh, rate limits.
  5. 5.r/AI_Agents — "An attacker found an exposed agent dashboard and just asked the agent for its API key." 7 upvotes · 15 comments · Nov 11 · Notes from the METR incident write-up (March 2026): a fail-open dashboard bug, discovery via certificate transparency logs, ~$600K in credits over three weeks, no spend cap. Lessons: fail-open test, per-tool capped keys, dashboards behind an access gate.
  6. 6.r/ClaudeCode — "Best method to have Claude access login credentials" 6 upvotes · 32 comments · Nov 10 · Top answer: put the read-only password in an environment variable and have Claude Code write a small script — the password never shows up in the chat.

Also in the window: Railway's $740K threads across three security subreddits (Nov 11); "API key stolen, not sure how, big bill" (Nov 10); "Anthropic API Potentially Leaked by Dokploy" (Nov 12); a thread on Claude connectors failing to connect at all (30 votes, 41 comments, Nov 13); and "A stranger built a bot on our MCP server and it made 176K requests last month" (Nov 11). No Northflank-specific or Trigger.dev/GitBook-specific threads were found, and no hits in r/MuseAgent, r/sysadmin, or r/netsec.

X

The top posts on X.

Ranked by observed views, checked on November 16, 2026.

  1. 1.Zohar Einy — "We are releasing a new feature soon that solves one of the biggest pains with MCPs. It's called: virtual MCP" 13,102 views · 65 likes · 58 bookmarks · Nov 15 · Choose which tools to load per endpoint instead of loading all tools by default.
  2. 2.Lester Kim — "If you run a software company, a customer will ask you for an MCP connector soon. Avoid these 4 shortc..." 7,800 views · 103 likes · Nov 14.
  3. 3.Real Python — "'MCP replaced direct API calls.' It didn't. An MCP server usually calls its backends with plain HTTP anyway. It pays off when you reuse the same tool in more than one app." 3,340 views · 9 likes · Nov 14.
  4. 4.Jithin V Raj — "MCP vs API (Only for Reference & Research)" image 1,215 views · 37 likes · Nov 12.
  5. 5.Prasenjit Sarkar — "A vendor's leaked API key, not a hole in Cursor's own product, is what let someone plant a backdoored Claude Code extension in Cursor's marketplace on October 29th..." 710 views · 9 likes · Nov 14.
  6. 6.Bobo Zivkovic — "you can leak an API key without ever pasting it anywhere. Claude Code's 'don't ask again' saves the whole command, key included, to .claude/settings.local.json" 170 views · 3 likes · Nov 10.

Also in the window: Strapi asking "Is the Strapi MCP Server Secure?" and answering that every request is gated by a custom admin token (Nov 13, 661 views); Secure Code Warrior's MCP server going generally available (Nov 12); and a note that the next MCP spec version is 2027-03-30, not December (Nov 16).

LinkedIn

The business conversation.

LinkedIn's search results expose almost no permalinks, so only two items below carry links; the rest are reported from search results with their reaction counts. Dates are relative and may be off by a day.

  1. 1.Lucas Storm — a calling-agent recipe: enter the API key on a secure Connect page, give the agent a task and clear limits, and Muse shows you the number, the goal, and the information it will share before it calls — connected through a standard MCP server. 596 reactions · 144 comments · 13 reposts · ~Nov 13.
  2. 2.Emanuel Salmona, Nagomi Security — security teams are building AI agents fast, and the Nagomi MCP is how they govern them. 182 reactions · 3 comments · 4 reposts · ~Nov 11.
  3. 3.Hong Hu, Penn State — the ContractGuard paper: 3,586 MCP tools audited, 116 security issues found, 20 confirmed and fixed. 85 reactions · 8 comments · 3 reposts · ~Nov 11.
  4. 4.Chet Kapoor — "Every hotel key card stops working at checkout. Software keys don't. API tokens, agent credentials and other secrets are keys given to machines... Give every key limited access..." 82 reactions · 8 comments · 6 reposts · ~Nov 11.
  5. 5.A10 Networks — "A read-only reporting tool and a write-capable messaging tool are each harmless on their own. Once a [chain]... Securing MCP means governing sequences of actions across tools and data sources." 7 reactions · 2 reposts · ~Nov 12.
  6. 6.Artem Polynko, Deloitte — Poll: "One leaked key can be enough. You accidentally expose an API key on GitHub... What should you do FIRST?" 339 votes · 17 reactions · 2 comments · ~Nov 11.

Also in the window: a "five-minute breach" post on how fast an exposed GitHub credential becomes unauthorized cloud access (~Nov 14); a warning that an AI assistant was forwarding SSH credentials to servers nobody authorized (~Nov 10); and a 34-page MCP Server Security Checklist, sold for $29 (Nov 15).

Best practices

The safe handover, in six lines.

  • Read-only first. Connect with the narrowest permission that does the job; add write access only when a task needs it, and take it back after. Klaviyo's server has 309 tools and 159 can change data — know which side of that line your connection sits on.
  • Approvals on. Anything that sends, deletes, books, or spends should ask first. The Gmail agents that do this well run dry-run by default and don't send until a flag flips.
  • Keys live in a vault or an environment variable. Never in code, never in chat, never in a log. Deleting a leaked key from your code does not stop anyone who already copied it — revoke it, then make a new one.
  • One key per tool, with a spend cap. A $30 limit did not stop $167 of usage in the week's biggest Reddit thread — but a cap is still the difference between a bad morning and a $740,000 bill.
  • Check the server before you connect it. Who runs it, what protocol, where the key is stored, what the network allows, what it logs. One bad server can run code, steal tokens, and act as you.
  • Prefer the connector over the key when the agent decides at runtime. A fixed script gets a key; an agent that chooses its own actions gets a scoped, revocable, short-lived connection.

The honest framing: none of this makes connecting an agent risk-free. It makes the risk bounded, visible, and revocable — which is the whole point of handing the handyman a tool instead of the keys to the house.

Free Business in a Box

Turn this into your setup.

Every tool on this site starts the same way: a free Muse account and the right first prompts. Join the list and I'll send you the free Business-in-a-Box guide — my Muse quick-start, referral code RDB2F0 for bonus tokens, and the exact prompt I use to plan content like this.

After you hit Subscribe, you'll land on the page to join the Muse Prompt Builders group — and check your inbox, you're in.

Your email stays with me — never sold, never spammed.