brin
brin

@mcpauth/auth

npm

Is @mcpauth/auth safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @mcpauth/auth v0.1.4. Trust score: 50/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

@mcpauth/auth Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

@mcpauth/auth Capabilities & Permissions

What @mcpauth/auth can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Environment Variables

Accesses the following environment variables.

DATABASE_URLMCPAUTH_ALLOWED_ORIGINMCPAUTH_PRIVATE_KEYMCPAUTH_SECRETNODE_ENV

AGENTS.md for @mcpauth/auth

Good instructions lead to good results. brin adds @mcpauth/auth documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

@mcpauth/auth Documentation & Source Code

For the full @mcpauth/auth README, API documentation, and source code, visit the official package registry.

View on npm

Frequently asked questions about @mcpauth/auth safety

Weekly Downloads

50

Version

0.1.4

License

ISC

Last Scanned

2 days ago

Trust Score

50/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: DATABASE_URL, MCPAUTH_ALLOWED_ORIGIN, MCPAUTH_PRIVATE_KEY...