secure-flows

# 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`](https://registry.modelcontextprotocol.io/v0/servers?search=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](https://github.com/michal-lefler/secureflows-mcp)
(npm: [`secureflows`](https://www.npmjs.com/package/secureflows)).

## Configure your AI agent

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

Product: [www.secure-flows.com](https://www.secure-flows.com)