Practonaut
NPM · PRACTONAUT
Local practice gym for AI agents on real apps: practice Excalidraw tasks, get a reproducible score.
Available components
Last scanned (10 hours ago)
Scores higher than 81% of npm servers
Category Testing and QA
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 Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 1 of 7 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to godarg/practonaut). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 824 tokens (~103/item across 8 items; 7 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +2
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
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 5 Nov 2026 · Analysed npm/practonaut@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | godarg/practonaut |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/godarg/practonaut/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 3283525901 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5260228a0d70afca340fb57522ad6c27a88110b000352b1cb55d7469f83d3e743671f290380a519dca076e276f171684922b0ebe51b12f4423e013680 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 7 packages
| Packages resolved | 7 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
act ~161
Apply exactly one action. Arguments: name (an action from list_actions), params (exactly that action's parameters), baseStep (the current step) and expectedRevision (the current revision), both from the latest observe or act reply; optional lang. On success the reply gives the new step and revision, the objects that changed (as they are now), the ids created and removed, and the current error explanations. A rejected action changes nothing: read error.code and error.message (a stale step or revision names the current ones), then choose a valid action. Never guess step or revision.
| Name | Type | Req | Description |
|---|---|---|---|
| baseStep | integer | yes | – |
| expectedRevision | integer | yes | – |
| lang | string | – | – |
| name | string | yes | – |
| params | – | yes | – |
No output schema declared.
No examples provided.
check_result ~112
Check whether the current state meets the task's goal conditions: passed plus one met/unmet entry per condition with its sentence and formal form, the same check a human player gets. Argument: expectedRevision (the current revision); optional lang. Checking changes nothing on the board. If observe shows limits.checks, each check uses one (checksRemaining says how many are left) and a used-up limit is refused with check_budget_exhausted.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedRevision | integer | yes | – |
| lang | string | – | – |
No output schema declared.
No examples provided.
explain_result ~46
Read the result of the last check and the player-visible explanations of errors in the current state. Optional lang. Changes nothing and never reveals hidden evaluation data.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
No output schema declared.
No examples provided.
list_actions ~69
List the actions this session accepts, each with its parameters: type (id, nullable-id, string, integer, enum, end), bounds and allowed values. Id parameters take ids from observe's state.objects; ids of new objects appear in the created list of the reply to the action that creates them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
observe ~152
Start here and call again whenever unsure. Returns the shared practice session as JSON: task (title, prompt and the goal conditions, each a sentence plus its formal form), state.objects (the live frames, steps and arrows keyed by id, with labels, positions, styles and arrow ends), step and revision (copy both into act), recent history, the last check and player-visible error explanations. Optional: detail "full" adds the action definitions, rules, task list and complete history; lang "en" (default), "de" or "both"; history = how many recent history items (default 5).
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
| history | integer | – | – |
| lang | string | – | – |
No output schema declared.
No examples provided.
reset ~69
Discard every action of this attempt and return to the starting state. Arguments: expectedRevision (the current revision) and confirmed: true; optional lang. The reply lists what changed, like act.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | – |
| expectedRevision | integer | yes | – |
| lang | string | – | – |
No output schema declared.
No examples provided.
undo ~49
Undo the most recent action. Argument: expectedRevision (the current revision); optional lang. The reply lists what changed, like act.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedRevision | integer | yes | – |
| lang | string | – | – |
No output schema declared.
No examples provided.
How do I install the Practonaut MCP server?
Practonaut runs locally as an npm package, launched with npx -y practonaut mcp --task excalidraw/connect. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
npm · practonaut
claude mcp add godarg-practonaut -- npx -y practonaut mcp --task excalidraw/connect
What is the Practonaut MCP server?
Practonaut is an MCP server listed in the public MCP registry as io.github.godarg/practonaut. Local practice gym for AI agents on real apps: practice Excalidraw tasks, get a reproducible score. This page covers its npm package (practonaut).
Is the Practonaut MCP server safe to use?
Practonaut scores 84 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Practonaut MCP server expose?
Practonaut exposes 7 tools: observe, list_actions, act, undo, reset, and 2 more. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.
Is the Practonaut MCP server still maintained?
Practonaut is still listed as active in the MCP registry. We last reached this channel on 5 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 Practonaut MCP server under?
Practonaut declares the Apache-2.0 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 Practonaut MCP server?
VerifyMCP ran 16 checks on Practonaut, 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.