Clockchain Developer Tools MCP Server (thetangstr/clockchain-developer-tools) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 37 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

Clockchain Developer Tools MCP Server

Provides Clockchain's verified-time primitives, notarization, smart-contract scheduling, audit trails, and agent identity verification to any MCP client.

→ thetangstr/clockchain-developer-tools· listed on glama

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

thetangstr

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
✅
37 tools verified — handlers match their declared behaviour
2 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 6 credentials: MCP_API_KEY, MCP_PROMOTE_SECRET, MCP_TOKEN, MCP_TOKEN_SIGNING_SECRET, MINIMAX_API_KEY, MINIMAX_CN_API_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.
configCHATGPT_APP_TESTER_KEYS
configFEEDBACK_FILE
configFOLDER_ID
configKEEPER_STORE_PATH
configMAX_TURNS
🔐 secretMCP_API_KEY
configMCP_AUTH_TOKENS
configMCP_LOG
configMCP_LOG_BUDGET
configMCP_PORT
🔐 secretMCP_PROMOTE_SECRET
configMCP_RATE_PER_MIN
configMCP_REQUIRE_AUTH
configMCP_SERVER_PATH
configMCP_SURFACE
🔐 secretMCP_TOKEN
configMCP_TOKEN_MINT_PER_HOUR
🔐 secretMCP_TOKEN_SIGNING_SECRET
configMCP_TOKEN_TTL_DAYS
configMCP_TRANSPORT
configMCP_UPGRADE_URL_BASE
configMCP_URL
🔐 secretMINIMAX_API_KEY
configMINIMAX_BASE_URL
🔐 secretMINIMAX_CN_API_KEY
configMINIMAX_MODEL
configNETWORK_LABEL
configRESEARCH_URL
configSAMPLES
configTASK
configWEB_HOST
configWEB_PORT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

3/37 tools have annotations

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

All four hints declared on every tool

37/37 tools missing one or more hints — keeper_schedule (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); keeper_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); keeper_cancel (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +34 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

32/37 tool handlers declare input schemas (86%)

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

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.

Shell command execution

7 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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/thetangstr/clockchain-developer-tools)](https://m8ven.ai/mcp/thetangstr/clockchain-developer-tools)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bef177bdf93f1d36fbbe0a2a787121518eb3d3eb
code hash: fdd35101aec7000cae931c2bea670075d841486bc9edb24d1853ec51d827b224
verified: 7/31/2026, 9:02:16 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