· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Daniel Stratton v1.1.0
Analyze track sessions
From the developer
Read-only access to existing account data. The plugin does not sell products, process payments, initiate subscriptions, or present upgrade flows.
Where am I losing the most time compared with my optimal lap?
Developer declarations; not independently tested. Listing last checked Nov 6, 2026. Package observed Nov 6, 2026.
From the marketplace listing
Review your synced Trackside driving sessions and telemetry. Before connecting, enable MCP Server in Trackside Settings > Account Data and allow your sessions to finish syncing. Sign in with the same Apple account used in Trackside. Access is read-only: the plugin cannot record, edit, or delete sessions.
Language: English · Automatically detected from descriptions.
Exact text from the indicated source. A mention alone does not establish support for your task.
Review your synced Trackside driving sessions and telemetry. Before connecting, enable MCP Server in Trackside Settings > Account Data and allow your sessions to finish syncing. Sign in with the same Apple account used in Trackside. Access is read-only: the plugin cannot record, edit, or delete sessions.
Analyze session data
Review your synced Trackside sessions, lap times, and original recording telemetry.
· 1 observation
Package or technical metadata updated
View technical comparison →· 4 observations
Skill instructions changed from “When available, `tires` identifies the resolved set, whether the assignment is automatic or explicit, and recorded usage. `get_session` also supplies install...” to “`list_sessions` sorts newest first by recording date, with an ID tie breaker. Filter by `track`, `trackLayoutId`,...
View comparison →Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Find competitors to follow as you develop your plugin.
Review training progress and manage your Setlane training data with permission.
Shared terms: track, cannot, analyze, record
Plan, build, log and review strength-training sessions with your Lifterly account: the same plan, history and exercise catalogue as the L...
Shared terms: track, apple, session, setting
Summarize and analyze strength-training data from your StrengthLog account.
Shared terms: analyze, delete, session, cannot
Read-only access to your DBHub data warehouse (Shopee, TikTok Shop, Lazada, Facebook Ads, POS...) through the DBHub remote MCP server.
Shared terms: analyze, delete, cannot, server
Manage your Marvis actions and decisions through your connected account.
Shared terms: track, delete, sign, review
--- name: review-telemetry description: Analyze synced Trackside sessions and full recording telemetry, including lap times, vehicle data, and GPS traces. --- Use Trackside MCP tools to answer questions about recorded driving data. The account must have Trackside Pro and MCP enabled in the iOS app. If linking or access fails, explain the returned error and direct the user to Trackside Settings, then reconnect. Never ask for Apple credentials or tokens in chat. Use `get_profile` to identify the account when needed. Find sessions with `list_sessions`, follow pagination, and use `get_session` to inspect the available recording files and current revision. A session appears only after its complete upload commits; absence does not prove the user never recorded it. `list_sessions` sorts newest first by recording date, with an ID tie breaker. Filter by `track`, `trackLayoutId`, `from` (inclusive), `to` (exclusive), `query` (session name), `vehicle` (car name), `vehicleId`, `tire` (set name), or `tireId`; `sort: "oldest"` reverses chronology. Pass `next` as `after` with unchanged filters. Text/car filtering can return an empty page or stop at a read budget with a continuation; keep paging. Dates are recording timestamps, not upload times. Prefer `get_session_summary` for completed-lap IDs/times, best lap, consistency, vehicle/tire context, and observed channel availability. It reads saved analysis, not a new lap calculation. Cite its analysis file and revision. Missing saved analysis means per-lap details are unavailable until the user opens the recording in Trackside and syncs its analysis. Channel coverage can be partial; never treat unexamined channels as absent. Source-timed laps can recover a crossing before the first recorded sample, so their saved start offset may be negative. Retained GPS samples may also extend past an authoritative finish. Preserve the saved completed duration rather than clamping it to the GPS sample window. Use `query_telemetry` for complete JSON Lines records or aggregates of specific source fields/dotted paths. Supply the session revision, requested `channels`, and optional saved `lapId` or recording-relative `startSeconds`/`endSeconds`. Raw time follows the primary recording's monotonic clock when present, otherwise its first usable timestamp; it does not apply replay GPS clock alignment. Lap filters honor saved phone receipt-clock repair and standalone receiver clocks. If `lap_timebase_unavailable` is returned, the archive does not establish a safe mapping from those saved lap boundaries to that original file; inspect originals without `lapId` or compare saved traces, and do not assume saved start/end seconds use the raw clock. A lap's end is excluded to avoid counting the next lap's boundary sample. `mode: "aggregate"` calculates numeric count/sum/min/max/mean; units remain in separate groups and unavailable signals remain null. Every aggregate covers one page only. Follow `nextCursor` as `cursor` with identical parameters, add counts and sums for a combined mean, and preserve unit groups. `complete` describes traversal of this query, not sync completeness. Unfiltered queries retain untimestamped records; `timeFilterCoverageComplete: false` means some records could not be placed within a requested time range. Original records and channel measurement timestamps are retained; no replay fusion or display smoothing is applied. Use `compare_laps` for two usable saved lap IDs with their session IDs and revisions. Cross-session comparison requires the same known layout ID. Positive delta means selected minus reference: the selected lap is slower. Timing uses Trackside's replay/live GPS projection, confidence rejection and smoothing algorithm 3; the finish delta uses saved completed durations. Metric traces are interpolated from saved analyzed traces only across available samples at most 1.5 seconds apart. Null channels and GPS delta gaps are unavailable, never zero. Sectors appear only when saved analy
Preview of the first 4,000 characters. Read full instructions →
Adds recording-date and vehicle/track/tire search, saved lap summaries, bounded telemetry queries, and revision-pinned lap comparisons using Trackside replay timing.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 6, 2026.
plugin_asdk_app_6ad668e33e608191976195bccef7b61d
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.