resuming (Dezodemius/resuming) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
6 days ago

resuming

Сайт для генерации резюме, а также для создания и хранения резюме под разные компании

→ Dezodemius/resuming· 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

Dezodemius

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

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.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 5 credentials: OPS_MCP_TOKEN, AI_API_KEY, YANDEX_CLIENT_SECRET, MAILRU_CLIENT_SECRET, SECRET_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.
🔐 secretOPS_MCP_TOKEN
configMUTATION_BASE_REF
configDATA_DIR
configLOG_LEVEL
configLOG_DIR
configOLLAMA_URL
configOLLAMA_MODEL
🔐 secretAI_API_KEY
configROBOKASSA_LOGIN
configROBOKASSA_PASSWORD1
configROBOKASSA_PASSWORD2
configROBOKASSA_TEST_MODE
configAPP_URL
configYANDEX_CLIENT_ID
🔐 secretYANDEX_CLIENT_SECRET
configVK_CLIENT_ID
configMAILRU_CLIENT_ID
🔐 secretMAILRU_CLIENT_SECRET
configOAUTH_LOGIN_ENABLED
configADMIN_EMAILS
configMETRIKA_ID
configANON_IP_LIMIT
configCLEANUP_INTERVAL_SEC
configANON_USAGE_TTL_DAYS
configEVENTS_TTL_DAYS
configRATE_LIMIT_ENABLED
configCSP_MODE
🔐 secretSECRET_KEY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySMTP_HOST
deploySMTP_PORT
deploySMTP_USER
deploySMTP_PASS
deploySMTP_FROM
// 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

6/6 tools missing one or more hints — get_logs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); restart (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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 test coverage

3/6 tools referenced in tests (50%)

Write tests that reference each tool by name so every tool has at least one test.

No eval / new Function

2 eval() or new Function() calls — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

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/dezodemius-resuming-6erzp3)](https://m8ven.ai/mcp/dezodemius-resuming-6erzp3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d2b507a3e777948f4e69007dc44c0909115816d7
code hash: 316a18a6ca2d72d3ee85348a1e923ed609448558c9533a639e4ef49f4ece7bd3
verified: 8/21/2026, 9:09:28 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