io.github.mikusnuz/agent-link
NPM · AGENT-LINK-MCP
Bidirectional AI agent collaboration — spawn and communicate with any agent CLI
Available components
Last scanned (20 hours ago)
Scores higher than 69% of npm servers
Category AI and Machine Learning
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
- 30 of 92 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 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 487 tokens (~60/item across 8 items; 6 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +16
- Malware scan: unverified → pass ▲ security
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 4 Nov 2026 · Analysed npm/agent-link-mcp@0.5.3
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
get_status ~17
Get the status of all active agent sessions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kill_agent ~35
Terminate an active agent session and clean up its resources.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Session ID of the agent to kill |
No output schema declared.
No examples provided.
list_agents ~19
List all known agents and their availability on this system.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reply ~63
Reply to an agent that is waiting for clarification. Continues the conversation until the agent returns a result or asks another question.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Session ID returned from spawn_agent |
| message | string | yes | Clarification or additional information to send to the agent |
No output schema declared.
No examples provided.
spawn_agent ~242
Spawn an AI agent to work on a task. Returns a question if the agent needs clarification, or a result when done.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | Agent name (e.g. "claude", "codex", "gemini", "aider") |
| context | object | – | Optional task context |
| cwd | string | – | Working directory for the agent process |
| escalate | boolean | – | On retry, escalate thinking level automatically (default: false). Requires retry: true. |
| model | string | – | Model to use (e.g. "o3", "gpt-5.4", "claude-sonnet-4", "gemini-2.5-pro"). Passed via --model flag to the agent CLI. |
| retry | boolean | – | Auto-retry on failure (default: false). |
| task | string | yes | Task description to send to the agent |
| thinking | string | – | Thinking/reasoning depth level (e.g. "low", "medium", "high", "max"). Controls how deeply the agent reasons. |
| timeoutMs | integer | – | Timeout in milliseconds (default: 3600000) |
No output schema declared.
No examples provided.
spawn_agents ~89
Spawn multiple AI agents in parallel. Each agent runs independently and results are returned together. Great for getting multiple opinions, parallel code reviews, or distributing subtasks.
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | Array of agent tasks to run in parallel |
| cwd | string | – | Working directory (shared for all agents) |
| timeoutMs | integer | – | Timeout per agent in ms (default: 3600000) |
No output schema declared.
No examples provided.
How do I install the io.github.mikusnuz/agent-link MCP server?
io.github.mikusnuz/agent-link runs locally as an npm package, launched with npx -y agent-link-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 · agent-link-mcp
claude mcp add mikusnuz-agent-link -- npx -y agent-link-mcp
What is the io.github.mikusnuz/agent-link MCP server?
io.github.mikusnuz/agent-link is an MCP server listed in the public MCP registry as io.github.mikusnuz/agent-link. Bidirectional AI agent collaboration, spawn and communicate with any agent CLI. This page covers its npm package (agent-link-mcp).
Is the io.github.mikusnuz/agent-link MCP server safe to use?
io.github.mikusnuz/agent-link scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.mikusnuz/agent-link MCP server expose?
io.github.mikusnuz/agent-link exposes 6 tools: spawn_agent, spawn_agents, reply, kill_agent, list_agents, get_status. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Is the io.github.mikusnuz/agent-link MCP server still maintained?
io.github.mikusnuz/agent-link is still listed as active in the MCP registry. We last reached this channel on 4 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.mikusnuz/agent-link MCP server under?
io.github.mikusnuz/agent-link declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.