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

insforge-mcp

InsForge turns your coding agents into full-stack builders, letting them add backend features like auth, databases, file storage, serverless functions, and LLMs to your apps in seconds.

→ InsForge/insforge-mcp· listed on modelscope

Caution. Specific findings reduced this grade. They are listed on the page. 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

InsForge

Source: modelscope · also listed on mcp.so

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

modelscopemcp.so

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: API_BASE_URL, INSFORGE_API_BASE. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: API_KEY, INSFORGE_CLIENT_SECRET, MIXPANEL_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.
configAPI_BASE_URLnpx @insforge/install --client claude-code --env API_KEY=your_api_key --env =http://localhost:7130
🔐 secretAPI_KEYnpx @insforge/install --client claude-code --env =your_api_key --env API_BASE_URL=http://localhost:7130
configENABLE_ANALYTICS
configHANDSHAKE_PORT
configHANDSHAKE_TIMEOUT_MS
configHOST
configINSFORGE_API_BASE
configINSFORGE_CLIENT_ID
🔐 secretINSFORGE_CLIENT_SECRET
configINSFORGE_DEPLOY_UPLOAD_CONCURRENCY
configINSFORGE_FRONTEND_URL
configINTEGRATION_FUNCTION_SLUG
configINTEGRATION_LOG_SOURCE
configINTEGRATION_TEST_ENABLED
configMCP_SERVER_URL
configMCP_SESSION_SWEEP_MS
configMCP_SSE_KEEPALIVE_MS
🔐 secretMIXPANEL_TOKEN
configVERIFY_HEALTH_URL
configVERIFY_TIMEOUT_MS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

1/1 tools missing one or more hints — echo-tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (API_BASE_URL → dynamic) (1 other flows matched canonical API hosts)

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

Secrets not logged

4 secret values sent to console.log

Redact or omit secret values from log output.

Dependency freshness

1/10 production deps stale: node-fetch@2023-11-30 (2.7y)

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 Verified](https://m8ven.ai/badge/mcp/insforge-insforge-mcp-1nu63m?variant=verified)](https://m8ven.ai/mcp/insforge-insforge-mcp-1nu63m)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 932561e9938cd008c5751cc1b3f60a76b0824a0d
code hash: ce1c401b8fbd4b22d11bef85c6783b2bb82298fb064be70e9198cc2ede2fd2e7
verified: 8/13/2026, 10:03:55 PM
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