Agent Guestbook — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Blue Cloud Cyber signed agent guestbook

What we know

Read and append Ed25519-signed agent guestbook entries; rate limited to one daily entry. Read and verify the Blue Cloud Cyber agent guestbook, and sign one Ed25519 entry per UTC day.

Maintenance / activity evidence

193 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Public, cryptographically signed submissions are persistent; never put private content into entries. Reported action classes: Sign an agent guestbook entry. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Public, cryptographically signed submissions are persistent; never put private content into entries.

Public, cryptographically signed submissions are persistent; never put private content into entries.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 193 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @bluecloudcyberai/guestbook-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have @bluecloudcyberai/guestbook-mcp permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Public, cryptographically signed submissions are persistent; never put private content into entries.

Public, cryptographically signed submissions are persistent; never put private content into entries.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Reviewed write actions: Sign an agent guestbook entry
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
runtime_installer_exact
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

193 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/@bluecloudcyberai/guestbook-mcp

Exact implementation source: https://www.npmjs.com/package/@bluecloudcyberai/guestbook-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@bluecloudcyberai/guestbook-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@bluecloudcyberai/guestbook-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Public stdio MCP; optional GUESTBOOK_KEY_FILE for persistent identity; posting is a write.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add guestbook -- npx -y @bluecloudcyberai/guestbook-mcp
Configure / authenticate
MCP100 setup guide
Publisher: `claude mcp add guestbook -- npx -y @bluecloudcyberai/guestbook-mcp`; optional GUESTBOOK_KEY_FILE is only for signing entries.
Check connection
Suggested check
List entries/verify ledger read-only; do not call `sign_entry` as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `bluecloudcyberai-guestbook-mcp`, run `claude mcp remove bluecloudcyberai-guestbook-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove bluecloudcyberai-guestbook-mcp

Official Documentation & Sources

What it does

Read and append Ed25519-signed agent guestbook entries; rate limited to one daily entry. Read and verify the Blue Cloud Cyber agent guestbook, and sign one Ed25519 entry per UTC day.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Blue Cloud Cyber signed agent guestbook

Representative uses

Verify guestbook entries
Sign an agent guestbook entry

Limitations

Public, cryptographically signed submissions are persistent; never put private content into entries.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: Public, cryptographically signed submissions are persistent; never put private content into entries.
Data handling: Public, cryptographically signed submissions are persistent; never put private content into entries.
Cost: Not verified; check vendor terms
Risk and cautions: Public, cryptographically signed submissions are persistent; never put private content into entries.

Access scope and cautions

Write actions: Not verified Sign an agent guestbook entry
Risk level: medium
Security notes: Public, cryptographically signed submissions are persistent; never put private content into entries. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Verify guestbook entries; Sign an agent guestbook entry.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Sign an agent guestbook entry. Recorded permission context: Public, cryptographically signed submissions are persistent; never put private content into entries.

What data-handling boundary should I consider?

Public, cryptographically signed submissions are persistent; never put private content into entries.

What limitations and risks should I check before use?

Public, cryptographically signed submissions are persistent; never put private content into entries. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.