Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TuneWorks

REMOTE · TUNEWORKS.AI

Motorsports workspace for vehicles, setups, sessions, logs, maintenance, and race engineering.

Available components

62 Trust /100

Last scanned (23 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 22 Oct 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 7810 tokens (~78/item across 100 items; 100 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 28% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 101 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • New tool “get_ai_log_tuner_transcript” functional
    • New tool “get_ai_race_engineer_transcript” functional
    • New tool “list_ai_log_tuner_transcripts” functional
    • New tool “list_ai_race_engineer_transcripts” functional
  • 18 Oct 26 60

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Oct 2026 · Probed https://tuneworks.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.tuneworks.ai CN=YR2,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 RSA 2048 SHA256-RSA 56566c6c83e2473660c5fe0c3ee6269e792
SANs: *.tuneworks.ai, tuneworks.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tuneworks.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
tuneworks.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tuneworks.ai/mcp Verified 200
http (plaintext) http://tuneworks.ai/mcp HTTPS enforced 308 https://tuneworks.ai/mcp
MCP tools · 100 exposed · ~7,614 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_vehicles ~29

Lists vehicles saved in the connected user’s TuneWorks app garage.

NameTypeReqDescription
limitnumber––
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

mark_chart_channel_set_used ~30

Update the last-used time for a saved chart-channel set.

NameTypeReqDescription
idnumberyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

preview_share_build ~103

Summarizes selected Share Build vehicle, setups, sessions, recipients, and message without sending email.

NameTypeReqDescription
messagestring–Optional message to include in the Share Build email.
recipientsarray–Recipient email addresses to preview.
sessionIdsarray–Optional TuneWorks session IDs to include.
setupIdsarray–Optional TuneWorks setup IDs to include.
vehicleIdstringyesTuneWorks vehicle ID selected for Share Build.
NameTypeReqDescription
confirmationRequiredForSendboolean––
previewobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––

No examples provided.

process_ecu_file ~49

Start or retry processing for an existing ECU definition file. This does not upload, create, or read a file, and processing may consume compute and analysis resources.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

recommend_autocross_damper_adjustment ~62

Provides a bounded shock/damper adjustment recommendation without authentication or access to TuneWorks account data.

NameTypeReqDescription
axlestring––
phasestringyes–
severitynumber––
symptomstringyes–
NameTypeReqDescription
acquisitionScopestring––
authenticationRequiredboolean––
nextStepstring––
recommendationobject–Recommended damper corner, adjustment direction, click count, reason, and validation check.
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
urlstring––

No examples provided.

remove_team_member ~42

Remove a member from a team after explicit confirmation.

NameTypeReqDescription
confirmedbooleanyes–
teamIdstringyes–
userIdnumberyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

rename_team ~29

Replace a team’s name.

NameTypeReqDescription
namestringyes–
teamIdstringyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

reset_shop_list_items ~38

Reset every item in a connected user shop list to unchecked/open.

NameTypeReqDescription
confirmedbooleanyes–
listIdstringyes–
NameTypeReqDescription
actionTypestring––
listobject––
listIdstring––
messagestring––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––

No examples provided.

retry_ecu_file ~33

Retry an eligible failed, already stored ECU file. MCP does not upload binaries.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

revoke_team_invite ~43

Revoke a pending team invitation after explicit confirmation.

NameTypeReqDescription
confirmedbooleanyes–
inviteIdstringyes–
teamIdstringyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

save_vehicle_map_config ~59

Create or replace the connected user’s complete map-channel configuration.

NameTypeReqDescription
channelsobjectyes–
lapTypestringyes–
selectionsobjectyes–
signsobject––
vehicleIdstringyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

send_share_build ~134

Emails selected TuneWorks vehicle, setup, and session details to up to three recipients. Explicit user confirmation is required.

NameTypeReqDescription
confirmedbooleanyesTrue indicates that the user explicitly confirmed the recipient list and selected build details.
messagestring–Optional message to include in the Share Build email.
recipientsarrayyesRecipient email addresses. Share Build supports up to 3 recipients.
sessionIdsarray–Optional TuneWorks session IDs to include.
setupIdsarray–Optional TuneWorks setup IDs to include.
vehicleIdstringyesTuneWorks vehicle ID selected for Share Build.
NameTypeReqDescription
actionTypestring––
idstring––
messagestring––
previewToolstring––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––

No examples provided.

send_team_invite ~51

Create and email a team invitation only after explicit user confirmation.

NameTypeReqDescription
confirmedbooleanyes–
emailstringyes–
rolestringyes–
teamIdstringyes–
NameTypeReqDescription
countnumber––
listsarray––
maintenancearray––
sessionsarray––
setupsarray––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––
vehiclesarray––

No examples provided.

update_custom_track ~73

Replace the editable fields and ownership scope of a custom track.

NameTypeReqDescription
citystring––
countrystring––
countryCodestring––
regionstring––
teamIdstring––
trackIdstringyes–
venuestringyes–
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_maintenance ~139

Edits a TuneWorks maintenance reminder or service item. Deletes are not supported.

NameTypeReqDescription
categorystring––
doneDatestring–Service completion date in YYYY-MM-DD format. Natural date strings are accepted but YYYY-MM-DD is preferred.
dueDatestring–Optional reminder date in YYYY-MM-DD format. Omit when no reminder is wanted.
intervalTypestring––
intervalValuenumber––
namestring––
notesstring––
reminderDaysBeforenumber––
trackerIdstringyes–
vehicleIdstringyes–
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_session ~243

Edits an existing TuneWorks driving session. Deletes are not supported.

NameTypeReqDescription
additionalSessionDetailsstring––
bestTimestring––
brakingstring––
cornerEntrystring––
cornerExitstring––
dataLogIdsarray––
didNotWorkstring––
driversstring––
eventNamestring––
eventTypestring––
expectedUpdatedAtstring–Optional optimistic-concurrency timestamp from a previous TuneWorks response.
locationstring––
midCornerstring––
overallBalancestring––
performanceFiguresstring––
sessionDatestring–Session date in YYYY-MM-DD format. Natural date strings are accepted but YYYY-MM-DD is preferred.
sessionFormatstring––
sessionIdstringyes–
setupIdstring––
suggestedSetupChangestring––
trackstring––
tractionstring––
vehicleIdstring––
workedstring––
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_setup ~236

Edits an existing TuneWorks setup revision. Deletes are not supported.

NameTypeReqDescription
dataLogIdsarray––
expectedUpdatedAtstring–Optional optimistic-concurrency timestamp from a previous TuneWorks response.
influencedSessionIdstring––
performedBystring–Person who performed the setup. If omitted, TuneWorks uses the connected user name/email.
revisionnumber–Optional setup revision number. If omitted, TuneWorks updates the latest revision.
setupDataobject–Partial setup fields to change, including setup goals, overall weight/balance, tire summary, front/rear ride height, front/rear total toe, per-corner tires, alignment, ride height, springs, dampers,…
setupDatestring–Setup date in YYYY-MM-DD format. Natural date strings are accepted but YYYY-MM-DD is preferred.
setupIdstringyes–
setupNamestring––
vehicleIdstring––
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_shop_list ~102

Edits shop-list metadata or replaces the full categories and items collection.

NameTypeReqDescription
categoriesarray––
itemsarray––
listIdstringyes–
notestring––
purposestring–Enabled Shop List Purpose value.
sessionIdstring––
setupIdstring––
statusstring––
titlestring––
vehicleIdstring––
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_shop_list_item ~59

Atomically check or uncheck one shop-list item, change its quantity, or do both.

NameTypeReqDescription
itemIdstringyes–
listIdstringyes–
quantityinteger––
statusstring––
NameTypeReqDescription
actionTypestring––
listobject––
listIdstring––
messagestring––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
userobject––

No examples provided.

update_team_member_role ~40

Replace a team member’s role.

NameTypeReqDescription
rolestringyes–
teamIdstringyes–
userIdnumberyes–
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_unit_settings ~27

Update unit-category choices for the connected TuneWorks user.

NameTypeReqDescription
settingsarrayyes–
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_user_preferences ~26

Update selected preferences for the connected TuneWorks user.

NameTypeReqDescription
preferencesobjectyes–
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_vehicle ~199

Edits an existing vehicle in the connected user’s TuneWorks garage. Deletes are not supported.

NameTypeReqDescription
aspirationstring––
cylindersOrRotorsstring––
displacementstring––
engineHoursstring––
engineModelstring––
engineTypestring––
expectedUpdatedAtstring–Optional optimistic-concurrency timestamp from a previous TuneWorks response.
fuelstring––
fuelRatingstring––
makestring––
mileagestring––
modelstring––
modificationsstring––
ownerstring––
purposestring––
subModelstring––
transmissionSpeedsstring––
transmissionTypestring––
vehicleIdstringyes–
vinstring––
yearnumber––
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_vehicle_make ~40

Rename or rescope a custom vehicle make.

NameTypeReqDescription
idnumberyes–
makestringyes–
teamIdstring––
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

update_vehicle_modification ~183

Update a structured modification on an editable TuneWorks vehicle.

NameTypeReqDescription
brandstring––
categorystring––
costnumber––
dateInstalledstring––
datePurchasedstring––
installHoursstring––
installMileagestring––
installedByNamestring––
laborCostnumber––
modificationIdstringyes–
notesstring––
partNamestring––
partNumberstring––
purchasedFromstring––
purposestring––
quantitynumber––
removedAtstring––
replacedModIdstring––
statusstring––
systemstring––
vehicleIdstringyes–
NameTypeReqDescription
listobject––
sessionobject––
setupobject––
statusstringyesResult status such as ok, created, updated, sent, auth_required, or confirmation_required.
toolstringyesTuneWorks MCP tool name that produced this result.
trackerobject––
urlstring––
userobject––
vehicleobject––

No examples provided.

Install

How do I install the TuneWorks MCP server?

TuneWorks is a hosted endpoint at https://tuneworks.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · tuneworks.ai

# add to Claude Code
claude mcp add --transport http chrismore-tuneworks 'https://tuneworks.ai/mcp'
Common questions

What is the TuneWorks MCP server?

TuneWorks is an MCP server listed in the public MCP registry as io.github.chrismore/tuneworks. Motorsports workspace for vehicles, setups, sessions, logs, maintenance, and race engineering. This page covers its hosted endpoint (https://tuneworks.ai/mcp).

Is the TuneWorks MCP server safe to use?

TuneWorks scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TuneWorks MCP server expose?

TuneWorks exposes 100 tools: calculate_race_fuel_and_weight, calculate_gear_ratio_speed, calculate_tire_pressure_adjustment, calculate_corner_balance, calculate_spring_wheel_rate, and 95 more. Their descriptions and schemas cost roughly 7,614 tokens of context every time the server is loaded.

Does the TuneWorks MCP server require authentication?

No. We connected to TuneWorks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TuneWorks MCP server still maintained?

TuneWorks is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.