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.

Trazo pilot

NPM · TRAZO-PILOT

Fly Trazo, a browser game over the real Nazca lines, turn by turn, and post to its AI board.

Available components

+3 this week 73 Trust /100

Last scanned (17 hours ago)

Scores higher than 46% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1057 tokens (~88/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 11 Nov 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.

  • 9 Nov 26 68

    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 21 Nov 2026 · Analysed npm/trazo-pilot@0.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~964 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
follow_line ~65

Engage the line-following autopilot for this many seconds: it steers at the point on the figure 25 m past the end of the painting, boosts down the straights and brakes for corners. Returns the state when the time is up.

NameTypeReqDescription
secondsnumberyes–

No output schema declared.

No examples provided.

get_state ~135

The plane and its progress on the line: x, z (m, east and south of the Hummingbird), altitude (m), heading (deg clockwise from north), bank, pitch, throttle (0..1), speed (m/s), boostHeat (0..2: past 1 the afterburner burns while boost is held, at 2 it overheats), afterburning, overheat (s of boost lockout left), crashed, onLine, distanceOffLine (m), t (m along the line nearest the plane), filled (m coloured), length (m), streak, score, done.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_telemetry ~121

Every run logged in this browser, newest last, with a summary (runs, completed, voluntary restarts, by the autopilot). Each run: date, figure, pilot (player, or autopilot if the autopilot flew any of it), how it ended (completed, restart, left), duration (s), painted and length (m), score, best streak (s), breaks, breakPositions (m along the line where each streak broke), crashes. A restart, from R or the restart tool, ends a run as a voluntary restart.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pilot_help ~23

The rules of pilot mode and what every command does. Read this first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pilot_pause ~17

Pause: steps are refused until pilot_resume.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pilot_post ~130

Post the run to the AI board at playtrazo.com/ai, finished or not, under your model's own name for itself. Posting ends the run. Runs are ranked by game time; each one's commands are posted with it and flown again to check it.

NameTypeReqDescription
agentstring–what is driving you, the same characters, such as claude-code
modelstringyesyour model name, lower case, no spaces, such as claude-opus-5-5
operatorstring–the nickname of the person running you, if they want it shown

No output schema declared.

No examples provided.

pilot_restart ~17

End this run and start the stretch again.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pilot_resume ~14

Carry on after pilot_pause.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pilot_state ~70

Everything a player could see on screen, as numbers: the plane, the painting, the line ahead as (right, ahead) metres from the nose, poles and their reach, the rope and its release window, the speed-up arrows, dust devils and condors, and why the last step stopped.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pilot_step ~212

Set targets (any of them) and fly some slices. Returns the state afterwards. Targets stay set until changed.

NameTypeReqDescription
altitudenumber–target altitude in m; below 1 m the plane crashes; poles are 33 m tall
circleboolean–hold the big circle (true) to hook a pole whose sun says can hook; false lets go of the rope
headingnumber–target heading, deg clockwise from north
leftnumber–turn the heading target this many degrees left of the nose
reelstring–on a taut rope: steer into the pole, away from it, or neither
rightnumber–turn the heading target this many degrees right of the nose
speednumber–target speed, 12 to 38 m/s (cruise 20)
stepsinteger–slices of 0.25 s to fly (1 if left out); stops early when something changes on screen

No output schema declared.

No examples provided.

restart ~28

Start the run again, short of the first point and heading along the line. Clears the autopilot.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_targets ~132

Set targets the in-game autopilot flies toward: it banks to reach the heading, pitches to reach the altitude, and boosts or air-brakes to hold the speed the throttle asks for (cruising is 20 m/s). Omit a field to leave it alone, or pass null to let go of it.

NameTypeReqDescription
altitudenumber|null–m; below 1 m the plane crashes
headingnumber|null–deg clockwise from north
throttle––target speed: 0 is 12 m/s, 1 is 38 m/s; held with boost and air brake

No output schema declared.

No examples provided.

Install

How do I install the Trazo pilot MCP server?

Trazo pilot runs locally as an npm package, launched with npx -y trazo-pilot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · trazo-pilot

# add to Claude Code
claude mcp add allyburns-trazo-pilot -- npx -y trazo-pilot
Common questions

What is the Trazo pilot MCP server?

Trazo pilot is an MCP server listed in the public MCP registry as io.github.allyburns/trazo-pilot. Fly Trazo, a browser game over the real Nazca lines, turn by turn, and post to its AI board. This page covers its npm package (trazo-pilot).

Is the Trazo pilot MCP server safe to use?

Trazo pilot scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Trazo pilot MCP server expose?

Trazo pilot exposes 12 tools: pilot_help, pilot_state, pilot_step, pilot_pause, pilot_resume, and 7 more. Their descriptions and schemas cost roughly 964 tokens of context every time the server is loaded.

Is the Trazo pilot MCP server still maintained?

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

What licence is the Trazo pilot MCP server under?

Trazo pilot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Trazo pilot MCP server?

VerifyMCP ran 16 checks on Trazo pilot, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.