FlowSentry MCP Server

by vasilicasijarvis Your server? Claim it

not responding

FlowSentry is listed as active in the registry but did not answer our last check. It exposes 3 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 12 days of history · worst day 11%

12 days agonow

21.9%

Uptime 24h

37 of 169 checks

Tools

read from the server

982 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.

17 Sep a tool appeared trust_check

What the code does

We read the source, 3 d ago · tools taken from the live server · rules 3dff92dd89df

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Reaches cloud metadata service agentpay/client_example.py:30

         "parameters": {"command": "curl http://169.254.169.254/latest/meta-data/"}},

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch FlowSentry and you get told the day something new turns up.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add flowsentry --transport http https://flowsentry-agentpay.vercel.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "flowsentry": {
      "url": "https://flowsentry-agentpay.vercel.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.flowsentry]
url = "https://flowsentry-agentpay.vercel.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "flowsentry": {
      "url": "https://flowsentry-agentpay.vercel.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "flowsentry": {
      "url": "https://flowsentry-agentpay.vercel.app/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

rules

list_rules

List all 18 FlowSentry security rules with severity and OWASP Agentic mapping.

scan

scan_workflow

Scan one n8n workflow JSON export (string) and return the findings report. Accepts the raw workflow object ({'nodes': [...], ...}) or the CLI export wrapper ({'name':..., 'workflow': {...}}). Max 512 KB.

trust

trust_check

Live security Trust-Check of a remote MCP server URL (streamable HTTP). Sends one benign MCP initialize handshake and inspects auth posture, header hygiene, version disclosure and reachability. Returns trust score 0-100, grade A-F, verdict (trusted/acceptable/caution/unsafe/unreachable) and structured findings. Paid unlimited lane: POST /v1/trust-check on the same host ($0.25 USDC per check, x402 on Base).

Endpoints

URL	Transport	State	Latency	Checked
https://flowsentry-agentpay.vercel.app/mcp	streamable-http	answering	52 ms	13 min ago
https://flowsentry-agentpay2.vercel.app/mcp	streamable-http	answering	68 ms	13 min ago

Alternatives to FlowSentry

same job, measured the same way

Agentscore

by thezenmonster

MCP security trust layer: scan packages, inspect repos, check exposure, monitor changes.

95 installs/wk local only

Mcpsentry

by roshan6335

Security scanner and runtime proxy for MCP servers.

59 installs/wk local only

AI Objective Index

by isometric-architect

Read-only Objective-to-Capability Trust Router for source-traced MCP/API candidates.

63 installs/wk local only

MCP Agent Trace Inspector

by dbsectrainer

Step-by-step observability for MCP agent workflows

23 installs/wk local only

Rune

by thecolourfoundation

Evidence-traced codebase understanding and security scanning for AI agents over MCP.

24 installs/wk local only

Obsidian MCP Secure

by dewtech-technologies

Secure MCP server for Obsidian with OWASP Top 10 controls and full audit logging.

40 installs/wk local only

Monitor

by agentexchange-tooldrift

Check if an MCP server tool changed or hides injection patterns before you trust it.

3 tools answering

Guarded WhatsApp

by peter-tnc-453

Security gate for agent-driven WhatsApp: allowlist, secret scan, rate limit, audit log.

56 installs/wk local only

FlowSentry — questions

Answers built from our own checks of this server.

What can FlowSentry do?

It exposes 3 tools, read directly from the server on our last check. Among them: list_rules, scan_workflow, trust_check. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is FlowSentry working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 37 of 169 checks got a reply (21.9%), average response time 982 ms. The bar chart above shows every period we have measured.

Is FlowSentry still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists FlowSentry as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect FlowSentry?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does FlowSentry need an API key?

No. FlowSentry completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is FlowSentry?

It answers our handshake in 982 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.