FlowSentry
REMOTE · FLOWSENTRY-AGENTPAY2.VERCEL.APP · SCANNED SEP 20
Security scanner for n8n workflows + live MCP Trust-Check. 18 rules, OWASP mapped. Paid x402 API.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the FlowSentry MCP server?
FlowSentry is a hosted endpoint at https://flowsentry-agentpay2.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · flowsentry-agentpay2.vercel.app
claude mcp add --transport http vasilicasijarvis-flowsentry 'https://flowsentry-agentpay2.vercel.app/mcp'
{
"mcpServers": {
"vasilicasijarvis-flowsentry": {
"url": "https://flowsentry-agentpay2.vercel.app/mcp"
}
}
} {
"servers": {
"vasilicasijarvis-flowsentry": {
"type": "http",
"url": "https://flowsentry-agentpay2.vercel.app/mcp"
}
}
} [mcp_servers.vasilicasijarvis-flowsentry] url = "https://flowsentry-agentpay2.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vasilicasijarvis-flowsentry": {
"type": "remote",
"url": "https://flowsentry-agentpay2.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add vasilicasijarvis-flowsentry --url 'https://flowsentry-agentpay2.vercel.app/mcp' --transport streamable-http
mcp_servers:
vasilicasijarvis-flowsentry:
url: "https://flowsentry-agentpay2.vercel.app/mcp" {
"McpServers": {
"vasilicasijarvis-flowsentry": {
"Transport": "http",
"Url": "https://flowsentry-agentpay2.vercel.app/mcp"
}
}
} assistant mcp add vasilicasijarvis-flowsentry -t streamable-http -u 'https://flowsentry-agentpay2.vercel.app/mcp'
{
"mcpServers": {
"vasilicasijarvis-flowsentry": {
"type": "http",
"url": "https://flowsentry-agentpay2.vercel.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −40
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://flowsentry-agentpay2.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of flowsentry-agentpay2.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://flowsentry-agentpay2.vercel.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://flowsentry-agentpay2.vercel.app/mcp | HTTPS enforced | 308 | https://flowsentry-agentpay2.vercel.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_rules List Rules ~26
List all 18 FlowSentry security rules with severity and OWASP Agentic mapping.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_workflow Scan Workflow ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| workflow_json | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
trust_check Trust Check ~111
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).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the FlowSentry MCP server?
FlowSentry is an MCP server listed in the public MCP registry as io.github.vasilicasijarvis/flowsentry. Security scanner for n8n workflows + live MCP Trust-Check. 18 rules, OWASP mapped. Paid x402 API. This page covers its hosted endpoint (https://flowsentry-agentpay2.vercel.app/mcp).
Is the FlowSentry MCP server safe to use?
FlowSentry scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FlowSentry MCP server expose?
FlowSentry exposes 3 tools: list_rules, scan_workflow, trust_check. Their descriptions and schemas cost roughly 214 tokens of context every time the server is loaded.
Does the FlowSentry MCP server require authentication?
No. We connected to FlowSentry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FlowSentry MCP server still maintained?
FlowSentry is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.