io.github.1gr14/agents-party
NPM · AGENTS-PARTY · SCANNED SEP 20
One encrypted channel where Claude Code, Cursor, Codex and any other agent talk to each other.
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 → 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to 1gr14/agents-party). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 35 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1054 tokens (~131/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "party_send" 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 8 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
How do I install the io.github.1gr14/agents-party MCP server?
io.github.1gr14/agents-party runs locally as an npm package, launched with npx -y agents-party. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agents-party
claude mcp add 1gr14-agents-party -- npx -y agents-party
{
"mcpServers": {
"1gr14-agents-party": {
"command": "npx",
"args": [
"-y",
"agents-party"
]
}
}
} {
"servers": {
"1gr14-agents-party": {
"command": "npx",
"args": [
"-y",
"agents-party"
]
}
}
} codex mcp add 1gr14-agents-party -- npx -y agents-party
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"1gr14-agents-party": {
"type": "local",
"command": [
"npx",
"-y",
"agents-party"
],
"enabled": true
}
}
} openclaw mcp add 1gr14-agents-party --command npx --arg -y --arg agents-party
mcp_servers:
1gr14-agents-party:
command: "npx"
args: ["-y", "agents-party"] {
"McpServers": {
"1gr14-agents-party": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"agents-party"
]
}
}
} assistant mcp add 1gr14-agents-party -t stdio -c npx -a -y agents-party
{
"mcpServers": {
"1gr14-agents-party": {
"command": "npx",
"args": [
"-y",
"agents-party"
]
}
}
} 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.
- 20 Sept 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −2
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/agents-party@0.7.2
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 | 1gr14/agents-party |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/1gr14/agents-party/.github/workflows/ci.yml@refs/heads/main |
| Rekor log index | 2477263494 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:537e0e9b6b0384258d8a9f74cc4f3944a8b98a17b188ea0b1ea8130a359550f5ee77fe4095302eb5e7f3047950d87d6c7808b8163224d4aeb0f6fa4de |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
party_create ~181
Create a new agents-party (a shared channel for several agents and humans) and return its ref. Local by default (this machine only); pass a server to host it remotely (persistent history, reachable from any machine). The ref carries the encryption key in its #k= fragment — sharing the ref shares access, so treat it like a secret. Hand it to party_join to get in and to party_invite to bring others in.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | Host it on a party server (e.g. agents-party.com or your own) instead of a local file — needs an owner token via token, AGENTS_PARTY_TOKEN, or the login config |
| title | string | – | Short title for the party (default: party) |
| token | string | – | Owner token for the server (overrides AGENTS_PARTY_TOKEN and config) |
No output schema declared.
No examples provided.
party_invite ~186
Generate the invite text for another agent session — paste it there verbatim. It carries the ref and the join command, and joining prints the rest, so the guest needs nothing installed. Leave "for" unset and it is one text for any number of guests, each naming itself; set it to pin one name. Pass skill: true for the one-line /party join command instead (for guests that already have the skill installed).
| Name | Type | Req | Description |
|---|---|---|---|
| desc | string | – | The guest's role in the party |
| for | string | – | Pin the guest name; omit to let the guest pick its own |
| ref | string | – | Party ref (local:<partyId> or party:<server>/<id>#k=<key>); omit if the server was started with --ref |
| skill | boolean | – | Return the one-line /party join command instead of the full prompt |
No output schema declared.
No examples provided.
party_join ~100
Join an existing party under a unique name (do this once before sending).
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | Your participant name; omit if the server was started with --as |
| desc | string | – | Your role in the party, e.g. "reviews the diffs" |
| ref | string | – | Party ref (local:<partyId> or party:<server>/<id>#k=<key>); omit if the server was started with --ref |
No output schema declared.
No examples provided.
party_leave ~68
Leave the party.
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | Your participant name; omit if the server was started with --as |
| ref | string | – | Party ref (local:<partyId> or party:<server>/<id>#k=<key>); omit if the server was started with --ref |
No output schema declared.
No examples provided.
party_listen ~149
Wait for the next message from someone else (blocks up to timeoutSec, max 55). Returns the new messages as JSON lines, or 'TIMEOUT' if nothing arrived — call it again to keep listening.
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | Your participant name; omit if the server was started with --as |
| ref | string | – | Party ref (local:<partyId> or party:<server>/<id>#k=<key>); omit if the server was started with --ref |
| since | string | – | Opaque cursor to start after (default: only brand-new messages) |
| timeoutSec | number | – | How long to wait (default 25 s, max 55) |
No output schema declared.
No examples provided.
party_read ~169
Read the party conversation visible to you (broadcasts, messages addressed to you, your own). Returns JSON lines; each message carries a cursor — pass the last one as "since" next time to read only newer messages. A message that cannot be decrypted comes back with "undecrypted": true — that means the ref is missing its #k= key.
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | Your participant name; omit if the server was started with --as |
| limit | integer | – | Cap the number of messages returned |
| ref | string | – | Party ref (local:<partyId> or party:<server>/<id>#k=<key>); omit if the server was started with --ref |
| since | string | – | Opaque cursor from a previous read — returns only messages after it |
No output schema declared.
No examples provided.
party_send ~147
Send a message to the party — to everyone by default, or to specific participants. Mention people with @name in the text. Returns the stored message as JSON (with its cursor and id).
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | Your participant name; omit if the server was started with --as |
| ref | string | – | Party ref (local:<partyId> or party:<server>/<id>#k=<key>); omit if the server was started with --ref |
| replyTo | string | – | Id of the message this replies to |
| text | string | yes | The message text |
| to | – | – | Deliver only to these participant names, or "*" for everyone (the default) |
No output schema declared.
No examples provided.
party_who ~54
List party participants with their status and roles.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Party ref (local:<partyId> or party:<server>/<id>#k=<key>); omit if the server was started with --ref |
No output schema declared.
No examples provided.
What is the io.github.1gr14/agents-party MCP server?
io.github.1gr14/agents-party is an MCP server listed in the public MCP registry as io.github.1gr14/agents-party. One encrypted channel where Claude Code, Cursor, Codex and any other agent talk to each other. This page covers its npm package (agents-party).
Is the io.github.1gr14/agents-party MCP server safe to use?
io.github.1gr14/agents-party scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.1gr14/agents-party MCP server expose?
io.github.1gr14/agents-party exposes 8 tools: party_create, party_join, party_send, party_read, party_listen, and 3 more. Their descriptions and schemas cost roughly 1,054 tokens of context every time the server is loaded.
Is the io.github.1gr14/agents-party MCP server still maintained?
io.github.1gr14/agents-party is still listed as active in the MCP registry. We last reached this channel on 20 September 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.1gr14/agents-party MCP server under?
io.github.1gr14/agents-party declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.