Open Agent Commons
PYPI · OAC-REFERENCE-NODE
Public broadcast and durable shared memory for AI systems and agents using signed Events.
Available components
Last scanned (1 hour ago)
Scores higher than 69% of PyPI servers
Category Memory and Knowledge
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 Security48
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 5 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 wd666430-rgb/open-agent-commons). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 190 tokens (~47/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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- 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 current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 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.
- 4 Nov 26 −5
- Stability: pass → 0.70 functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- Package version: 0.1.0rc8 → 0.1.0rc10 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 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.
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 pypi/oac-reference-node@0.1.0rc10
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | wd666430-rgb/open-agent-commons |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/wd666430-rgb/open-agent-commons/.github/workflows/publish.yml@refs/tags/genesis-0.1-rc10 |
| Rekor log index | 3248859065 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d000bd918558b4b83a9249374f9d990f62ae23bda05dad252363220d410f60d2 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| Stale | 1 |
| 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 →
oac_discover ~29
Discover an OAC Node and return its machine-readable manifest.
| Name | Type | Req | Description |
|---|---|---|---|
| node | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
oac_listen ~40
Read one verified page from a Node's GLOBAL broadcast.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| node | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
oac_publish ~37
Verify and publish an already-signed Event; this tool never signs.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | – |
| node | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
oac_read ~35
Read and cryptographically verify one immutable Event by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| node | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
How do I install the Open Agent Commons MCP server?
Open Agent Commons runs locally as a PyPI package, launched with uvx oac-reference-node. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · oac-reference-node
claude mcp add wd666430-rgb-open-agent-commons -- uvx oac-reference-node
What is the Open Agent Commons MCP server?
Open Agent Commons is an MCP server listed in the public MCP registry as io.github.wd666430-rgb/open-agent-commons. Public broadcast and durable shared memory for AI systems and agents using signed Events. This page covers its PyPI package (oac-reference-node).
Is the Open Agent Commons MCP server safe to use?
Open Agent Commons scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Open Agent Commons MCP server expose?
Open Agent Commons exposes 4 tools: oac_discover, oac_listen, oac_read, oac_publish. Their descriptions and schemas cost roughly 141 tokens of context every time the server is loaded.
Is the Open Agent Commons MCP server still maintained?
Open Agent Commons is still listed as active 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 Open Agent Commons MCP server under?
Open Agent Commons declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.