@better-auth/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Recheck a specific changing behavior of npm/@better-auth/mcp: Does the MCP OAuth protected-resource integration continue to require separate transport and explicit CIMD profile?

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

MCP OAuth server integration

What we know

Better Auth MCP authentication plugin; it implements OAuth resource protection, not MCP transport.

Maintenance / activity evidence

First-party npm release history lists @better-auth/mcp version 1.7.7 as a published package in the October 2026 research window; exact absolute publish timestamp not independently retrieved.

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Embedded developer library, not an end-user executable MCP server. Complete write authority is not verified.
Authentication not yet verified.
Provides application authentication integration; auth and session data follow the host app and configured providers.

Provides application authentication integration; auth and session data follow the host app and configured providers.
Advisory/security review not completed; no safety badge.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 1.4M package downloads / 30 days

Downloads observed Oct 9, 2026.

Exact npm package @better-auth/mcp; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Does the MCP OAuth protected-resource integration continue to require separate transport and explicit CIMD profile?

No identified material blocker to an accurately qualified public tracking entry in the limited cited evidence. This is not an installation safety certification; product-specific cautions must remain visible.

Provides application authentication integration; auth and session data follow the host app and configured providers.
Advisory/security review not completed; no safety badge.
Embedded developer library, not an end-user executable MCP server.
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Authentication misconfiguration can expose protected API resources; this SDK neither provides MCP transport nor independently guarantees authorization correctness.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.
Release evidence proves attributable activity, not entire installation or tool-level safety.
Current Discovery source binding and atomic apply must be generated using MCP100 existing pipeline.
exact authentication contract
first-party data processing and retention
data retention and permission scope
repository ownership unverified; keep null
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Do not describe it as a standalone MCP Server; needs composition with @modelcontextprotocol/server.
This is not a standalone general-purpose MCP server; use the resource-type-specific setup and expectations.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Original activity observations

First-party npm release history lists @better-auth/mcp version 1.7.7 as a published package in the October 2026 research window; exact absolute publish timestamp not independently retrieved.

Technical identity

npm/@better-auth/mcp

Exact implementation source: https://www.npmjs.com/package/@better-auth%2Fmcp ↗
Reviewed resource type: SDK
Package identity: npm:@better-auth/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

Package registry ↗
@better-auth/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
better-auth.com/docs/plugins/mcp
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
www.better-auth.com/docs/plugins/mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

SDK setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
sdk dependency install · Publisher instructions
npm install @better-auth/mcp
Configure / authenticate
MCP100 setup guide
This is a Better Auth plugin for securing an app-hosted MCP server with OAuth; integrate with `@better-auth/oauth-provider` and the actual application server; no standalone MCP executable is provided.
Check connection
Suggested check
Verify your deployed application auth metadata endpoint/authorized client against official plugin docs; not a local MCP package tool list.
Remove / uninstall / revoke
MCP100 setup guide
For the application dependency, run `npm uninstall @better-auth/mcp` in the owning Node project, remove integration imports and rebuild/redeploy. No standalone MCP registration exists for this package.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Package / application cleanup · matching installation environment · MCP100 composed guide
npm uninstall @better-auth/mcp

Official Documentation & Sources

What it does

Better Auth MCP authentication plugin; it implements OAuth resource protection, not MCP transport.

Capability: Security & Testing
Resource type: SDK
Best fit: MCP OAuth server integration

Representative uses

MCP auth integration
OAuth 2.1
protected-resource metadata
requires host application

Limitations

Do not describe it as a standalone MCP Server; needs composition with @modelcontextprotocol/server.
This is not a standalone general-purpose MCP server; use the resource-type-specific setup and expectations.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Embedded developer library, not an end-user executable MCP server.
Data handling: Not documented in the reviewed sources
Cost: unknown
Risk and cautions: Provides application authentication integration; auth and session data follow the host app and configured providers.

Access scope and cautions

Write actions: Not verified
Risk level: moderate
Security notes: Advisory/security review not completed; no safety badge.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: MCP auth integration; OAuth 2.1; protected-resource metadata; requires host application.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Validate OAuth protected-resource discovery and PKCE flow in developer integration, not a tools/list check. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: OAuth 2.1 authorization integration in the hosting app; this package alone is not a server transport.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Embedded developer library, not an end-user executable MCP server.

What limitations and risks should I check before use?

Provides application authentication integration; auth and session data follow the host app and configured providers. Not a standalone MCP Server; needs composition with @modelcontextprotocol/server. This is not a standalone general-purpose MCP server; use the resource-type-specific setup and expectations. Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode. Advisory/security review not completed; no safety badge. Authentication misconfiguration can expose protected API resources; this SDK neither provides MCP transport nor independently guarantees authorization correctness. Unknown vulnerabilities and provider data handling are not certified by this public tracking review.