Huntress counted 81 million login attempts against Azure CLI in two weeks of June and 78 compromises. Most of the victims had MFA. It just did not apply to the flow the attacker used.
Reality
- Evidence45
- Adoption
- Not scored
- Hype gap+25
- Incentives65
- Confidence55
buildOne report1 publisher MCP servers need their RFC 9728 resource URL to reject tokens minted for other servers
MCP servers that skip audience binding accept tokens minted for other servers, says a dev.to OAuth 2.1 guide that puts it in the 80% most guides skip. The check depends on RFC 9728 metadata the server publishes and a resource parameter the client sends.
Reality
- Evidence30
- Adoption
- Not scored
- Hype gap+25
- Incentives60
- Confidence35
buildOne report1 publisher Six OAuth steps run before an MCP client makes its first tool call
The MCP spec mandates OAuth 2.1 with PKCE, dynamic client registration and metadata discovery for remote servers. The one-hour tokens and customer-facing audit logs procurement asks about come from a guide's own bar.
Reality
- Evidence40
- Adoption
- Not scored
- Hype gap+25
- Incentives55
- Confidence48
Agentic AI's 2030 market more than doubles depending on who draws the category line
Grand View Research and MarketsandMarkets both compound the agent market at about 46% a year and finish $28.12bn apart in 2030. The gap is in what each firm counts, so a plan quoting either figure is betting on a category boundary.
Reality
- Evidence55
- Adoption40
- Hype gap+20
- Incentives68
- Confidence50
buildOne report1 publisher Sharing an MCP server across a team now costs an OAuth 2.1 authorization flow
The auth overhaul in the final MCP spec reaches only remote transports, which turns a compliance question into a question about deployment topology, and even the vendors credited with getting ahead of it need checking.
Reality
- Evidence38
- Adoption45
- Hype gap+28
- Incentives55
- Confidence45
A public OIDC client with PKCE replaces the cluster certificate that outlives its owner
Self-hosted Kubernetes still hands out certificate files that keep working after their owner leaves. The fix in a CNCF walkthrough turns on one Keycloak toggle, because a confidential client only moves the shared static credential onto every laptop.
Reality
- Evidence60
- Adoption
- Not scored
- Hype gap+12
- Incentives45
- Confidence58
buildOne report1 publisher MapMcp publishes your whole tool list before you add a single auth check
Wrapping an ASP.NET Core API in the Model Context Protocol is a two-file job. The part that takes real time is deciding whose token reaches the backend, and whether the backend will accept the one you forward.
Reality
- Evidence38
- Adoption
- Not scored
- Hype gap+25
- Incentives35
- Confidence55
Lovable will hand your published app to any AI assistant as a set of callable tools
The MCP server is generated from the app you already shipped, so the tools inherit whatever roles and plans your backend already enforces, and on Free and Pro the app has to be public before any of it works.
Publishers:docs.lovable.dev
Reality
- Evidence58
- Adoption
- Not scored
- Hype gap+10
- Incentives78
- Confidence57
buildOne report1 publisher Recurring invalid_grant is usually two of your own workers racing one refresh token
A dev.to writeup argues the intermittent OAuth failure is a concurrency bug on a rotating token, and that retrying it looks exactly like the replay attack reuse detection exists to catch.
Reality
- Evidence42
- Adoption
- Not scored
- Hype gap+22
- Incentives
- Not scored
- Confidence45
buildOne report1 publisher Wrap OAuth around all of MCP and the directories report zero tools
A developer's four-tool server read as empty on glama, Smithery and mcp.directory, because tools/list arrives without a token. The fix is a four-method allowlist.
Reality
- Evidence52
- Adoption28
- Hype gap+22
- Incentives58
- Confidence56
buildOne report1 publisher Atlas App Connections hands AI clients your whole Atlas role, so fix the roles first
MongoDB's OAuth 2.1 platform issues tokens that call the Atlas Administration API with the authorizing user's full permissions. Least-privilege role design stops being hygiene and becomes the control.
Publishers:mongodb.com
Reality
- Evidence76
- Adoption15
- Hype gap−5
- Incentives62
- Confidence63
Human-in-the-loop is being retired, and the assurance burden shifts to machine identity
A DigiCert CTO argues the human approval step in agentic AI will disappear entirely. If he is right, the control most boards signed off on is going before its replacement is provisioned.
Reality
- Evidence17
- Adoption
- Not scored
- Hype gap+58
- Incentives88
- Confidence22