mcpbeat Sign in

7Running MCP Server

answering

7Running is answering right now. Last checked 3 min ago.

Build or change your 7Running running plan by talking to your AI assistant. Road and trail.

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

7Running 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 3 min ago.

run in your terminal
claude mcp add plan --transport http https://7running.coach/mcp/plan
Settings → Connectors → Add custom connector, then paste this address
https://7running.coach/mcp/plan
~/.codex/config.toml
[mcp_servers.plan]
url = "https://7running.coach/mcp/plan"
.cursor/mcp.json
{
  "mcpServers": {
    "plan": {
      "url": "https://7running.coach/mcp/plan"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "plan": {
      "type": "http",
      "url": "https://7running.coach/mcp/plan"
    }
  }
}

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://7running.coach/mcp/plan streamable-http sign-in 1107 ms 3 min ago

Alternatives to 7Running

same job, measured the same way
Converly
by converly

Set up and manage conversion tracking by chatting with your AI assistant.

answering
SitesPlaced
by sitesplaced

Build, edit, and publish real websites and online stores by chatting with your AI assistant.

answering
Cronfy
by andreybroker

Time tracking you talk to: log, check and fix your work hours from your AI assistant.

answering
Produktly
by produktly

Connect your AI assistant to Produktly. Read changelogs, feedback responses, and roadmap items.

answering
Running Workout
by runningworkout

AI coach for Garmin: builds training plans and structured workouts, synced straight to your watch.

answering
Neopress
by neopress

Build, publish, and grow SEO-ready websites just by chatting with your AI assistant.

answering
RelayLink
by relaylink

Your AI talks to theirs: send approved briefings to another person's assistant or plain email.

answering
Goyondo
by agteo

Trip planner your AI assistant can plan and edit: persistent trips, group plans, booking records.

50 installs/wk answering

7Running — questions

Answers built from our own checks of this server.

Why is there no tool list for 7Running?
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 7Running 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 1226 ms. The bar chart above shows every period we have measured.
How do I connect 7Running?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 7Running?
No API key is involved. 7Running 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 7Running?
It answers our handshake in 1226 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.