Paceva MCP server
online · 100% uptimeio.github.OwenScheuer/paceva·v1.0.0Your swim, bike and run training: readiness, HRV, sleep, workouts and race predictions. Read-only.
0 stars
Reviews
Write oneNobody has reviewed Paceva yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Paceva tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1693ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Paceva compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 2,071 ms
- faster than 5% of 30,031 servers
Install Paceva in Claude Code, Cursor or VS Code
claude mcp add --transport http paceva https://paceva.app/api/mcp
What the publisher says
From the Paceva repository's README, as published. We do not edit it. Read it on GitHub
Paceva for developers
Paceva turns an endurance athlete's watch data into honest race predictions: ranges, checked against their own history. This repository documents the public surface: the Paceva MCP server, the OAuth 2.1 sign-in in front of it, and how Paceva connects to Intervals.icu.
The Paceva app itself is closed source. This repo is documentation and
examples only.
Connect in one minute
Server URL: https://paceva.app/api/mcp
Then ask things like "Should I go hard today?", "What could I swim a 1500 in right now?" or "How did my last block of riding go?".
Full walkthrough: docs/connect.md.
What's here
Ground rules
read anyone else's.
- Read-only. One scope, paceva:read. No tool writes anything.
- Only your own data. A token is bound to one Paceva account; it can never
(e.g. Garmin's HRV); paceva values are computed by Paceva.
- Every number is labelled. device values are your watch's own
range holds for you. Quote the range, not a single time.
- Predictions are ranges. Tools return a low–high range and how often that
working on the next call.
- Revocable. Disconnect any app from Paceva → Use with AI; its tokens stop
Status
Security
Found a problem? Please email privacy@paceva.app rather than opening a public issue. See SECURITY.md.
License
Docs and examples in this repository are MIT licensed. The Paceva name and logo are not.
Nothing above is checked by us. What we check is on the safety report.
Paceva: common questions
- Is Paceva MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the Paceva safety report
- How do I install Paceva?
- It runs remotely at paceva.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Paceva need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Paceva maintained?
- The last commit was 12 days ago (2026-10-23). The latest release is v1.0.0.
- Is Paceva up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Paceva compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 2,071 ms (faster than 5% of 30,031 servers). Full comparison.