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

n8n-workflows-mcp

An MCP server that turns deployed n8n workflows into callable tools for AI agents, enabling discovery and execution of tagged workflows via a standard interface without rewriting integrations.

→ NestorPVsf/n8n-workflows-mcp· listed on glama

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

NestorPVsf

Source: Glama

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

Glama

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 1 credential: N8N_API_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.
🔐 secretN8N_API_KEY"": "your-api-key",
configN8N_API_KEY_FILEN8N_API_KEY Yes — REST API key, sent as X-N8N-API-KEY on every discovery request. Mutually exclusive with — exactly one is required.
configN8N_BASE_URL"": "https://your-n8n-instance.example.com",
configN8N_MCP_TAGto). Only tagged workflows become visible to the agent.
configN8N_WEBHOOK_AUTH_HEADER_NAMENo — Name of a header sent on every webhook call. Requires a value (below) if set.
configN8N_WEBHOOK_AUTH_HEADER_VALUENo — Value of that header. Requires the name above if set. Mutually exclusive with N8N_WEBHOOK_AUTH_HEADER_VALUE_FILE. Leave unset (along with the file variant) to disable.
configN8N_WEBHOOK_AUTH_HEADER_VALUE_FILEN8N_WEBHOOK_AUTH_HEADER_VALUE No — Value of that header. Requires the name above if set. Mutually exclusive with . Leave unset (along with the file variant) to disable.
// quality suggestions

Tool annotations

1/4 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — list_workflows (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_workflow_schema (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_workflow (missing: readOnlyHint, openWorldHint), +1 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 inputs are validated

Only 0/4 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

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/nestorpvsf-n8n-workflows-mcp-g44u6l)](https://m8ven.ai/mcp/nestorpvsf-n8n-workflows-mcp-g44u6l)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6357c63f54690fee078e3ca228d7c2aa9ac390ef
code hash: 6a25e8556e72b8a2c282cdd760ef09988f79706b610173271aabc67ed22f034d
verified: 8/3/2026, 10:13:31 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