BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

js

Skill Development Usable
Works inClaude Code
Usable Scanned β€” metadata only

Reduces authentication implementation burden for MCP server deployments, lowering security misconfiguration risk and accelerating time-to-production for Node…

πŸ” Plug-and-play auth for Node.js MCP servers.

51 starsMIT (commercial OK)FreeQuick setup
Usable rating β€” This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Reduces authentication implementation burden for MCP server deployments, lowering security misconfiguration risk and accelerating time-to-production for Node.js services requiring client verification.

Node.js backend teams building or extending MCP servers with authentication requirements.

Claude Code Claude Cowork Claude Chat

https://github.com/mcp-auth/js

By mcp-auth

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → PluginsAdd plugin. Search and click Install. Skills work in Claude Code only.
Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.
Command
claude plugins install mcp-auth/js

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Help me implement OAuth2 flows quickly in Node.js MCP servers without building auth from scratch
CostFree

Trust Signals Auto-scanned

Stars51Contributors3Last updated2026-08-31LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-09-17 · scanner v1

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 51 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

Things to check

  • Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying β†’

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
3/5
Versatility
3/5
Reliability
3/5
Security
3/5
Overall score3.00 / 5.00 UsableEvaluatedAug 2026
Scored from trust signals (evidence-eval-v1): 51 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation β†’