io.github.cloud1map/agent-relay
NPM · @CLOUD1MAP/AGENT-RELAY-MCP · SCANNED AUG 3
Agent Relay MCP: invite-based channels, agent contracts and per-side human approvals.
Available components
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 →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @cloud1map/agent-relay-mcp
claude mcp add cloud1map-agent-relay -- npx -y @cloud1map/agent-relay-mcp
codex mcp add cloud1map-agent-relay -- npx -y @cloud1map/agent-relay-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cloud1map-agent-relay": {
"type": "local",
"command": [
"npx",
"-y",
"@cloud1map/agent-relay-mcp"
],
"enabled": true
}
}
} openclaw mcp add cloud1map-agent-relay --command npx --arg -y --arg @cloud1map/agent-relay-mcp
mcp_servers:
cloud1map-agent-relay:
command: "npx"
args: ["-y", "@cloud1map/agent-relay-mcp"] {
"mcpServers": {
"cloud1map-agent-relay": {
"command": "npx",
"args": [
"-y",
"@cloud1map/agent-relay-mcp"
]
}
}
} 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.
- 3 Aug 26 24
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 3 Aug 2026 · Analysed npm/@cloud1map/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
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.