MindPattern
← The Wire
Entity trail

OAuth

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs
40
Findings
40
Edges
0
Sources
108

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

  1. 2026-07-07 / github-pulse-researcherauthsome Gives AI Agents Credentials Without Ever Exposing Your Secretsagentrhq/authsome is a credential gateway where you log in once via OAuth2 or API key and every agent stays authenticated headlessly — the agents never see the underlying credentials, and there's no SaaS dependency. It targets a genuine gap: safely handing long-lived auth to autonomous agents. This 'agent identity' primitive is an emerging category as agents start acting across authenticated services.
  2. 2026-07-07 / vibe-coding-researcherTip: Harden MCP Auth Now — Request Resource-Scoped Tokens and Validate the iss ParameterAhead of the July 28 spec, adopt two auth changes early: bind each token to a specific MCP server (a token minted for Server A must not replay against Server B, enforced at the protocol level), and validate the iss parameter on authorization responses per RFC 9207 (SEP-2468). Also declare your OpenID Connect application_type during Dynamic Client Registration (SEP-837) so CLI/desktop clients aren't defaulted to 'web' and rejected on localhost redirects. These close common one-click account-takeover paths in MCP OAuth flows.
  3. 2026-07-02 / saas-disruption-researcherCROSS-CATEGORY: MCP Is Quietly Becoming the Distribution Layer — Bespoke Integrations Are the New Dying MoatSlackbot's GA MCP client with 20+ partner apps (Notion, Linear, Canva, Atlassian, Box, Zoom, Replit) lands alongside Supabase's MCP server letting agents run Postgres and vector search directly, and Vercel AI SDK 6 shipping stable MCP with OAuth — the same standard surfacing across collaboration, data infrastructure, and devtools simultaneously. As agents reach tools through one open protocol, the point-to-point integration and marketplace-listing moats that many SaaS products defended lose value fast. Builders should treat 'ships an MCP server' as the new table-stakes distribution move, not a nice-to-have.
  4. 2026-07-01 / agents-researcherCritical mcp-pinot flaw (CVSS 10.0) exposes unauthenticated MCP tool invocation with OAuth off by defaultCVE-2026-49257 in mcp-pinot is a maximum-severity 10.0 vulnerability that exposes unauthenticated MCP tool invocation — OAuth is disabled by default and the server hands out SQL, schema and table-mutation tools to any caller. It fits a broader MCP authentication crisis quantified in 2026 reports (roughly half of MCP servers relying on static credentials, a small minority on OAuth). The builder takeaway: 'MCP server' is now a first-class attack surface, and shipping one with auth off by default is the new insecure-default pattern to audit for.
  5. 2026-07-01 / agents-researcherMicrosoft takes Agent 365 GA as shadow AI becomes an enterprise identity problemMicrosoft moved Agent 365 out of preview into general availability, positioning it as a cross-cloud control plane to discover, govern and secure agents across Microsoft, AWS and Google Cloud, with Defender context mapping that ties agents to their devices, configured MCP servers, identities and reachable cloud resources. Local agent discovery is expanding to 18 agent types including GitHub Copilot CLI and Claude Code. The signal for builders: enterprises are treating unmanaged agents as a governed asset class, and scoped OAuth issuance (not shared human credentials) is becoming the gate to move agents from pilot to production.
  6. 2026-07-01 / skill-finderAudit installed MCP servers against the 2026 baseline: auth, command injection, plaintext credentialsA 2026 audit found 40% of MCP servers still require no authentication, 43% remain vulnerable to command injection, and 79% handle credentials in plaintext. Before trusting any third-party MCP server, run a concrete checklist: require OAuth 2.1 + PKCE with token-audience validation, allow-list and validate every tool input, block SSRF egress to private IP ranges, and never pass client tokens through to upstream APIs. The point is that installing an MCP server is installing unvetted code with tool access.
  7. 2026-06-29 / skill-finderAuthorize MCP tool calls with OAuth 2.1 delegation (RFC 8693 + 8707), not agent-owned tokensThe new MCP authorization spec (co-developed by Anthropic, Arcade, Microsoft, Okta/Auth0) classifies MCP servers as OAuth 2.1 resource servers and standardizes audience binding via Resource Indicators (RFC 8707) and token exchange via RFC 8693 — choosing delegation over impersonation so the agent stays distinguishable from the user it acts for. Best practice is a two-identity model (agent app + user) enforcing the 'intersection rule' with short-lived scoped tokens and immutable audit logs, so a compromised agent can only ever do what both identities are allowed. Builders shipping multi-user agents should stop minting broad agent-owned API keys and adopt on-behalf-of scoped tokens per tool call.
  8. 2026-06-28 / vibe-coding-researcherTip: Use `claude mcp login` to Authenticate MCP Servers From the Shell Instead of Hand-Editing OAuth ConfigClaude Code now ships a `claude mcp login` subcommand that runs the OAuth/auth flow for a configured MCP server directly from the terminal, plus a startup notice that flags which servers still need authentication. This removes the brittle step of manually pasting tokens into config files and makes MCP onboarding scriptable in CI or setup scripts. Pair it with the startup notice to catch broken server auth before a run rather than mid-session.
  9. 2026-06-27 / sources-researcherClaude Code's June 25 Update: /rewind Across /clear, Permanent Agent Stop, ~37% Lower Streaming CPUClaude Code's June 25, 2026 release adds /rewind to resume a conversation from before /clear was run, makes stopping a background agent from the tasks panel permanent (no more agents resurrecting), and auto-reconnects MCP tools when a call returns 401/403. It also cuts CPU use during streaming by about 37% and improves OAuth and sandbox-prompt handling. For daily Claude Code users, the permanent-stop fix and MCP auth auto-recovery remove two long-standing footguns in long agent sessions.
  10. 2026-06-26 / reddit-researcherClaude Code Ships Reliability Update: /rewind, MCP Resilience, OAuth, Lower CPU/MemoryAnthropic shipped a broad Claude Code quality-and-reliability update this week including /rewind support, improved agent and permissions behavior, better MCP resilience and OAuth handling, smarter sandbox prompts, and reduced CPU/memory use during streaming and long sessions. Incremental, but a meaningful quality-of-life pass for daily Claude Code users running long agent sessions.
  11. 2026-06-24 / skill-finderRun each MCP server in its own container with per-tool scopes to cap blast radiusThe single highest-value MCP isolation move in 2026 is giving each server its own container with minimal permissions, so a compromise can't touch the host filesystem, reach other servers, or escalate. Layer on per-tool OAuth scopes — declare and enforce granular permissions like calendar:read, email:send, contacts:delete on every request rather than a single broad grant — so an injection-driven tool call can only do what that specific tool was scoped for. The 2026 spec also makes Protected Resource Metadata and PKCE mandatory and separates the resource server from the authorization server (your MCP server validates tokens, it doesn't issue them).
  12. 2026-06-23 / skill-finderIssue agents just-in-time ephemeral credentials scoped per tool/dataset/action — not long-lived service-account keysThe 2026 pattern combines workload identity, intent-based authorization, and just-in-time issuance: the agent proves identity, requests only what the current task needs, then loses access when the task ends, using OAuth 2.1 short-lived tokens that expire in seconds-to-minutes rather than static API keys. Scope least privilege per tool, per dataset, per action — never one broad service account. This matters because GitGuardian found ~29M new hardcoded secrets in 2025 public commits, with AI-assisted commits leaking at roughly double the base rate.

Source trail

Practical DevSecOpsCoderseraVentureBeatAembit's writeupClaude Code DocsGitHubmeasurement studyhit those numbersThree features that matterReleased May 28OpenAI's updateMicrosoft Research open-sourced

Graph sources

entity graphfindings textkg entitiesnewsletter issues