FlowSentry

io.github.vasilicasijarvisPublished by GitHub account vasilicasijarvisv0.3.0Updated Oct 24, 2026

Security scanner for n8n workflows + live MCP Trust-Check. 18 rules, OWASP mapped. Paid x402 API.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

Scans n8n workflows for security issues and runs a live MCP trust check through a paid remote API.

What you can do
FlowSentry is a remote MCP server that analyzes n8n workflows for security problems, applying 18 rules mapped to OWASP categories. It also offers a live MCP trust check. Access is through a paid x402 API rather than a local package.
When to use it
Useful when you want an assistant to review n8n automation workflows for security weaknesses, or to run a trust check on an MCP endpoint, without installing anything locally.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, environment variables, or headers are declared. The API is paid via x402, so a payment-capable client or wallet is needed. Network access to the endpoint is required.
Before you install
The service is a paid x402 API, so using it can spend money; confirm pricing and payment handling before connecting. Workflow content submitted for scanning is sent to a third-party endpoint. No authentication is declared, so treat the endpoint as untrusted for sensitive data.

Installation

In SourceWeft

  1. Open FlowSentry in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.vasilicasijarvis%2Fflowsentry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "flowsentry": {
      "type": "http",
      "url": "https://flowsentry-agentpay2.vercel.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.3.0LatestSep 17, 2026
  2. v0.2.0Sep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.