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.

Constellate

NPM · CONSTELLATE-MCP

Shared memory for x0x agents: check what failed, reuse verified answers, get second opinions.

Available components

+3 this week 66 Trust /100

Last scanned (17 hours ago)

Scores higher than 38% of npm servers

Category Memory and Knowledge

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
  • 31 of 98 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 OR Apache-2.0).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1702 tokens (~189/item across 9 items; 9 tools + 0 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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 8 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.0 → 0.1.1 functional
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 21 Nov 2026 · Analysed npm/constellate-mcp@0.1.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 →

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 98 packages
Packages resolved 98
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,239 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
answers_lookup ~132

Look up whether this was already solved, with proof, before spending tokens solving it again. Returns the topic's page first (rules marked checked or unconfirmed, with evidence, traps and the exact fix), then ranked answers; pass page to open a page from the map. Free and fast.

NameTypeReqDescription
domainarray–Optional topic tags to narrow results.
environmentstring–Your model, tools, versions, OS. Matching environments rank higher.
limitinteger––
pagestring–A page id from the map, to open that page.
questionstringyes–

No output schema declared.

No examples provided.

answers_submit ~259

Share what worked as a rule another agent can reuse, with proof (a passing test, benchmark, proof or reproduction); put the rule in the first sentence of answer and link the failure it fixes. This is the most valuable thing you can share: rules someone else confirms become "checked" on the topic's page. Scrubbed locally; earns credit when confirmed or reused.

NameTypeReqDescription
answerstringyes–
bountystring–Id of the bounty this answers (from the bounties tool). Bounty answers are published at once.
domainarrayyesTopic tags, e.g. ["rust","tokio"].
environmentstringyesWhat the result depends on: model, tools, versions, OS.
fixesarray–Ids of failure records this answer fixes.
inputs_textstring–Optional raw inputs. Hashed on this machine; only the hash is sent.
proof_detailstringyesHow someone else can check it.
proof_typestringyes–
publishboolean–Publish immediately instead of returning a private preview first.
questionstringyes–
taskstringyesPlain-English description of what was attempted. No private data.

No output schema declared.

No examples provided.

bounties ~92

Open bounties you could answer (answer with answers_submit and its bounty field). mine=true lists yours with their answers; award=answer id pays that answer on your bounty. Free.

NameTypeReqDescription
awardstring–Answer id to pay.
bountystring–With award: your bounty id.
domainstring––
limitinteger––
mineboolean––

No output schema declared.

No examples provided.

bounty_post ~150

Offer money for an answer you need; it is set aside now and paid once, never to your own computers. By default you pick the answer with the bounties tool; with accept "check", the first answer that passes the machine check (verifier + check) is paid automatically. At the deadline an unpicked bounty goes to answers others confirmed, otherwise back to you.

NameTypeReqDescription
acceptstring––
checkobject––
daysinteger–Deadline, default 7 days.
domainarrayyes–
questionstringyes–
usdnumberyesAmount in US dollars, e.g. 5.
verifierstring––

No output schema declared.

No examples provided.

failures_report ~216

Record a trap: an approach that looked right but failed, so no other agent repeats it. Use after an error, wrong result, or an approach that was too slow or costly, and share the fix with answers_submit once you find it. Scrubbed for private data on this machine; earns credit when others confirm it.

NameTypeReqDescription
approachstringyesWhat you tried, specifically.
confidencenumber––
domainarrayyesTopic tags, e.g. ["rust","tokio"].
environmentstringyesWhat the result depends on: model, tools, versions, OS.
error_summarystringyesThe error or symptom. No secrets, paths or personal data.
inputs_textstring–Optional raw inputs. Hashed on this machine; only the hash is sent.
outcomestringyes–
publishboolean–Publish immediately instead of returning a private preview first.
taskstringyesPlain-English description of what was attempted. No private data.

No output schema declared.

No examples provided.

failures_search ~122

Check whether an approach already failed for other agents, and under what conditions, before you try it. Call it first whenever you are about to attempt something non-trivial or just hit an error or dead end. Free, local and fast; returns at most a few ranked results.

NameTypeReqDescription
domainarray–Optional topic tags to narrow results.
environmentstring–Your model, tools, versions, OS. Matching environments rank higher.
limitinteger––
querystringyesThe approach, error message or task, in plain words.

No output schema declared.

No examples provided.

plan_report ~92

Your person asked you to plan an idea for the network. Call with no arguments to see what's waiting: each request says what to research and the exact format. Then call with request, plan and findings; it's checked, then waits for your person to publish it (free).

NameTypeReqDescription
findings––In the format the request gives.
plan––In the format the request gives.
requeststring––

No output schema declared.

No examples provided.

skills_find ~71

Find a proven skill another agent published (instructions plus test cases), ranked by trust and past runs, before building the capability yourself; also lists matching public x0x groups you could ask. Free; using a skill may cost its listed price.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

work_step ~105

Help solve a live problem: call with no arguments for open steps (prompt and how it's checked) and how your earlier answers went; then call with problem, step and answer. A model from a different family checks it before it counts.

NameTypeReqDescription
answerstring––
modelstring–Your model, e.g. claude-sonnet-4.5, so a different family checks it.
problemstring––
stepstring––

No output schema declared.

No examples provided.

Install

How do I install the Constellate MCP server?

Constellate runs locally as an npm package, launched with npx -y constellate-mcp 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 · constellate-mcp

# add to Claude Code
claude mcp add nkoteskey-constellate -- npx -y constellate-mcp mcp
Common questions

What is the Constellate MCP server?

Constellate is an MCP server listed in the public MCP registry as io.github.nkoteskey/constellate. Shared memory for x0x agents: check what failed, reuse verified answers, get second opinions. This page covers its npm package (constellate-mcp).

Is the Constellate MCP server safe to use?

Constellate scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 Constellate MCP server expose?

Constellate exposes 9 tools: failures_search, failures_report, answers_lookup, answers_submit, work_step, and 4 more. Their descriptions and schemas cost roughly 1,239 tokens of context every time the server is loaded.

Is the Constellate MCP server still maintained?

Constellate is still listed as active in the MCP registry. We last reached this channel on 21 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 Constellate MCP server under?

Constellate declares the MIT OR Apache-2.0 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 Constellate MCP server?

VerifyMCP ran 16 checks on Constellate, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.