GraphyLoop
NPM · GRAPHYLOOP
Workflow planner, wave dispatcher, persistent swarm memory, and deploy preflight for AI agents.
Available components
Last scanned (5 hours ago)
Scores higher than 62% of npm servers
Category Workflow Automation
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chadixearth/graphyloop). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1596 tokens (~106/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "memory_forget" 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 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.6.4 → 0.6.5 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 29 Oct 26 65
First indexed and scored.
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/graphyloop@0.6.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chadixearth/graphyloop |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chadixearth/graphyloop/.github/workflows/publish.yml@refs/tags/v0.6.5 |
| Rekor log index | 3637337944 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:895d74540a61fb648fdb5b3e3dd9908773f24aa3c678c5a3f37a28414d48be2042bbc38bcb1d7ce6b94617591eeef0173fbe27e7f109b1d7c3dba590b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
agent_list ~22
List all swarm agents with type, status, role, and health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
agent_spawn ~129
Spawn a swarm agent. type (required): coder|tester|reviewer|architect|explorer|security|coordinator|frontend|data. Optional: id (default auto-generated), capabilities (comma-separated overrides), role (worker|peer|leader).
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | string | – | Comma-separated capability overrides |
| id | string | – | Custom agent id (default auto-generated) |
| role | string | – | worker | peer | leader (default: worker) |
| type | string | yes | Agent type: coder, tester, reviewer, architect, explorer, security, coordinator, frontend, data |
No output schema declared.
No examples provided.
env_sync ~147
Write the stored credentials into the env file the framework actually reads (default .env.local), add the framework public aliases for public keys only (NEXT_PUBLIC_*/VITE_*, never for a service-role key), refresh a values-free .env.example, and make sure .gitignore covers the env files. Values move file-to-file: the result lists key NAMES, never values.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Overwrite a key that already has a different value (a timestamped backup is kept) |
| providers | string | – | Comma-separated provider filter, e.g. "supabase" |
| target | string | – | Env file name inside the project (default .env.local) |
No output schema declared.
No examples provided.
memory_forget ~64
Delete one memory entry by id (ids come from memory_search results). Use this to correct a wrong or outdated memory instead of letting it be recalled forever.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory id to delete, e.g. mem-1700000000000-ab12 |
No output schema declared.
No examples provided.
memory_search ~93
Keyword-search stored memories, ranked by match quality with a recency bias. query (required), limit (optional, default 10), type (optional: decision|pattern|lesson|event|task).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Max results (default 10) |
| query | string | yes | Search query |
| type | string | – | Only search this memory type: decision | pattern | lesson | event | task |
No output schema declared.
No examples provided.
memory_store ~98
Store a memory entry. content (required). Optional: agent (default system), type (decision|pattern|lesson|event|task, default event), metadata (object or JSON string).
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Agent id (default: system) |
| content | string | yes | Memory text |
| metadata | object | – | Optional metadata object |
| type | string | – | decision | pattern | lesson | event | task (default: event) |
No output schema declared.
No examples provided.
plan_feature ~320
Plan a multi-layer feature as parallel waves before writing any code. goal (required): the request in plain words, e.g. "inventory system with stock levels, a dashboard and deploy to vercel". Returns wave 0 (the driver, or ONE agent when the code is unmapped, freezes the contract: schema + API + props + test scenarios, AND the context pack ctx-<slug>.md next to it: per lane path:line + current code excerpt + pattern to copy) -> wave 1 parallel builders (data, backend, frontend, tests; the driver keeps the most coupled lane) -> wave 2 integration -> wave 3 parallel verifiers (test, typecheck, security, performance, review) -> wave 4 gated deploy, with per-task file ownership, acceptance checks and dependsOn. Every lane brief ends with the turn-economy footer (batch reads, first edit by turn 5, no project-wide lint/test/build). A goal with no data/backend/frontend/pipeline signal answers shape no-fanout; work touching 8 known files or fewer (inlineThreshold 8) is done inline unless it splits into 2+ independent slices of about 5 minutes each. Pass the returned tasks array (JSON) straight to task_distribute.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | The feature request, verbatim |
| includeDeploy | boolean | – | Force the deploy wave on even if the goal does not mention shipping |
| maxParallel | string | – | Local builder concurrency cap (default 4, RAM-bound) |
No output schema declared.
No examples provided.
preflight ~100
Readiness check + ordered command plan for database setup and/or deploy. target: db | deploy | all (default all). Returns the detected stack, blockers (missing credentials, no build script, env file not git-ignored), warnings, and the exact commands to run — every destructive step (db push, --prod deploy) carries the approval gate it needs. Executes nothing itself.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | db | deploy | all (default all) |
No output schema declared.
No examples provided.
secrets_set ~145
Store one credential in the project-local secret store (<project>/.graphyloop/secrets.json, chmod 600, git-ignored before the first write). key (required) e.g. SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, VERCEL_TOKEN. value (required) is written to disk and echoed back masked only. Use this once per key, then env_sync.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | UPPER_SNAKE_CASE key name |
| provider | string | – | supabase | vercel (optional; inferred from the key) |
| value | string | yes | The credential value (stored, never echoed back) |
No output schema declared.
No examples provided.
secrets_status ~95
Masked readiness report for the project credentials (Supabase, Vercel): which keys are set, where each one comes from (process env, graphyloop store, .env file), and what is still missing. Values are NEVER returned — only a mask. Call this before database or deploy work instead of asking the user to paste keys.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | supabase | vercel | all (default all) |
No output schema declared.
No examples provided.
shutdown ~25
Shut down the swarm (terminates agents, keeps memory) and exit the MCP server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
skills_status ~180
Which skills are actually installed on this machine (project .opencode/skills, .dsh/skills, .agents/skills; ~/.config/opencode/skills, ~/.claude/skills, ~/.dsh/skills, ~/.omp/agent/skills, ~/.gemini/skills, ~/.agents/skills). Reports the graphyloop-bundled skills (70, of which 12 are graphyloop-authored: graphyloop-waves, graphyloop-workflow, api-contract-design, api-hardening, frontend-security, web-accessibility, web-performance, dependency-audit, supabase-setup, vercel-deploy, secrets-hygiene, swarm-memory) and which skills the squad routes on but are missing. Call it before claiming a skill was used — a missing skill is stated in one line, never faked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
swarm_state ~28
Swarm status: agents, active agents, tasks completed/failed, pending tasks, memory count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
task_distribute ~66
Distribute tasks across swarm agents. tasks (required): JSON string array of {id, type, description, priority}. Returns per-task assignments with opencodeAgentType and prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| tasks | string | yes | JSON array of {id, type, description, priority} task objects |
No output schema declared.
No examples provided.
task_record ~84
Record a task result and update agent metrics. taskId + status (required; status: completed|failed). Optional: agentId, error.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Agent id (default: task assigned agent) |
| error | string | – | Error message when failed |
| status | string | yes | completed | failed |
| taskId | string | yes | Task id |
No output schema declared.
No examples provided.
How do I install the GraphyLoop MCP server?
GraphyLoop runs locally as an npm package, launched with npx -y graphyloop. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · graphyloop
claude mcp add chadixearth-graphyloop -- npx -y graphyloop
What is the GraphyLoop MCP server?
GraphyLoop is an MCP server listed in the public MCP registry as io.github.chadixearth/graphyloop. Workflow planner, wave dispatcher, persistent swarm memory, and deploy preflight for AI agents. This page covers its npm package (graphyloop).
Is the GraphyLoop MCP server safe to use?
GraphyLoop scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 GraphyLoop MCP server expose?
GraphyLoop exposes 15 tools: agent_spawn, agent_list, task_distribute, swarm_state, task_record, and 10 more. Their descriptions and schemas cost roughly 1,596 tokens of context every time the server is loaded.
Is the GraphyLoop MCP server still maintained?
GraphyLoop 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 GraphyLoop MCP server under?
GraphyLoop declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.