Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Clutter

NPM · CLUTTER-MCP

Generate synthetic companies, documents & data via the Clutter API (e.g. to fill SharePoint).

Available components

0 this week 75 Trust /100

Last scanned (9 hours ago)

Scores higher than 50% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Changelog

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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +1
    • Stability: 0.87 → pass security
Diagnostics

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/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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~970 tokens

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 →

Tool Tokens
build_org ~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.

NameTypeReqDescription
locale_languagestring–BCP-47, e.g. en-US
projectIdstring–Existing project to build into; OMIT to auto-create one
projectNamestring–Name for the auto-created project (optional)
promptstringyes–
ref_org_idstring–Build a variant FROM an existing org
target_systemsarray––
web_searchboolean–Use web search for real-world grounding (default true; set false to disable)

No output schema declared.

No examples provided.

build_zip ~35

Start building a single ZIP of all of a run's documents. Poll get_zip_url after.

NameTypeReqDescription
runIdstringyes–

No output schema declared.

No examples provided.

clutter_whoami ~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 ~30

Create a new Clutter project. Returns the project (with its id).

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

create_run ~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? }

NameTypeReqDescription
kindstringyes–
orgIdstringyes–
paramsobject––

No output schema declared.

No examples provided.

delete_org ~36

Delete an organisation and ALL its runs/artefacts (S3 + DB). Irreversible.

NameTypeReqDescription
orgIdstringyes–

No output schema declared.

No examples provided.

delete_project ~46

Delete a project and EVERYTHING under it — all its organisations, runs, datasets, metadata and artefacts (S3 + DB). Irreversible.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

delete_run ~39

Delete a run and its artefacts (S3 + DB). Leaves the parent org intact. Irreversible.

NameTypeReqDescription
runIdstringyes–

No output schema declared.

No examples provided.

get_document_url ~31

Get a short-lived presigned download URL for a single generated document.

NameTypeReqDescription
documentIdstringyes–

No output schema declared.

No examples provided.

get_org ~31

Get an organisation including its full org.json structure. Check `org.status`.

NameTypeReqDescription
orgIdstringyes–

No output schema declared.

No examples provided.

get_run ~32

Get a run's status + progress counts. Poll this until status is terminal.

NameTypeReqDescription
runIdstringyes–

No output schema declared.

No examples provided.

get_usage ~36

Your Clutter API usage (request counts by route) over a rolling window + the daily quota.

NameTypeReqDescription
windowHoursinteger––

No output schema declared.

No examples provided.

get_zip_url ~36

Get a presigned download URL for a run's ZIP (409 until the build is ready).

NameTypeReqDescription
runIdstringyes–

No output schema declared.

No examples provided.

list_orgs ~25

List the synthetic organisations in a project.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

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 ~34

List the documents generated by a run (title, format, folderPath, status).

NameTypeReqDescription
runIdstringyes–

No output schema declared.

No examples provided.

list_runs ~24

List the generation runs under an organisation.

NameTypeReqDescription
orgIdstringyes–

No output schema declared.

No examples provided.

query_org ~48

Ask a grounded natural-language question about an organisation (synchronous, one-shot answer).

NameTypeReqDescription
locale_languagestring––
messagestringyes–
orgIdstringyes–

No output schema declared.

No examples provided.

wait_for_org ~53

Poll an org until its build reaches a terminal state (ready/failed) or the timeout. Returns the final org summary.

NameTypeReqDescription
orgIdstringyes–
timeoutSecondsinteger–default 600

No output schema declared.

No examples provided.

wait_for_run ~54

Poll a run until it reaches a terminal state (complete/partial/failed) or the timeout. Returns the final run status.

NameTypeReqDescription
runIdstringyes–
timeoutSecondsinteger–default 600

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add michaelhologram-clutter-mcp -- npx -y clutter-mcp
Common questions

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 75 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 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 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 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.