FeesDefender (TyukhayNi/FeesDefender) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 59 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

FeesDefender

→ TyukhayNi/FeesDefender· 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

TyukhayNi

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
🚨
Secret credentials may flow to a network call
8 flows detected: SUDESPACHO_API_KEY, SUDESPACHO_LEGACY_REFRESH_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: SUDESPACHO_API_KEY, LLM_CLOUD_API_KEY, SUDESPACHO_LEGACY_REFRESH_TOKEN
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.
configXL_IO_CAP
configXL_OP_TIMEOUT
configGMAIL_DL_ROOT
configGOOGLE_DESPACHO_DL_ROOT
configGOOGLE_DESPACHO_UPLOAD_ROOT
configCASOS_ROOT
configOLLAMA_HOST
configOLLAMA_MODEL
configOLLAMA_TIMEOUT_S
configOLLAMA_TEMPERATURE
configRCLONE_BINARY
configRCLONE_REMOTE
configSCORING_MODE
configSCORING_TOP_K
configDRIVE_OUTPUT_FOLDER_ID
configDRIVE_EV_REMOTE
configDRIVE_EV_ROOT_FOLDER_ID
configLOG_LEVEL
configRCLONE_REMOTE_TL
configTEAM_DRIVE_TL
configFEESDEFENDER_ACTOR
🔐 secretSUDESPACHO_API_KEY
🔐 secretLLM_CLOUD_API_KEY
configLLM_CLOUD_BASE_URL
configLLM_CLOUD_MODEL
configLLM_CLOUD_TIMEOUT_S
configLLM_LOCAL_BASE_URL
configLLM_LOCAL_MODEL
configLLM_LOCAL_TIMEOUT
configLLM_LOCAL_TEMPERATURE
configRCLONE_CONF
configSUDESPACHO_LEGACY_PHPSESSID
configSUDESPACHO_LEGACY_JWT
🔐 secretSUDESPACHO_LEGACY_REFRESH_TOKEN
configSUDESPACHO_LEGACY_HOST
configFEESDEFENDER_SKILL_LOGS
configFEESDEFENDER_OFFLINE
configRUN_SLOW
configPYTHONIOENCODING
configFEESDEFENDER_WORKSPACE_REGISTRY
// 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

59/59 tools missing one or more hints — export_label_emails (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hash_path (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hash_tree (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +56 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.).

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 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/tyukhayni/feesdefender)](https://m8ven.ai/mcp/tyukhayni/feesdefender)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3043d97848e2189b9a52b2d87187eb996a06646d
code hash: 88102390a0e4fdf57574c05b611634c9e3dfd9840688bd14623292173028bea1
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