rs.hotpath/hotpath-cloud · v1.0.1 · developer-tools
hotpath-cloud is healthy: it completed an MCP handshake in 720 ms and exposes 8 tools.
Read-only access to Rust profiling reports from CI: benchmark history, diffs and policies
Endpoint: https://hotpath.rs/api/v1/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 8 |
| Latency | 720 ms |
| Last checked (UTC) | 2026-11-07T15:40:27.372Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-07T15:40:27.372Z | Healthy | 720 |
get_default_policy | Get the default policy document (its keys at their defaults, comments included), as `source`. Every uploaded report must carry a policy file of its repository: write it as hotpath/policy.toml (or hotpath/<benchmark>-policy.toml), edit it, then check it with validate_policy. |
get_diff | Explain what changed in a benchmark: compare a stored report with the baseline recorded for it at upload (the report the PR comment compared), judged under the policy the report carried. The head is picked as in get_report. Values are strings formatted as the PR comment shows them, with a `unit`; `c |
get_report | Fetch one stored report by pull request, commit or id (exactly one). `pr` and `commit` answer the newest matching upload; `commit` matches the measured commit or a PR's head commit, so the local HEAD sha of a PR branch finds the PR's report. The summary names the policy file the report was judged un |
list_benchmarks | List one repository's benchmarks. A repository that does not exist, that the user cannot see or that has no App installed all answer not_found. list_repos already includes every repository's benchmarks; use this one when the repository is known. |
list_reports | List a repository's stored reports, newest first, as summaries without payloads: id, benchmark, commit, PR, event, verdict, dashboard URL. Use it to discover report history (recent runs of one or all benchmarks, a PR's or a commit's reports, regressions in a time window). Filters combine; `benchmark |
list_repos | List the repositories the token's user can see with the hotpath GitHub App installed, ordered by full name, each with its benchmarks (name, stored reports, time of the newest report). Start here: `full_name` is the `repo` argument of the other tools. A user in a large organization may see hundreds o |
validate_policy | Check that a policy TOML document parses as a hotpath policy, with the parser that judges uploaded reports. Stores nothing. A document with a problem is an error naming it. Use it after editing a policy file, before committing it. |
whoami | Show which user and API token this connection acts as: the GitHub login, the token's name and expiry. Use it to confirm the connection works, or after a call answers invalid_token. |