Okta-MCP (vaibhavGoyal1096/Okta-MCP) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Limited view
71/100
2 months ago

Okta-MCP

A production-ready MCP server for Identity and Access Management with Okta integration, providing user and group management, audit logging, and permission guardrails.

→ vaibhavGoyal1096/Okta-MCP· listed on glama

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

vaibhavGoyal1096

Source: Glama

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. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: JWT_SECRET_KEY, REDIS_PASSWORD, POSTGRES_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretJWT_SECRET_KEY
configJWT_EXPIRE_MINUTES
configAPI_KEYS
configREDIS_HOST
configREDIS_PORT
configREDIS_CACHE_DB
🔐 secretREDIS_PASSWORD
configCACHE_DEFAULT_TTL
configCACHE_ENABLED
configDATABASE_TYPE
configPOSTGRES_HOST
configPOSTGRES_PORT
configPOSTGRES_DB
configPOSTGRES_USER
🔐 secretPOSTGRES_PASSWORD
configPOSTGRES_POOL_SIZE
configPOSTGRES_MAX_OVERFLOW
configWORKFLOW_ENABLED
configWORKFLOW_CLEANUP_DAYS
configACCESS_REVIEW_DEFAULT_DURATION_DAYS
configIP_WHITELIST_ENABLED
configALLOWED_IPS
configRATE_LIMIT_ENABLED
configCELERY_BROKER_URL
configCELERY_RESULT_BACKEND
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPOSTGRES_URL
deploySMTP_HOST
deploySMTP_PORT
deploySMTP_USERNAME
deploySMTP_PASSWORD
deploySMTP_FROM_EMAIL
deploySMTP_USE_TLS
deployREDIS_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

91/91 tools missing one or more hints — list_okta_users (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_okta_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_user_groups (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +88 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 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/vaibhavgoyal1096-okta-mcp-1qq6rn)](https://m8ven.ai/mcp/vaibhavgoyal1096-okta-mcp-1qq6rn)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 865b899eec2f6ba34a6e82f3dca5eaede4689a96
code hash: 1df8a8313f30624b3b845574e04b9a1134d8fb123dfa77099ad399f8128ef476
verified: 6/23/2026, 10:43:01 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client