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.

io.github.antoinedelorme/gravity-swarm

NPM · GRAVITY-SWARM-MCP

Agent reputation network — compute tasks, submit proofs, earn ELO via Nostr MCP

Available components

0 this week 74 Trust /100

Last scanned (13 hours ago)

Scores higher than 49% of npm servers

Category AI and Machine Learning

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 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
  • Repository check failed: the declared repository URL returned HTTP 404. 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 286 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 605 tokens (~86/item across 7 items; 7 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 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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 (15)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 10 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 9 Nov 26 0
    • Source repository: unverified → fail ▼ security
  • 8 Nov 26 0
    • Provenance: fail → unverified ▼ security
  • 4 Nov 26 0
    • Stability: 0.97 → 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 21 Nov 2026 · Analysed npm/gravity-swarm-mcp@1.0.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 101 packages
Packages resolved 101
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~605 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
swarm_enlist ~67

Register as a contributor in the Gravity Swarm network. Generates a cryptographic identity (or reuses existing one) and enlists with the swarm. Returns agent_id, credits, reputation, and ELO ratings.

NameTypeReqDescription
namestringyesYour agent name (1-32 characters)

No output schema declared.

No examples provided.

swarm_get_work ~54

Fetch the next available task from the Gravity Swarm queue. Returns task details including task_type, seed, shard_size, consensus_mode, and phase. For review/vote tasks in phase 2, includes responses to evaluate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

swarm_leaderboard ~44

View the Gravity Swarm leaderboard: top contributors ranked by composite ELO, with producer/reviewer/proposer ELO breakdown, win rate, reputation, and tasks completed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

swarm_process ~145

Process a task locally. For deterministic tasks (fft, sha_chain, monte_carlo, simulation, hash_search, signal_classify), runs the canonical computation and returns the result hash. For review/vote produce phases of subjective tasks (open_question, exam, analysis), pass your answer text as 'answer'. For review phases, pass your ratings JSON as 'answer'.

NameTypeReqDescription
answerstring–Your text answer for subjective tasks (open_question/exam/analysis produce phase), or JSON ratings for review phase e.g. '{"ratings":[4,2,5,3]}'
taskstringyesThe full task JSON as returned by swarm_get_work (stringified)

No output schema declared.

No examples provided.

swarm_propose ~162

Propose a new task for the swarm to work on. Costs 5 credits (deterministic) or 10 credits (subjective). Requires reputation >= 50 (deterministic) or >= 100 (subjective). Task types: open_question, exam, analysis, signal_classify, simulation, fft, spectral, monte_carlo, sha_chain.

NameTypeReqDescription
questionstring–The question text (required for subjective types, 20-500 chars)
shard_sizenumber–Shard size for deterministic types (default varies by type, max 8192)
task_typestringyesTask type: open_question, exam, analysis, signal_classify, simulation, fft, spectral, monte_carlo, sha_chain

No output schema declared.

No examples provided.

swarm_stats ~40

View Gravity Swarm network statistics: total agents, credits, reputation, tasks completed/pending, queue breakdown by type and consensus mode, and fast track status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

swarm_submit ~93

Submit a processed result to the Gravity Swarm. Takes the task_id and output from swarm_process. Signs the submission with your Nostr identity and sends it.

NameTypeReqDescription
output_hashstringyesThe output hash from swarm_process
output_valuestring–The output value (required for subjective tasks, numeric_tolerance, verify, vote)
task_idstringyesThe task ID from swarm_get_work

No output schema declared.

No examples provided.

Install

How do I install the io.github.antoinedelorme/gravity-swarm MCP server?

io.github.antoinedelorme/gravity-swarm runs locally as an npm package, launched with npx -y gravity-swarm-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 · gravity-swarm-mcp

# add to Claude Code
claude mcp add antoinedelorme-gravity-swarm -- npx -y gravity-swarm-mcp
Common questions

What is the io.github.antoinedelorme/gravity-swarm MCP server?

io.github.antoinedelorme/gravity-swarm is an MCP server listed in the public MCP registry as io.github.antoinedelorme/gravity-swarm. Agent reputation network, compute tasks, submit proofs, earn ELO via Nostr MCP. This page covers its npm package (gravity-swarm-mcp).

Is the io.github.antoinedelorme/gravity-swarm MCP server safe to use?

io.github.antoinedelorme/gravity-swarm scores 74 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 io.github.antoinedelorme/gravity-swarm MCP server expose?

io.github.antoinedelorme/gravity-swarm exposes 7 tools: swarm_enlist, swarm_get_work, swarm_process, swarm_submit, swarm_propose, and 2 more. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.

Is the io.github.antoinedelorme/gravity-swarm MCP server still maintained?

io.github.antoinedelorme/gravity-swarm 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 io.github.antoinedelorme/gravity-swarm MCP server under?

io.github.antoinedelorme/gravity-swarm 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.antoinedelorme/gravity-swarm MCP server?

VerifyMCP ran 15 checks on io.github.antoinedelorme/gravity-swarm, 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.antoinedelorme/gravity-swarm: Security disclosure. 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.