Atlas / MCP servers / nahmanmate / Better Auth

Better AuthSAFE

mcp/nahmanmate/better-auth
Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
8 5r · 3w · 0d
Transport
stdio
License
AGPL-3.0
Stars
41
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://smithery.ai/server/@nahmanmate/better-auth-mcp-server)

MCP Server for Authentication Management

Enterprise-grade authentication solution providing:

  • 🔐 Secure credential management with AES-256 encryption
  • ⚙️ Multi-protocol auth (OAuth2, SAML, LDAP)
  • 🛡️ Real-time threat detection and prevention

Features

Core Tools

  • analyze_project - Analyze project structure for auth setup recommendations
  • setup_better_auth - Configure auth providers with project ID and API key
  • analyze_current_auth - Detect existing auth.js/next-auth implementations
  • generate_migration_plan - Create step-by-step migration path

Testing & Security

  • test_auth_flows - Validate login/register/reset/2fa flows
  • test_security - Run OWASP-aligned security checks
  • analyze_logs - Review auth system logs for issues
  • monitor_auth_flows - Real-time authentication monitoring

Available Resources

  • better-auth://config - Current Better-Auth configuration settings
  • better-auth://logs - Authentication system logs

Development

Clone and install:

git clone https://github.com/better-auth-mcp-server/better-auth-mcp-server.git
cd better-auth-mcp-server
npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Configuration

Environment Variables

# Required
BETTER_AUTH_PROJECT_ID=your-project-id
BETTER_AUTH_API_KEY=your-api-key

# Optional
BETTER_AUTH_ENV=development|staging|production
LOG_LEVEL=info|debug|error

Security Best Practices

  1. API Key Management
  2. Store API keys in environment variables
  3. Rotate keys regularly
  4. Use different keys per environment
  1. Acc
Read from source at commit 25e97df017a3OBSERVED · 2026-10-08
Advertisement
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add better-auth-mcp-server -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "better-auth-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (8)

5 read · 3 write · 0 destructive.

ToolRiskDescription
analyze_current_authreadDetect and analyze existing auth.js/next-auth implementation
analyze_logsreadAnalyze Better-Auth logs for issues
analyze_projectreadAnalyze project structure and dependencies to recommend Better-Auth setup approach
generate_migration_planwriteCreate step-by-step migration plan from existing auth to Better-Auth
monitor_auth_flowsreadReal-time monitoring of authentication processes
setup_better_authwriteInstall and configure Better-Auth in the project
test_auth_flowsreadTest authentication workflows
test_securitywriteRun security tests on Better-Auth setup
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (1)

LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
axios, better-auth, winston, @types/node, typescript
Why it matters. 5 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-08 · audit v0.4.1 · source sha 25e97df017a3full audit observations/trust-audit/mcp-server/nahmanmate__better-auth.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-0825e97df017a3SAFEB89first audit
06

Questions

What tools does Better Auth expose?

8 in total: 5 read-only, 3 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Better Auth safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Better Auth need?

No credential environment variables were found in its source, so it appears to need none.

How does Better Auth run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as better-auth-mcp-server at 0.1.0.

How current is this page?

The grade is for one exact copy of the source (25e97df017a3), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement