palaver
NPM · PALAVER-AGENTS
Messaging between AI coding agents (Claude Code, Codex, ...) over your own self-hosted relay.
Available components
Last scanned (15 hours ago)
Scores higher than 92% of npm servers
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Renamed to hoptell: io.github.EminUZUN/hoptell.
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency94
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to EminUZUN/palaver). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 495 tokens (~123/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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; "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 5 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
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.
- 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.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Security disclosure: pass → unverified ▼ functional
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
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/palaver-agents@0.1.1
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 | EminUZUN/palaver |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/EminUZUN/palaver/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3111621146 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:007ae5bed49aa892496c81ca772ccea7d54a40d9b66d8cb69813fc73ff4037336f955c8ecc6ea4a8746888b8dacb810e5f44a4d8daf5bfd84916b3f56 |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
list_peers ~28
List palaver peers (agent sessions on this or other machines) and whether they are online.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_inbox ~23
Return and clear messages received from peers that were not pushed to you.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_message ~104
Send a plain-text message to a palaver peer by name (offline peers get it when they reconnect), or to @<role> / @all (every ONLINE peer with that role / every online peer; not queued for offline peers).
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Plain text, up to 100000 characters; files are not attached |
| to | string | yes | Peer name (from list_peers or a message's sender), @<role>, or @all |
No output schema declared.
No examples provided.
wait_for_message ~65
Block until a peer message arrives (or the timeout passes), then return it. Use this to listen when messages are not pushed to you (e.g. in Codex).
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_seconds | number | – | Max wait in seconds, default 300, max 1500 |
No output schema declared.
No examples provided.
How do I install the palaver MCP server?
palaver runs locally as an npm package, launched with npx -y palaver-agents 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 · palaver-agents
claude mcp add eminuzun-palaver -- npx -y palaver-agents mcp
What is the palaver MCP server?
palaver is an MCP server listed in the public MCP registry as io.github.EminUZUN/palaver. Messaging between AI coding agents (Claude Code, Codex, ...) over your own self-hosted relay. This page covers its npm package (palaver-agents).
Is the palaver MCP server safe to use?
palaver scores 88 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 palaver MCP server expose?
palaver exposes 4 tools: list_peers, send_message, wait_for_message, read_inbox. Their descriptions and schemas cost roughly 220 tokens of context every time the server is loaded.
Is the palaver MCP server still maintained?
palaver is marked deprecated 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 palaver MCP server under?
palaver declares the Apache-2.0 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 palaver MCP server?
VerifyMCP ran 16 checks on palaver, 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.