OSCAR
NPM · CREATEWITHOSCAR
An assistant reads your OSCAR installation (OSC, MIDI, DMX) and drafts interfaces you review.
Available components
Last scanned (2 hours ago)
Scores higher than 90% of npm servers
Category IoT and Hardware
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (BSD-3-Clause).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1226 tokens (~111/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 20 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.
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/createwithoscar@1.0.2
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
create_draft Save a draft for the person to review ~139
Validate an interface and, if it is clean, save it as a draft: it appears in OSCAR under File > Open project or template, with a Draft badge. It is a file for a person to review: nothing is published, nothing is sent, and no project is changed. An existing draft of the same name is only replaced when overwrite is true.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The whole HTML document |
| name | string | yes | The draft's name, shown in File > Open project or template (up to 80 characters; longer is cut) |
| overwrite | boolean|string | – | Replace an existing draft of the same name |
No output schema declared.
No examples provided.
describe_widgets The widgets and how to write them ~46
Every widget OSCAR has -- tag, attributes, defaults, and each setting with its type, options and meaning -- plus how an interface is written as HTML. Read this before building one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
installation_map The installation, as OSCAR knows it ~152
One picture of the whole installation: this computer's network addresses and ports, its MIDI ports and USB interfaces (a USB DMX interface among them), and everything the published interfaces talk to and listen for -- each OSC destination with the addresses sent to it, each MIDI port with its channels and controllers, each DMX output with its universe and channels -- with the control and interface behind every one. notices lists what does not add up: a MIDI port or USB interface that is not there, OSC followed while OSCAR cannot listen, two controls on the same DMX channels. It is worked out from settings and sends nothing onto the network: it says where OSCAR sends, not whether anything is there to hear it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects The projects in OSCAR ~52
Every project OSCAR holds, with its id and its title, as File > Open project or template lists them. A project is what a person edits; it reaches phones only once it is published (list_published).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_published The published interfaces ~84
Every published interface: its name, the project it was published from, the path it is served at, who can open it (access: "network", or "off" for one no device can open, whose schedules and bridges still run), and how many widgets it holds. Published interfaces are running -- phones and tablets may be on them, and the rig hears them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
midi_ports The MIDI ports ~24
The MIDI inputs and outputs this machine has right now, and the driver's condition.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_project A project's widgets ~102
Every widget in one project, published or not, with its full settings as the editor holds them: addresses, ports, channels, MIDI mappings, DMX targets. Also says where the project is published, if it is. A setting nobody touched reads as its default. What phones see is the published copy, which may be older: read_published reads that one.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | The project's id, or its title, as list_projects gives them |
No output schema declared.
No examples provided.
read_published A published interface's widgets ~67
Every widget on one published interface, with its full settings as phones have them: addresses, ports, channels, MIDI mappings, DMX targets. For answering why something does or does not respond.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The published interface's id, as list_published names it |
No output schema declared.
No examples provided.
recent_activity What the server has lately done ~187
The network log's recent rows: what OSCAR's server actually received and sent, oldest first, repeats within a moment gathered into one row with a count n. Each row has what (OSC address, MIDI control, DMX universe and channels) and value (what the latest carried). Incoming rows: device (the sender's address, or the MIDI port), surfaces (published interfaces that follow it), canvas (the editor's canvas followed it); with neither, nothing follows it. Outgoing rows: to (where it went), origin (whose move: canvas, local, internet, schedule, bridge), surface (the published interface) and widget. dropped, on either, says why it was refused. The first place to look when something moves that should not, or does not move when it should.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many of the newest rows (default 50) |
No output schema declared.
No examples provided.
status What this OSCAR is ~50
OSCAR's version, its ports (HTTP, the fixed OSC listening port, the socket bridge), whether editing is locked, the MIDI driver's condition, and how many projects and published interfaces there are. Start here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_draft Judge a draft ~57
Run an interface written as HTML through the widgets' own validators: unknown settings, values their panels would refuse, missing or repeated ids. Returns the complaints to correct. Nothing is saved.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | The whole HTML document |
No output schema declared.
No examples provided.
How do I install the OSCAR MCP server?
OSCAR runs locally as an npm package, launched with npx -y createwithoscar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · createwithoscar
claude mcp add trafalmejo-oscar -- npx -y createwithoscar
What is the OSCAR MCP server?
OSCAR is an MCP server listed in the public MCP registry as io.github.trafalmejo/oscar. An assistant reads your OSCAR installation (OSC, MIDI, DMX) and drafts interfaces you review. This page covers its npm package (createwithoscar).
Is the OSCAR MCP server safe to use?
OSCAR scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 OSCAR MCP server expose?
OSCAR exposes 11 tools: status, list_projects, read_project, list_published, read_published, and 6 more. Their descriptions and schemas cost roughly 960 tokens of context every time the server is loaded.
Is the OSCAR MCP server still maintained?
OSCAR 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 OSCAR MCP server under?
OSCAR declares the BSD-3-Clause licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.