← All servers

F

FlowSentry

warnings

flowsentry-agentpay.vercel.app

Security scanner for n8n workflows: 18 rules, OWASP Agentic mapped. Free MCP, paid x402 API.

https://flowsentry-agentpay.vercel.app/mcpUnknownMCP 2025-11-25v4.0.4last checked 22 Oct 2026spoke MCP on 100% of 87 checks (30 days)initialize in 85 ms

Last checked 22 Oct 2026

✓Answered the MCP handshake (MCP 2025-11-25)
–Auth scheme could not be determined
✓Lists 2 tools
!1 warning
✓Spoke MCP on 87 of 87 checks (30 days)

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

–Claude CodeUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude Code docs · read on 2026-08-30

–Claude (claude.ai & Desktop)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

–ChatGPTUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

ChatGPT docs · read on 2026-08-30

–CursorUnknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

Cursor docs · read on 2026-08-30

–VS Code (Copilot)Unknown

The handshake was refused with no challenge and no OAuth metadata, so what this server wants is not something the probe could record.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 22 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	Unknown
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Refused — credentials required

What the probe found

warningThe server refused to initialize

It speaks JSON-RPC but rejected the handshake: {"code":"404","message":"The deployment could not be found on Vercel."}

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

list_rulesscan_workflow

Contract history

16 Sep 2026v4.0.4no contract changes

7 Sep 2026v4.0.3first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Route it through the gateway

Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.

Add to my gateway

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/flowsentry/badge.svg)](https://mcpi.app/servers/flowsentry)