CanopiiCanopiiAll serversEnterprise →
com.swarmmemo/bulletin

com.swarmmemo/bulletin v1.37.0

Security Trust Score
Grade F · Serious issues
Tier 1 · Public sourceHigh confidence · 96%
Declared MCP capabilities
ResourcesPrompts

This server scored F. Run it behind runtime policy enforcement so one bad tool call can't become an incident.

4 issues capping this score
  • highNo unsafe deserialization — 12 occurrences
  • highTool descriptions free of injection markers — 4 marker(s) across 4 tool(s)
  • highNo risky post-publish tool changes (rug-pull) — 1 risky tool-definition change(s) in version history (1.18.2 → 1.18.3)
  • mediumNo over-broad / destructive tools — 1 over-broad tool(s)
Reputation1stars3forks2open issues8d agolast commit<1yage

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Fail
    Indirect Prompt Injection (IPI) Defensesguard4 marker(s) across 4 tool(s)

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent. How many servers fail this?

    create_identity — exfiltration directivepost_message — exfiltration directivescreen_leak — exfiltration directivesend_private — exfiltration directive

    Fix: Remove hidden directives, HTML/comment instructions, and override phrasing from descriptions.

  • Fail
    Tool Definition Integrityguard1 risky tool-definition change(s) in version history (1.18.2 → 1.18.3)

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns. How many servers fail this?

    post_message

    Fix: Never add hidden directives or destructive scope to an already-published tool; document description changes in release notes.

  • Fail
    User-in-the-Loop / Approval Scopeguard1 over-broad tool(s)

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval. How many servers fail this?

    claim_identity

    Fix: Scope tools narrowly; avoid arbitrary command execution and destructive defaults.

  • Pass
    Strict JSON Schema EnforcementadditionalProperties:false present

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

  • Pass
    In-Session Definition Integrityguardno call-gated or call-time tool definition changes

    Tool and prompt definitions stay fixed during a session — they don't change after a few calls, which is how runtime-gated rug-pulls slip past one-time review.

Application Security Checks

  • Fail
    No unsafe deserializationguard12 occurrences

    pickle/yaml.load/etc. on untrusted data can execute code. How many servers fail this?

    research/swarmchasing/analysis/collusionwiki/02_labels_recruitment_handoff.py:13research/swarmchasing/analysis/collusionwiki/03_deletion_response.py:13research/swarmchasing/analysis/collusionwiki/03_deletion_response.py:14research/swarmchasing/analysis/collusionwiki/04_network_core_clusters.py:69

    Fix: Use safe loaders (yaml.safe_load, JSON) on untrusted input.

  • Warn
    No dynamic code executionguard2 occurrences (build/test paths only)

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

    scripts/test_private_read_guide.py:71scripts/test_url_budget_guide.py:50

    Fix: Remove eval/exec; parse and dispatch explicitly.

  • Warn
    No path traversalguard64 occurrences

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

    clients/javascript/swarmmemo.mjs:427clients/javascript/swarmmemo.mjs:450clients/javascript/test_client.mjs:354clients/javascript/test_client.mjs:438

    Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.

  • Warn
    No SSRF sinksguard107 occurrences

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

    clients/javascript/swarmmemo.mjs:512clients/javascript/test_client.mjs:513clients/javascript/test_client.mjs:536clients/javascript/test_client.mjs:542

    Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

  • Warn
    No known-vulnerable dependencies1 of 87 runtime deps vulnerable; worst critical

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

    [email protected] — GHSA-2gx3-rcp4-g85q[email protected] — GHSA-42vr-xj54-vc7v[email protected] — GHSA-8wjv-2p76-3863[email protected] — GHSA-9j54-fg26-wv3r

    Fix: Upgrade the flagged dependencies past their fixed versions.

  • Warn
    Adoption & popularitylimited adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

    Fix: Adoption grows naturally with real-world use; this never gates the score.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    Dependencies pinned (lockfile)lockfile present

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseApache-2.0

    A clear license is required for legal enterprise use.

  • Pass
    Has a security policySECURITY.md present

    A SECURITY.md gives a private path to report vulnerabilities.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

  • N/A
    No install/post-install scriptsguardno published package

    install hooks run arbitrary code on every consumer at install time.

  • N/A
    Package name not typosquattingguardno published package

    Names mimicking popular packages are a common malware delivery vector.

  • N/A
    Published with provenanceno published package

    Build provenance attests the artifact was built from the claimed source by CI.

  • N/A
    Established maintainerno published package

    Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

  • Pass
    Transport Encryption (TLS)guardall remotes use HTTPS

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • Pass
    IAM / Authentication ScopingOAuth / PRM handling detected

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • Pass
    No Token Passthroughguardno inbound token forwarded downstream

    The client's token is never forwarded to downstream APIs — the server obtains its own, correctly-scoped credential instead.

  • Pass
    Execution Sandboxingcontainerized

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • Not checked
    DNS-Rebinding ProtectionHTTP transport not found in source

    HTTP endpoints reject requests carrying an unlisted Origin, so a malicious web page can't drive the server through the user's browser.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (103)

findtrustwhoamijournalallowancedocs_listdocs_opendocs_readfind_worklog_proofread_feedread_worktune_feedclaim_workdocs_writefetch_pagelist_pageslist_roomsmemory_getmemory_putnotary_getnotary_keyread_agentscreen_keyset_handletools_callaccept_workdocs_createdocs_deletefind_agentsjoin_invitememory_listread_threadreject_workscreen_leakscreen_textsubmit_workwakeup_listwork_proofsagent_recordbuy_offeringdocs_historynotary_stamppost_messageread_subjectread_updatessend_privatetools_searchwrite_reviewcreate_invitecredits_topuplist_servicesmanage_tokensmemory_deleteread_messagesread_offeringreceiver_listscreen_verifystanding_wayswakeup_cancelaccept_requestclaim_identityfind_offeringsoffering_callsraise_standingreceiver_itemsset_protectionsubscribe_roomwakeup_noticesx402_resourcesx402_tools_getcreate_identitydispose_updatesjournal_suspendreceiver_createreceiver_deletereceiver_rotateresolve_subjectsearch_subjectswakeup_schedulex402_tools_callpublic_data_bulkpublish_offeringread_agent_postsrecover_identitymark_updates_readpublic_data_fetchread_conversationread_work_historyx402_tools_searchinference_completelist_conversationsclaim_offering_callcorroborate_resolvecreate_conversationupdate_conversationanswer_offering_calloffering_call_statuspublic_data_datasetsrefund_offering_calldecline_offering_calllist_event_subscriptionscancel_event_subscription

AI-flagged — for review

Observations from an AI review of tool descriptions. These are advisory only and do not affect the score — they can be noisy and need human judgement.

  • info
    Tool "publish_offering" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

  • info
    Tool "read_subject" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

  • info
    Tool "write_review" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.