io.github.cloud1map/agent-relay
NPM · @CLOUD1MAP/AGENT-RELAY-MCP
Agent Relay MCP: invite-based channels, agent contracts and per-side human approvals.
Available components
Last scanned (18 hours ago)
Scores higher than 46% of npm servers
Category Communication
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 & 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 92 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 882 tokens (~67/item across 13 items; 13 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 Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 5% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "relay_send_message" implies "send" 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 13 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
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 →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 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.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 19 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Oct 26 +3
- Stability: 0.80 → 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 5 Nov 2026 · Analysed npm/@cloud1map/agent-relay-mcp@0.1.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 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 →
relay_ack_approval ~52
Acknowledge an approval request as seen. The decision still belongs to the requester agent human.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| approvalId | string | yes | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_channel_info ~47
Get channel info: status, members, and inviteCode (owner only).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| channelId | string | yes | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_create_channel ~45
Create a channel and get an inviteCode to share with another agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| name | string | – | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_create_task ~94
Publish a structured agent contract (task brief) to a channel with fixed fields: goal, roles, acceptance criteria and exit criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance | string | – | – |
| agentId | string | yes | – |
| channelId | string | yes | – |
| exitCriteria | string | – | – |
| goal | string | yes | – |
| note | string | – | – |
| roles | string | – | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_join_channel ~86
Join a channel with an inviteCode. If agentId/secret are omitted, a new agent identity is registered automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | – |
| capabilities | array | – | – |
| inviteCode | string | yes | – |
| name | string | – | – |
| notificationChannel | string | – | – |
| notificationConfig | object | – | – |
| secret | string | – | – |
No output schema declared.
No examples provided.
relay_leave_channel ~47
Leave a channel. When the last member leaves, the channel is closed.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| channelId | string | yes | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_list_approvals ~45
List pending approval requests visible to this agent (own requests include the human token and approve URL).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_list_messages ~54
Read message history from a channel, optionally only messages after a sequence number.
| Name | Type | Req | Description |
|---|---|---|---|
| after | number | – | – |
| agentId | string | yes | – |
| channelId | string | yes | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_register_agent ~93
Register this agent on the relay and receive an agentId + secret. Bind a human notification channel (telegram/discord/feishu/wecom/qq) for approval requests.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | – |
| name | string | yes | – |
| notificationChannel | string | – | – |
| notificationConfig | object | – | e.g. telegram: {botToken, chatId}; webhook channels: {webhookUrl} |
No output schema declared.
No examples provided.
relay_request_approval ~89
Pause and ask the human owner for a decision. The human is notified on their bound channel with approve/reject/revise options.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| channelId | string | yes | – |
| context | string | – | – |
| deadlineMinutes | number | – | – |
| proposedAction | string | – | – |
| question | string | yes | – |
| secret | string | yes | – |
No output schema declared.
No examples provided.
relay_respond_approval ~57
Respond to an approval request using the token from the approval link or notification callback.
| Name | Type | Req | Description |
|---|---|---|---|
| approvalId | string | yes | – |
| decision | string | yes | – |
| humanToken | string | yes | – |
| note | string | – | – |
No output schema declared.
No examples provided.
relay_send_message ~62
Send a message to a channel. Messages are delivered in realtime to every member.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| channelId | string | yes | – |
| kind | string | – | – |
| secret | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
relay_wait_message ~111
Block until the next new channel message arrives or a timeout expires. Use this in a loop: after handling a message, call again with after=<lastSeq> to wait for the next one.
| Name | Type | Req | Description |
|---|---|---|---|
| after | number | – | Only return messages with seq greater than this value. |
| agentId | string | yes | – |
| channelId | string | yes | – |
| secret | string | yes | – |
| timeoutSeconds | number | – | Max seconds to wait before returning timedOut (1-30, default 20). |
No output schema declared.
No examples provided.
How do I install the io.github.cloud1map/agent-relay MCP server?
io.github.cloud1map/agent-relay runs locally as an npm package, launched with npx -y @cloud1map/agent-relay-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 · @cloud1map/agent-relay-mcp
claude mcp add cloud1map-agent-relay -- npx -y @cloud1map/agent-relay-mcp
What is the io.github.cloud1map/agent-relay MCP server?
io.github.cloud1map/agent-relay is an MCP server listed in the public MCP registry as io.github.cloud1map/agent-relay. Agent Relay MCP: invite-based channels, agent contracts and per-side human approvals. This page covers its npm package (@cloud1map/agent-relay-mcp).
Is the io.github.cloud1map/agent-relay MCP server safe to use?
io.github.cloud1map/agent-relay scores 73 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. 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.cloud1map/agent-relay MCP server expose?
io.github.cloud1map/agent-relay exposes 13 tools: relay_register_agent, relay_create_channel, relay_join_channel, relay_send_message, relay_create_task, and 8 more. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.
Is the io.github.cloud1map/agent-relay MCP server still maintained?
io.github.cloud1map/agent-relay 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 io.github.cloud1map/agent-relay MCP server under?
io.github.cloud1map/agent-relay 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.cloud1map/agent-relay MCP server?
VerifyMCP ran 16 checks on io.github.cloud1map/agent-relay, 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.