io.github.brac/particlr-mcp
NPM · @PARTICLR/MCP · SCANNED SEP 20
Agents author particlr .prt particle effects headlessly: validate, simulate, render to PNG, patch.
Available components
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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 34 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1435 tokens (~119/item across 12 items; 9 tools + 3 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.brac/particlr-mcp server?
io.github.brac/particlr-mcp runs locally as an npm package, launched with npx -y @particlr/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @particlr/mcp
claude mcp add brac-particlr-mcp -- npx -y @particlr/mcp
{
"mcpServers": {
"brac-particlr-mcp": {
"command": "npx",
"args": [
"-y",
"@particlr/mcp"
]
}
}
} {
"servers": {
"brac-particlr-mcp": {
"command": "npx",
"args": [
"-y",
"@particlr/mcp"
]
}
}
} codex mcp add brac-particlr-mcp -- npx -y @particlr/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"brac-particlr-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@particlr/mcp"
],
"enabled": true
}
}
} openclaw mcp add brac-particlr-mcp --command npx --arg -y --arg @particlr/mcp
mcp_servers:
brac-particlr-mcp:
command: "npx"
args: ["-y", "@particlr/mcp"] {
"McpServers": {
"brac-particlr-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@particlr/mcp"
]
}
}
} assistant mcp add brac-particlr-mcp -t stdio -c npx -a -y @particlr/mcp
{
"mcpServers": {
"brac-particlr-mcp": {
"command": "npx",
"args": [
"-y",
"@particlr/mcp"
]
}
}
} 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 Sept 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.
- 18 Sept 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 −1
- Stability: pass → 0.97 functional
- 13 Sept 26 +1
- Stability: 0.97 → pass security
- 11 Sept 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.
- 9 Sept 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.
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 20 Sept 2026 · Analysed npm/@particlr/mcp@0.2.0
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 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
get_effect Get Effect ~58
Fetch the canonical stored .prt text for a handle — use this for final delivery/export after iterating. Handles live only for this session (server process); they do not survive a reconnect.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | A handle from open_effect. |
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | yes | The canonical stored .prt text — for final delivery/export. |
| handle | string | yes | – |
No examples provided.
get_preset Get Preset ~61
Fetch one shipped preset by name (stem): its raw .prt text plus a parsed summary. Unknown name returns an error listing the valid names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The preset filename stem (see list_presets), e.g. "explosion". |
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | yes | The preset's raw .prt JSON text. |
| name | string | yes | – |
| summary | object | yes | – |
No examples provided.
get_reference Get Reference ~104
Fetch reference material inline: topic "format-spec" (the .prt format spec, markdown) or "schema" (the JSON Schema for a .prt document).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | "format-spec" = the .prt format spec (markdown); "schema" = the JSON Schema for a .prt document; "authoring-guide" = how to author a .prt that LOOKS good (units, blend/layer/curve/trail recipes, comm… |
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | – |
| text | string | yes | – |
| topic | string | yes | – |
No examples provided.
list_presets List Presets ~32
List the shipped .prt presets (name, layer count, schemaVersion) — the few-shot authoring corpus.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| presets | array | yes | – |
No examples provided.
open_effect Open Effect ~111
Validate a .prt document and store it under a session handle so you can iterate without resending the text. Returns the handle + validate fields (ok, schemaVersion, warnings, errors); pass the handle to patch_effect / validate_effect / simulate_effect / render_effect. Handles live only for this session (server process); they do not survive a reconnect. Capped at 64 per session.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | yes | The .prt document as a JSON string. Validated and stored under a fresh handle. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| handle | string|null | yes | A session handle ("fx-1", …) to pass as `handle` to patch/validate/simulate/render; null on failure. |
| migratedFrom | number|null | yes | The doc's ORIGINAL schemaVersion if it was migrated up, else null. |
| ok | boolean | yes | – |
| schemaVersion | number|null | yes | – |
| warnings | array | yes | – |
No examples provided.
patch_effect Patch Effect ~156
Apply a small list of RFC 6902 ops (replace/add/remove) to a stored effect, then re-validate. Iterate by sending only the diff, not the whole document. Any failure — bad path/index or a post-patch validation error — rolls back: the stored doc is left unchanged and the failing op index is named. Handles live only for this session (server process); they do not survive a reconnect.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | A handle from open_effect. |
| ops | array | yes | Restricted RFC 6902 ops (replace/add/remove) applied IN ORDER (max 64). Any failure — bad path, bad index, or a post-patch validation error — rolls back: the stored doc is unchanged. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| handle | string|null | yes | A session handle ("fx-1", …) to pass as `handle` to patch/validate/simulate/render; null on failure. |
| migratedFrom | number|null | yes | The doc's ORIGINAL schemaVersion if it was migrated up, else null. |
| ok | boolean | yes | – |
| schemaVersion | number|null | yes | – |
| warnings | array | yes | – |
No examples provided.
render_effect Render Effect ~523
CPU-rasterize a .prt effect to PNG image(s): by default one contact-sheet PNG of 16 frames evenly spaced over [0, completion||duration], auto-framed. All builtin + embedded-PNG textures, all five blend modes, flipbook, stretch/velocity-align/flip, per-particle + connect-ribbon TRAILS, and layer draw order are rendered; DISSOLVE is NOT rasterized (a dissolve doc still renders its sprites). Deterministic: frames snap to the same 1/60 trajectory as simulate_effect. Returns image block(s) + a renderHash, the snapped times, the viewport, and the grid. An invalid doc returns validate-shaped errors.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | – | Background: "checker" (default), "transparent", or a hex color (#rgb / #rrggbb / #rrggbbaa). |
| doc | string | – | The .prt document as a JSON string. |
| fps | number | – | Frames at 0, 1/fps, 2/fps … up to the range end (max 240). Overrides `frames`. |
| frames | integer | – | Number of evenly-spaced frames over [0, completion||duration]. Default 16; max 64. |
| handle | string | – | A handle from open_effect — use instead of doc to avoid resending the document. |
| height | integer | – | Frame height in px. Default 256; cap 1024 longest edge. |
| layout | string | – | "sheet" (default): one contact-sheet PNG. "separate": one PNG per frame (same caps). |
| overrunSeconds | number | – | Render past the loop seam: extends the frames/fps time range to duration + overrunSeconds. Looping docs only; ignored (with a warning) otherwise. Explicit `times` already accept any time. |
| seed | integer | – | Override the doc's authored seed. Default: the doc's seed. |
| supersample | number | – | Anti-alias by rendering at 2x/4x then downsampling. Default off (crisp, byte-golden). |
| times | array | – | Explicit render times in seconds (snapped to 1/60 boundaries). Max 64 entries, each <= 60s. Overrides frames/fps. |
| viewport | object | – | Explicit world-space viewport. Auto-framed from a bounds scan (+12% margin) when omitted. |
| width | integer | – | Frame width in px. Default 256; cap 1024 longest edge. |
| Name | Type | Req | Description |
|---|---|---|---|
| completionTime | number|null | yes | – |
| frameHeight | integer | yes | – |
| frameWidth | integer | yes | – |
| grid | – | yes | Contact-sheet grid; null in separate mode. |
| imageCount | integer | yes | – |
| layout | string | yes | – |
| renderHash | string | yes | hex8 over normalizedDoc + seed + snapped times + size + viewport + bg — distinct from the sim statehash. |
| snappedTimes | array | yes | The actual step-snapped render times (seconds). |
| viewport | object | yes | – |
| warnings | array | yes | – |
No examples provided.
simulate_effect Simulate Effect ~226
Deterministically step a .prt effect in Node (no rendering) and report per-layer live counts over time, peak vs capacity, spatial bounds, completion, and a statehash plus the exact {seed, dt, steps} to reproduce it. Same seed + dt sequence => identical output. Validates first; an invalid doc returns validate-shaped errors.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | – | The .prt document as a JSON string. |
| dt | number | – | Fixed timestep. Default 1/60; clamped to [0.001, 0.05] (the runtime MAX_DT). |
| duration | number | – | Seconds to simulate. Default 3; capped at 60. |
| handle | string | – | A handle from open_effect — use instead of doc to avoid resending the document. |
| sampleInterval | number | – | Seconds between count samples. Default 0.1; floor 0.001, widened if it would emit more than 4096 samples. |
| seed | integer | – | Override the doc's authored seed. Default: the doc's seed. |
| Name | Type | Req | Description |
|---|---|---|---|
| bounds | – | yes | Axis-aligned bounds over every live particle across the run; null if none ever spawned. |
| completed | boolean | yes | True if the effect reached isDone (one-shots); false for looping/unfinished. |
| completionTime | number|null | yes | Seconds at which isDone first held; null if never. |
| echo | object | yes | The exact inputs used after defaulting/clamping — replay these for an identical statehash. |
| layers | array | yes | – |
| statehash | string | yes | hex8 FNV-1a over the final public sim state — reproducible per {seed, dt, steps}. |
| warnings | array | yes | – |
No examples provided.
validate_effect Validate Effect ~98
Validate a .prt document (JSON string) against the real parse -> migrate -> validate pipeline. Returns ok + the canonical normalized doc + schemaVersion (and the pre-migration version), or structured, path-anchored errors worded for you to fix.
| Name | Type | Req | Description |
|---|---|---|---|
| doc | string | – | The .prt document as a JSON string. |
| handle | string | – | A handle from open_effect — use instead of doc to avoid resending the document. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| migratedFrom | number|null | yes | The doc's ORIGINAL schemaVersion if it was migrated up, else null. |
| normalizedDoc | string|null | yes | Canonical serializeParticle() output on success (agents iterate on this); null on failure. |
| ok | boolean | yes | – |
| schemaVersion | number|null | yes | The doc's schemaVersion after migration; null when parsing failed. |
| warnings | array | yes | – |
No examples provided.
What is the io.github.brac/particlr-mcp server?
io.github.brac/particlr-mcp is listed in the public MCP registry as io.github.brac/particlr-mcp. Agents author particlr .prt particle effects headlessly: validate, simulate, render to PNG, patch. This page covers its npm package (@particlr/mcp).
Is the io.github.brac/particlr-mcp server safe to use?
io.github.brac/particlr-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.brac/particlr-mcp server expose?
io.github.brac/particlr-mcp exposes 9 tools: validate_effect, simulate_effect, list_presets, get_preset, get_reference, and 4 more. Their descriptions and schemas cost roughly 1,369 tokens of context every time the server is loaded.
Is the io.github.brac/particlr-mcp server still maintained?
io.github.brac/particlr-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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.brac/particlr-mcp server under?
io.github.brac/particlr-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.