Clutter
NPM · CLUTTER-MCP · SCANNED SEP 20
Generate synthetic companies, documents & data via the Clutter API (e.g. to fill SharePoint).
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 96 dependencies flagged as unhealthy. View diagnostics → Partial
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 78 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 970 tokens (~48/item across 20 items; 20 tools + 0 resources), lean.Pass
- 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 Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_project" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 20 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 Clutter MCP server?
Clutter runs locally as an npm package, launched with npx -y clutter-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 · clutter-mcp
claude mcp add michaelhologram-clutter-mcp -- npx -y clutter-mcp
{
"mcpServers": {
"michaelhologram-clutter-mcp": {
"command": "npx",
"args": [
"-y",
"clutter-mcp"
]
}
}
} {
"servers": {
"michaelhologram-clutter-mcp": {
"command": "npx",
"args": [
"-y",
"clutter-mcp"
]
}
}
} codex mcp add michaelhologram-clutter-mcp -- npx -y clutter-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"michaelhologram-clutter-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"clutter-mcp"
],
"enabled": true
}
}
} openclaw mcp add michaelhologram-clutter-mcp --command npx --arg -y --arg clutter-mcp
mcp_servers:
michaelhologram-clutter-mcp:
command: "npx"
args: ["-y", "clutter-mcp"] {
"McpServers": {
"michaelhologram-clutter-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"clutter-mcp"
]
}
}
} assistant mcp add michaelhologram-clutter-mcp -t stdio -c npx -a -y clutter-mcp
{
"mcpServers": {
"michaelhologram-clutter-mcp": {
"command": "npx",
"args": [
"-y",
"clutter-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 0
- Security disclosure: fail → unverified ▼ functional
- 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 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 11 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.
- 10 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
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/clutter-mcp@0.1.4
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 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
build_org Build organisation (async) ~179
Start building a synthetic organisation from a prompt. Returns 202 with an orgId. The build runs in the background (minutes) — then poll get_org, or call wait_for_org to block until ready. Omit projectId to auto-create a project (named after the generated company) — the simplest path.
| Name | Type | Req | Description |
|---|---|---|---|
| locale_language | string | – | BCP-47, e.g. en-US |
| projectId | string | – | Existing project to build into; OMIT to auto-create one |
| projectName | string | – | Name for the auto-created project (optional) |
| prompt | string | yes | – |
| ref_org_id | string | – | Build a variant FROM an existing org |
| target_systems | array | – | – |
| web_search | boolean | – | Use web search for real-world grounding (default true; set false to disable) |
No output schema declared.
No examples provided.
build_zip Build run ZIP (async) ~35
Start building a single ZIP of all of a run's documents. Poll get_zip_url after.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
No output schema declared.
No examples provided.
clutter_whoami Who am I ~22
Return the authenticated Clutter user for the configured API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_project Create project ~30
Create a new Clutter project. Returns the project (with its id).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
create_run Create generation run (async) ~158
Launch a generation run. Returns 202 with a runId — poll get_run or call wait_for_run. kind + params: • doc_generator → { prompt, doc_number (≤300), file_types:[docx|pdf|xlsx|eml|jpg], structure:'flat'|'nested', target_system?, allow_underscores? } • data_generator → { prompt, row_count (≤2000), data_format:'xlsx'|'csv'|'json', data_fields?, target_system? } • doc_metadata_gen → { sourceRunId (a completed doc_generator run), data_format, data_fields?, target_system? }
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| orgId | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
delete_org Delete organisation ~36
Delete an organisation and ALL its runs/artefacts (S3 + DB). Irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| orgId | string | yes | – |
No output schema declared.
No examples provided.
delete_project Delete project ~46
Delete a project and EVERYTHING under it — all its organisations, runs, datasets, metadata and artefacts (S3 + DB). Irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
No output schema declared.
No examples provided.
delete_run Delete run ~39
Delete a run and its artefacts (S3 + DB). Leaves the parent org intact. Irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
No output schema declared.
No examples provided.
get_document_url Get document download URL ~31
Get a short-lived presigned download URL for a single generated document.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | – |
No output schema declared.
No examples provided.
get_org Get organisation ~31
Get an organisation including its full org.json structure. Check `org.status`.
| Name | Type | Req | Description |
|---|---|---|---|
| orgId | string | yes | – |
No output schema declared.
No examples provided.
get_run Get run status ~32
Get a run's status + progress counts. Poll this until status is terminal.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
No output schema declared.
No examples provided.
get_usage Get API usage ~36
Your Clutter API usage (request counts by route) over a rolling window + the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| windowHours | integer | – | – |
No output schema declared.
No examples provided.
get_zip_url Get run ZIP URL ~36
Get a presigned download URL for a run's ZIP (409 until the build is ready).
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
No output schema declared.
No examples provided.
list_orgs List organisations ~25
List the synthetic organisations in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
No output schema declared.
No examples provided.
list_projects List projects ~21
List all of your Clutter projects (top-level tenant containers).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_run_documents List run documents ~34
List the documents generated by a run (title, format, folderPath, status).
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
No output schema declared.
No examples provided.
list_runs List runs ~24
List the generation runs under an organisation.
| Name | Type | Req | Description |
|---|---|---|---|
| orgId | string | yes | – |
No output schema declared.
No examples provided.
query_org Query organisation ~48
Ask a grounded natural-language question about an organisation (synchronous, one-shot answer).
| Name | Type | Req | Description |
|---|---|---|---|
| locale_language | string | – | – |
| message | string | yes | – |
| orgId | string | yes | – |
No output schema declared.
No examples provided.
wait_for_org Wait for organisation build ~53
Poll an org until its build reaches a terminal state (ready/failed) or the timeout. Returns the final org summary.
| Name | Type | Req | Description |
|---|---|---|---|
| orgId | string | yes | – |
| timeoutSeconds | integer | – | default 600 |
No output schema declared.
No examples provided.
wait_for_run Wait for run ~54
Poll a run until it reaches a terminal state (complete/partial/failed) or the timeout. Returns the final run status.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
| timeoutSeconds | integer | – | default 600 |
No output schema declared.
No examples provided.
What is the Clutter MCP server?
Clutter is an MCP server listed in the public MCP registry as io.github.michaelhologram/clutter-mcp. Generate synthetic companies, documents & data via the Clutter API (e.g. to fill SharePoint). This page covers its npm package (clutter-mcp).
Is the Clutter MCP server safe to use?
Clutter scores 79 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 Clutter MCP server expose?
Clutter exposes 20 tools: clutter_whoami, get_usage, list_projects, create_project, delete_project, and 15 more. Their descriptions and schemas cost roughly 970 tokens of context every time the server is loaded.
Is the Clutter MCP server still maintained?
Clutter 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 Clutter MCP server under?
Clutter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.