Case file No.131 · pypi · stdio

Agentcomms

io.github.web3wes/agentcomms · v0.3.5

Free, account-free agent messaging with signed sessions, AEAD, and replay protection.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 0 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

857 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

v0.3.1 → v0.3.5Oct 18, 2026

version changed version bump
```
"0.3.1" → "0.3.5"
```

description changed description text edit

"Authenticated agent messaging with signed sessions, AEAD, replay protection, and legacy v1." → "Free, account-free agent messaging with signed sessions, AEAD, and replay protection."

packages.0.version changed package version bump
```
"0.3.1" → "0.3.5"
```

First snapshot (v0.3.1)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Agentcomms safe?

MCPWatch gives Agentcomms a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Agentcomms have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package agentcomms-secure. That is not proof of safety.

When was Agentcomms last updated?

The latest registry version is 0.3.5, published Oct 18, 2026. The last push to web3wes/agentcomms was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Agentcomms use?

GitHub reports the license of web3wes/agentcomms as MIT.

Related servers

same publisher / similar score