coding-agent-loop (manishiitg/coding-agent-loop) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
22/100

coding-agent-loop

AgentWorks: the open-source control plane for running, measuring, and improving AI agent workflows across your company.

→ manishiitg/coding-agent-loop· listed on github_code

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

manishiitg

Source: github_code · also listed on github_repo_search

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
2 flows detected: MCP_API_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Reads files from sensitive locations
Touches: /srv/confida/.env
🚨
Code appears obfuscated
14 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 2 credentials: AUTH_SECRET, MCP_API_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.
configAGENTWORKS_EXECUTION_CONTEXT
configAGENTWORKS_LIVE_VIEW
configAGENTWORKS_RUNTIME_CONFIG_PATH
configAGENTWORKS_STATE_ROOT
🔐 secretAUTH_SECRET
configDEV_URL
configELECTRON_REMOTE_DEBUG_PORT
🔐 secretMCP_API_TOKEN
configMCP_API_URL
configMCP_SESSION_ID
configRUNLOOP_DOCS_DIR
configRUNLOOP_USER_DATA_DIR
configSHELL
configSPARKQUILL_USER_DATA_DIR
configSANDBOX_PERSISTENT_DIR
configAGENT_BROWSER_EXECUTABLE_PATH
configSTEP_OUTPUT_DIR
// quality suggestions

License file

No license file

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

No access to sensitive paths

Reads sensitive paths: /srv/confida/.env

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

No eval / new Function

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

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

14 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Secrets stay with their owner

2 secrets sent to a request target we could not resolve (MCP_API_TOKEN → dynamic, MCP_API_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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 5 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 Verified](https://m8ven.ai/badge/mcp/manishiitg/coding-agent-loop?variant=verified)](https://m8ven.ai/mcp/manishiitg/coding-agent-loop)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 81905e17d13477639dee28582e856775e02c78bd
code hash: 20a22b6c70ac31e6c9e8b36044e0e29924bf5e599a0c5b7f09127bb7f1d2b565
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