Skip to content

From October 1, WhatsApp charges for every business reply. Read the migration playbook

Most MCP servers still skip OAuth. That is the whole security story.

The specification makes OAuth 2.1 mandatory. Surveys of the public server ecosystem suggest only a small minority implement it. If you are about to connect an MCP server to an assistant that can see your work, that is the first thing to check.

Most MCP servers still skip OAuth. That is the whole security story.

The Model Context Protocol has had a very good eighteen months. Thousands of public servers, adoption in every major AI client, and a specification that now moves through an open process. The security picture is less flattering: the spec requires OAuth 2.1, and third-party surveys of public servers keep finding that only a small fraction actually implement it.

What the specification requires

OAuth 2.1, and as of the July 2026 revision, a noticeably harder version of it. Authorization servers should return the iss parameter per RFC 9207 and clients must validate it before redeeming a code, which closes an authorization-server mix-up attack. Client credentials are bound to the issuer that minted them, so they cannot be replayed against a different authorization server. And Client ID Metadata Documents are now the preferred registration path — Dynamic Client Registration is formally deprecated in favour of CIMD, though it keeps working for compatibility.

Why a buyer should care

  • A server with no authentication that touches real data is an open endpoint with a friendly description.
  • Credentials that are not issuer-bound are a confused-deputy problem waiting for someone to notice.
  • Without per-seat identity there is no way to revoke one person's access — only everyone's.
  • If a server cannot tell you who called a tool, it cannot tell you who leaked something either.

What we do

SuperCognit's MCP endpoint implements OAuth 2.1 including issuer validation and CIMD registration. Tools list without signing in, deliberately, so a prospective buyer can paste the URL and see exactly what a server offers before any credential changes hands; OAuth kicks in on the first actual tool call. That combination — inspectable without an account, authenticated before it does anything — is what we would want from somebody else's server.

If you are evaluating a server, the checklist is short: does it do OAuth at all, does it validate the issuer, can you revoke a single seat, and does it log who called what. A server that fails the first question does not need the other three.

Keep reading

Related guides

Weighing up your options?

Customer support

Eight tools people actually move to when their support AI stops fitting — what each is genuinely good at, what it costs you in flexibility, and how to pick without a three-month evaluation.

Sales

Eight tools for putting an AI in front of a buyer — qualifying, answering the awkward questions and getting a named contact into your pipeline rather than an anonymous chat log.

Human ambition. SuperCognit intelligence.

Try what you just read about

Free for 7 days — bring a prompt, leave with a product on your own domain.