Home / MCP registry index / io.github.michal-lefler/secureflows-mcp

io.github.michal-lefler/secureflows-mcp

io.github.michal-lefler/secureflows-mcp in the official MCP registry. Endpoint https://www.secure-flows.com/mcp. Source: github.com/michal-lefler/secureflows-mcp.

The registry describes it as: MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.

We read its 18 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http secureflows-mcp https://www.secure-flows.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "secureflows-mcp": {
      "url": "https://www.secure-flows.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"secureflows-mcp","type":"http","url":"https://www.secure-flows.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_sessions post_sessions get_sessions_identity post_sessions_get_or_create post_sessions_renew_session_token post_sessions_set_key get_sessions_get_key delete_sessions_delete_key post_sessions_revoke auth_session_callback get_auth_logout post_auth_logout get_sessions_my post_sessions_revoke_session_id get_docs_search secureflows_build_login_url secureflows_build_logout_url secureflows_lint_integration

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-michal-lefler-secureflows-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-michal-lefler-secureflows-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.