# io.github.n1m21n/infinite-engine (npm · infinite-engine)

Infinite audiovisual engine for AI agents: sound, shaders and video patches. Free, MIT.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- npm · `infinite-engine`: 66/100 (this document), [markdown](https://verifymcp.io/servers/n1m21n-infinite-engine/infinite-engine.md), [page](https://verifymcp.io/servers/n1m21n-infinite-engine/infinite-engine)

## Channel facts

- Registry: `npm`
- Package: `infinite-engine`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 975 tokens (~108/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add n1m21n-infinite-engine -- npx -y infinite-engine
```

### Cursor

```json
{
  "mcpServers": {
    "n1m21n-infinite-engine": {
      "command": "npx",
      "args": [
        "-y",
        "infinite-engine"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "n1m21n-infinite-engine": {
      "command": "npx",
      "args": [
        "-y",
        "infinite-engine"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add n1m21n-infinite-engine -- npx -y infinite-engine
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "n1m21n-infinite-engine": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "infinite-engine"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add n1m21n-infinite-engine --command npx --arg -y --arg infinite-engine
```

### Hermes

```yaml
mcp_servers:
  n1m21n-infinite-engine:
    command: "npx"
    args: ["-y", "infinite-engine"]
```

### Netclaw

```json
{
  "McpServers": {
    "n1m21n-infinite-engine": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "infinite-engine"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add n1m21n-infinite-engine -t stdio -c npx -a -y infinite-engine
```

### Other

```json
{
  "mcpServers": {
    "n1m21n-infinite-engine": {
      "command": "npx",
      "args": [
        "-y",
        "infinite-engine"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 66, +20)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Source repository: unverified → pass

### 2026-11-05 (score 46)

First indexed and scored.

## MCP tools (9)

### `infinite_synthesize_field_synth` (~117 tokens)

synthesize wav audio from an inline field synth per-sample dsp kernel using infinite c++ engine

Input parameters:

- `code` (string, required): 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

### `infinite_synthesize_field_notes` (~116 tokens)

generate algorithmic midi sequences and euclidean rhythms with field notes node into audio

Input parameters:

- `code` (string, required): 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

### `infinite_process_field_effect` (~84 tokens)

process audio through an inline field effect per-sample dsp filter or wavefolder kernel

Input parameters:

- `code` (string, required): 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

### `infinite_render_sketch3d` (~137 tokens)

render procedural 3d geometry generated via algorithmic javascript to a png frame

Input parameters:

- `code` (string, required): 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)

### `infinite_render_field_primitive` (~138 tokens)

render dynamic parametric mathematical surfaces (plane, sphere, torus) via field primitive equations

Input parameters:

- `code` (string, required): 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

### `infinite_render_field_modifier` (~91 tokens)

deform procedural 3d mesh topology using inline field deformation expressions

Input parameters:

- `code` (string, required): 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

### `infinite_render_field_pixel` (~79 tokens)

render an audio-reactive or procedural pixel shader using infinite field pixel node to a png frame

Input parameters:

- `code` (string, required): 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

### `infinite_validate_patch` (~37 tokens)

validate an infinite modular patch text file against the c++ compiler

Input parameters:

- `patch_text` (string, required): content of an .inf patch file

### `infinite_render_video` (~80 tokens)

render an mp4 video from an infinite patch file headlessly

Input parameters:

- `duration` (number): duration in seconds (default 5.0)
- `fps` (number): frames per second (default 30)
- `out_mp4` (string, required): output mp4 file path
- `patch_path` (string, required): path to .inf patch file

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/n1m21n-infinite-engine/infinite-engine#diagnostics

## Score history

- 2026-11-06: 66
- 2026-11-05: 46

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/infinite-engine
- Socket report: https://socket.dev/npm/package/infinite-engine
- Repository: https://github.com/n1m21n/Infinite
- Changelog RSS feed: https://verifymcp.io/servers/n1m21n-infinite-engine/infinite-engine.xml
- Changelog JSON feed: https://verifymcp.io/servers/n1m21n-infinite-engine/infinite-engine/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/n1m21n-infinite-engine/infinite-engine.json
- HTML version of this page: https://verifymcp.io/servers/n1m21n-infinite-engine/infinite-engine