io.github.n1m21n/infinite-engine
NPM · INFINITE-ENGINE
Infinite audiovisual engine for AI agents: sound, shaders and video patches. Free, MIT.
Available components
Last scanned (2 minutes ago)
Scores higher than 34% of npm servers
Category Design and Media
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 (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 975 tokens (~108/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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.
- 6 Nov 26 +20
- Malware scan: unverified → pass ▲ security
- Source repository: unverified → pass ▲ security
- 5 Nov 26 46
First indexed and scored.
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 6 Nov 2026 · Analysed npm/infinite-engine@1.0.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 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 →
infinite_process_field_effect ~84
process audio through an inline field effect per-sample dsp filter or wavefolder kernel
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | field audio effect code (e.g. 'out = tanh(in * 2.5) * 0.7;') |
| duration | number | – | duration in seconds |
| out_wav | string | – | optional output .wav path |
No output schema declared.
No examples provided.
infinite_render_field_modifier ~91
deform procedural 3d mesh topology using inline field deformation expressions
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | field mesh deformer equation (e.g. 'P.y += sin(P.x * 3.0 + t) * 0.25; Cd = vec3(0.96, 0.5, 0.4);') |
| out_png | string | – | output png file path |
No output schema declared.
No examples provided.
infinite_render_field_pixel ~79
render an audio-reactive or procedural pixel shader using infinite field pixel node to a png frame
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | field pixel shader code (e.g. 'col = vec3(uv.x, uv.y, sin(t)*0.5+0.5);') |
| out_png | string | – | output png file path |
No output schema declared.
No examples provided.
infinite_render_field_primitive ~138
render dynamic parametric mathematical surfaces (plane, sphere, torus) via field primitive equations
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | field 3d primitive equation (e.g. 'P = vec3(uv.x - 0.5, sin(length(uv)*5.0 - t)*0.3, uv.y - 0.5); Cd = vec3(0.9, 0.4, 0.2);') |
| out_png | string | – | output png file path |
| topology | number | – | 0 for plane grid, 1 for sphere, 2 for torus |
No output schema declared.
No examples provided.
infinite_render_sketch3d ~137
render procedural 3d geometry generated via algorithmic javascript to a png frame
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | javascript 3d sketch code (e.g. 'function draw(t) { rotateY(t * 0.8); fill(0.2, 0.6, 0.9); torus(1.2, 0.4, 24, 24); }') |
| height | number | – | frame height in pixels (default 720) |
| out_png | string | – | output png file path |
| width | number | – | frame width in pixels (default 720) |
No output schema declared.
No examples provided.
infinite_render_video ~80
render an mp4 video from an infinite patch file headlessly
| Name | Type | Req | Description |
|---|---|---|---|
| duration | number | – | duration in seconds (default 5.0) |
| fps | number | – | frames per second (default 30) |
| out_mp4 | string | yes | output mp4 file path |
| patch_path | string | yes | path to .inf patch file |
No output schema declared.
No examples provided.
infinite_synthesize_field_notes ~116
generate algorithmic midi sequences and euclidean rhythms with field notes node into audio
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | field notes logic (e.g. 'if (tick(1/8) > 0.5) { note(deg(floor(rand() * 7)), 0.8, 1/8) }') |
| duration | number | – | duration in seconds |
| out_wav | string | – | optional output .wav path |
| synth_type | string | – | synth engine to receive notes |
No output schema declared.
No examples provided.
infinite_synthesize_field_synth ~117
synthesize wav audio from an inline field synth per-sample dsp kernel using infinite c++ engine
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | field dsp code (e.g. 'state float phase = 0\nphase = (phase + freq / sr) % 1.0\nout = sin(6.28318 * phase) * 0.4 * gate') |
| duration | number | – | duration in seconds (default 3.0) |
| out_wav | string | – | optional output .wav path |
No output schema declared.
No examples provided.
infinite_validate_patch ~37
validate an infinite modular patch text file against the c++ compiler
| Name | Type | Req | Description |
|---|---|---|---|
| patch_text | string | yes | content of an .inf patch file |
No output schema declared.
No examples provided.
How do I install the io.github.n1m21n/infinite-engine MCP server?
io.github.n1m21n/infinite-engine runs locally as an npm package, launched with npx -y infinite-engine. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · infinite-engine
claude mcp add n1m21n-infinite-engine -- npx -y infinite-engine
What is the io.github.n1m21n/infinite-engine MCP server?
io.github.n1m21n/infinite-engine is an MCP server listed in the public MCP registry as io.github.n1m21n/infinite-engine. Infinite audiovisual engine for AI agents: sound, shaders and video patches. Free, MIT. This page covers its npm package (infinite-engine).
Is the io.github.n1m21n/infinite-engine MCP server safe to use?
io.github.n1m21n/infinite-engine scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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 io.github.n1m21n/infinite-engine MCP server expose?
io.github.n1m21n/infinite-engine exposes 9 tools: infinite_synthesize_field_synth, infinite_synthesize_field_notes, infinite_process_field_effect, infinite_render_sketch3d, infinite_render_field_primitive, and 4 more. Their descriptions and schemas cost roughly 879 tokens of context every time the server is loaded.
Is the io.github.n1m21n/infinite-engine MCP server still maintained?
io.github.n1m21n/infinite-engine is still listed as active in the MCP registry. We last reached this channel on 6 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 io.github.n1m21n/infinite-engine MCP server under?
io.github.n1m21n/infinite-engine 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 io.github.n1m21n/infinite-engine MCP server?
VerifyMCP ran 15 checks on io.github.n1m21n/infinite-engine, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.n1m21n/infinite-engine: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.