68
/ 100
3 days ago
glama

built-in-authorization-server

An MCP authorization server implementing OAuth2/OIDC flows, supporting dynamic client registration, PKCE, consent screens, and client ID metadata documents for MCP authorization.

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: GITHUB_CLIENT_SECRET, JWT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high4 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@nestjs/microservices@11.0.0GHSA-hpwf-8g29-85qm

Nest Affected by DoS via Recursive handleData in JsonSocket (TCP Transport)

hightypeorm@0.3.20GHSA-q2pj-6v73-8rgj

TypeORM vulnerable to SQL injection via crafted request to repository.save or repository.update

low@nestjs/common@11.0.0GHSA-cj7v-w2c7-cp7c

nest allows a remote attacker to execute arbitrary code via the Content-Type header

low@nestjs/core@11.0.0GHSA-36xv-jgw5-4q75

@nestjs/core Improperly Neutralizes Special Elements in Output Used by a Downstream Component ('Injection')

lowtypeorm@0.3.20GHSA-2rp8-mm9q-fp49

TypeORM: migration:generate template-literal code injection

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configGITHUB_CLIENT_IDxxx GITHUB_CLIENT_SECRET=yyy JWT_SECRET=<32+ chars> PORT=3014 npm start
🔐 secretGITHUB_CLIENT_SECRETGITHUB_CLIENT_ID=xxx =yyy JWT_SECRET=<32+ chars> PORT=3014 npm start
🔐 secretJWT_SECRETGITHUB_CLIENT_ID=xxx GITHUB_CLIENT_SECRET=yyy =<32+ chars> PORT=3014 npm start
configMCP_CIMD1 Accepts URL-shaped client_ids, and hosts GET /client-metadata.json + GET /demo-callback so the client side of the demo runs locally too. Implies consent — McpAuthModule forces it on.
configMCP_CONSENT1 Turns on the interactive consent screen (consent: { enabled: true }).
configMCP_FAKE_AUTHPORT=3005 =1 MCP_FAKE_IDP=1 npm start
configMCP_FAKE_IDPPORT=3005 MCP_FAKE_AUTH=1 =1 npm start
configPORT3005 MCP_FAKE_AUTH=1 MCP_FAKE_IDP=1 npm start
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/rinormaloku-mcp-inspector-v2-bug-authz-3aby98)](https://m8ven.ai/mcp/rinormaloku-mcp-inspector-v2-bug-authz-3aby98)
commit: 58c1535ce080a415e77df44af5d15780ec75d514
code hash: b8767e05e1aa1ad63a1fc4fe691a4eada93c3b046312883a8e1f0a1f55a3305e
verified: 7/28/2026, 9:00:59 AM
view raw JSON →