About secure-flows
secure-flows is an MCP Registry alias for secureFlows that points to the same live service as the primary listing, not a separate server or codebase. It provides another listing for people searching for or configuring the hyphenated name.
Key features
- 01Alias listing for secureflows-mcp
- 02Points to the same live MCP server
- 03Includes an Agent configuration example
Use cases
- 01Find the service using the secure-flows name
- 02Configure an Agent to connect to the live service
MCP support
The listing uses the remote endpoint https://www.secure-flows.com/mcp?alias=secure-flows to reach the same MCP server; the query string distinguishes the registry listing.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://www.secure-flows.com/mcp?alias=secure-flowsclaude mcp add --transport http michal-lefler-secure-flows https://www.secure-flows.com/mcp?alias=secure-flows{"mcpServers":{"michal-lefler-secure-flows":{"type":"http","url":"https://www.secure-flows.com/mcp?alias=secure-flows"}}}Open in Cursor{"servers":{"michal-lefler-secure-flows":{"type":"http","url":"https://www.secure-flows.com/mcp?alias=secure-flows"}}}Open in VS Code{"mcpServers":{"michal-lefler-secure-flows":{"type":"http","url":"https://www.secure-flows.com/mcp?alias=secure-flows"}}}{"mcpServers":{"michal-lefler-secure-flows":{"serverUrl":"https://www.secure-flows.com/mcp?alias=secure-flows"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
18| Parameter | Type | Required | Description |
|---|---|---|---|
| auth | object | No | |
| auth.sessionToken | string | Yes | secureFlows session token |
| body | any | No | |
| query | object | No | |
| params | object | No | |
| connection | object | Yes | |
| connection.host | string | Yes | secureFlows base URL, for example https://api.example.com |
| connection.appId | string | No | Optional secureFlows app id used as a default for hosted login tools |
| connection.workspaceName | string | No | Optional workspace name used as a default for tools that need it |
Details
From the project READMEsecure-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
{
"mcpServers": {
"secureflows": {
"url": "https://www.secure-flows.com/mcp"
}
}
}
Product: www.secure-flows.com
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.