Secure Flows

io.github.michal-leflerPublished by GitHub account michal-leflerv0.2.0Updated Oct 24, 2026

MCP server for secureFlows (secure-flows.com). Alias of io.github.michal-lefler/secureflows-mcp.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

Alias listing for the secureFlows remote MCP server, pointing at the same live endpoint as the primary secureflows-mcp listing.

What you can do
  • Connects an assistant to the secureFlows MCP server at secure-flows.com over streamable HTTP.
  • No tools are listed for this entry, so the available capabilities are not described here.
  • The README states it is the same running server as the primary secureflows-mcp listing, reached through a URL with an extra query string.
  • It exists only so the hyphenated name secure-flows is findable in registry search.
When to use it
Use it when you want to reach the secureFlows MCP server and found it under the hyphenated secure-flows name; otherwise prefer the primary secureflows-mcp listing, which documents the actual server, source and npm package.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the secure-flows.com endpoint. No packages, environment variables or headers are declared, and no authentication is declared.
Before you install
This is a duplicate listing, not a separate server or codebase; the README says the URL differs only by a query string that routing ignores. No tools, authentication or data handling are documented here, so check the primary secureflows-mcp listing before relying on it.

Installation

In SourceWeft

  1. Open Secure Flows 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.michal-lefler%2Fsecure-flows/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": {
    "secure-flows": {
      "type": "http",
      "url": "https://www.secure-flows.com/mcp?alias=secure-flows"
    }
  }
}

README

secure-flows

This repo exists so secure-flows — the hyphenated form matching the product domain (secure-flows.com) — is findable both on GitHub and in the MCP Registry, alongside the primary io.github.michal-lefler/secureflows-mcp listing (registry search does a literal substring match against the listing name only, and secure-flows is not a substring of secureflows-mcp, so a second listing was the only way to make both search terms resolve).

Same live server, distinct listing. The MCP Registry rejects a second listing whose remotes[].url string exactly matches an existing one — it does not check whether the URL actually resolves to the same backend. This listing's remotes[].url is https://www.secure-flows.com/mcp?alias=secure-flows: a harmless query string appended to the real endpoint. nginx's routing ignores it, so it reaches the exact same running MCP server — this is not a fork, a proxy, or separate infrastructure, just a distinct URL string to satisfy the registry's uniqueness check.

This is not a separate server or a separate codebase. For the actual MCP server source, tests, and npm package, see michal-lefler/secureflows-mcp (npm: secureflows).

Configure your AI agent

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

Product: www.secure-flows.com

Source: README.md at commit 402f004

Tools

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

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

85% 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
  • License10 pts