OpenSesame (Tyler-R-Kendrick/OpenSesame) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 41 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
9 days ago

OpenSesame

An all-in-one authorization fabric for the agentic era.

→ Tyler-R-Kendrick/OpenSesame· listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

Tyler-R-Kendrick

Source: github_code

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

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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: OPENSESAME_ACCESS_TOKEN, OPENSESAME_OPERATOR_TOKEN, OPENSESAME_TELEMETRY_KEY
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.
🔐 secretOPENSESAME_ACCESS_TOKEN
configOPENSESAME_DAEMON_URL
configOPENSESAME_HOST_API
configOPENSESAME_HOST_AUDIENCE
configOPENSESAME_MCP_TRANSPORT
🔐 secretOPENSESAME_OPERATOR_TOKEN
configOPENSESAME_SERVER
configOPENSESAME_TELEMETRY_HOST
🔐 secretOPENSESAME_TELEMETRY_KEY
// 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

41/41 tools missing one or more hints — delegation_narrow (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); delegation_revoke (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); connection_rotate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +38 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.

Tool inputs are validated

34/41 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

README present

No README found

Add a README.md describing the server and its tools.

License file

No license file

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

Domain consistency

npm scope @opensesame doesn't match GitHub owner tyler-r-kendrick

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 6 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/tyler-r-kendrick/opensesame)](https://m8ven.ai/mcp/tyler-r-kendrick/opensesame)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 935b09063e6c58af58257b9ec85803c169356203
code hash: f1f92399f1a460922adb35f9d5c524c4d7a686e9e8687a52cdd4b1f9555baf20
verified: 9/3/2026, 8:12:46 PM
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