mcpbeat Sign in

Pacing Tools MCP Server

answering

Pacing Tools is answering right now. Last checked 8 min ago.

Ask your AI about your fitness: activities and data from Garmin, COROS, Strava, GPX and more

Uptime history 44 days of history · worst day 96%
44 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
246 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Pacing Tools every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 8 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.pacing.tools/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.pacing.tools/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.pacing.tools/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.pacing.tools/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.pacing.tools/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://mcp.pacing.tools/mcp streamable-http sign-in 234 ms 8 min ago

Alternatives to Pacing Tools

same job, measured the same way
Garmin MCP
by garminmcp

Read-only Garmin data for your AI: sleep, Body Battery, activities, laps, and training status.

1 tools answering
athletedata
by athletedata

Your Garmin, Oura, WHOOP, Hevy and 35 more fitness apps, queryable from your own AI.

answering
Savi Tools
by getsavitools

Ask your AI assistant about your Savi Tools business: invoices, expenses, mileage, and more.

25 tools answering
Garmin — MissingMCP
by missingmcp

Garmin data in Claude: 135 tools — activities, sleep, HRV, training, workouts. Free, open source.

answering
Fartlek
by matisdsp

A coach's morning report from your Garmin data, for any LLM via MCP.

90 installs/wk local only
Stratyfix
by stratyfix

Ask about your deals, pace to target, and team odds from Stratyfix. Read only, real permissions.

answering
Leo Training
by leo-runningcoach

Running, trail and triathlon coach. Reads Strava, Garmin, COROS, Suunto, Polar. Adapts to your feel.

answering
Archstone
by nousvigil

Compile your own business capabilities from declarative YAML and serve them as MCP tools.

188 installs/wk local only

Pacing Tools — questions

Answers built from our own checks of this server.

Why is there no tool list for Pacing Tools?
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 Pacing Tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 246 ms. The bar chart above shows every period we have measured.
How do I connect Pacing Tools?
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 Pacing Tools?
No API key is involved. Pacing Tools 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 Pacing Tools?
It answers our handshake in 246 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.