mcpbeat Sign in

BioFlow MCP Server

by getbioflow Your server? Claim it
answering

BioFlow is answering right now. Last checked 7 min ago.

Manage BioFlow link-in-bio pages, blocks, leads, and analytics from AI agents.

Uptime history 9 days of history · worst day 99%
9 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
473 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

BioFlow missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add bioflow --transport http https://app.getbioflow.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "bioflow": {
      "url": "https://app.getbioflow.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.bioflow]
url = "https://app.getbioflow.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "bioflow": {
      "url": "https://app.getbioflow.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "bioflow": {
      "url": "https://app.getbioflow.com/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.getbioflow.com/api/mcp streamable-http sign-in 452 ms 7 min ago

Alternatives to BioFlow

same job, measured the same way
details.page
by details

Manage your details.page link-in-bio from Claude: edit details, post updates, read analytics.

answering
Snapto
by snapto

Manage your Snapto link-in-bio page: links, social icons, and visit and click analytics.

answering
Sinkto.Link
by sinkto

Free URL shortener: manage short links, QR codes and click analytics from AI clients.

answering
CodeQR
by codeqr

Create and manage CodeQR short links, QR codes, and analytics from any MCP client.

answering
branchly
by branchly

Connect your agent to branchly: manage content, prompts, actions, learn from analytics and insights

37 tools answering
AnyFile
by useanyfile

Connect AnyFile to AI clients to manage files, share links, file requests, and analytics.

answering
Swonkie
by swonkie

Manage social media from your AI client: analytics, posts, scheduling, media, and AI images.

answering
BrightSite
by brightsitehq

Manage BrightSite websites: pages, blog posts, components, forms, media, and analytics.

answering

BioFlow — questions

Answers built from our own checks of this server.

Why is there no tool list for BioFlow?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is BioFlow working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 473 ms. The bar chart above shows every period we have measured.
How do I connect BioFlow?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to BioFlow?
No API key is involved. BioFlow answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is BioFlow?
It answers our handshake in 473 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.