Windows-Network-Recovery-Toolkit (Kozphy/Windows-Network-Recovery-Toolkit) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

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

Windows-Network-Recovery-Toolkit

One-click toolkit to diagnose and fix common Windows network issues (proxy errors, Winsock corruption, DNS problems). Includes automated scripts and troubleshooting workflows.

→ Kozphy/Windows-Network-Recovery-Toolkit· 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

Kozphy

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 3 credentials: STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, SUPABASE_JWT_SECRET
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.
configMCP_READ_ONLY
configWNRT_API_HOST
configWNRT_API_PORT
configWNRT_API_RELOAD
configDEMO_MODEReviewer demo docker-compose.demo.yml API only (=true, fixture volumes) Hiring panels, read-only /trisk/
configPLATFORM_DATA_DIR
🔐 secretSTRIPE_SECRET_KEY
🔐 secretSTRIPE_WEBHOOK_SECRET
🔐 secretSUPABASE_JWT_SECRET
configAUTH_BYPASS_USER_ID
configAUTH_BYPASS_EMAIL
configPLATFORM_SAFE_MODE
configALLOW_PLATFORM_EXECUTE
configENDPOINT_AGENT_DRY_RUN
configENDPOINT_AGENT_API
configENDPOINT_AGENT_INTERVAL
configENDPOINT_AGENT_COLLECT
configENDPOINT_AGENT_DRY_COLLECTORS
configENDPOINT_AGENT_VERSION
configAGENT_VERSION
configFAILURE_SYSTEM_DATA_DIR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_API_BASE
deployNEXT_PUBLIC_PLATFORM_API
deployNEXT_PUBLIC_SUPABASE_ANON_KEY
deployNEXT_PUBLIC_SUPABASE_URL
deployNEXT_PUBLIC_TRISK_TOKEN
// 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

7/7 tools missing one or more hints — call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_proxy_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_tls_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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

5/7 tools referenced in tests (71%)

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

Shell command execution

11 child_process/subprocess calls in production code — runs shell commands (src/__main__.py:41, mcp_server/tools.py:76, mcp_server/tools.py:110)

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 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/kozphy-windows-network-recovery-toolkit-1ka496)](https://m8ven.ai/mcp/kozphy-windows-network-recovery-toolkit-1ka496)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c61bf00d30c4d60736ced27ce9a34d12ca5e4caf
code hash: 7a2b0ae9387c2c49360b9e93902fc080ed9b4cd3473814ef4542924758004dbf
verified: 8/17/2026, 10:03:48 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