eclipse-herald
mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/herald
What this is: eclipse-herald is the MCP server edition of
Eclipse Herald — Cyan Eclipse Technologies' agent-to-agent
discovery and delegation layer: signed Agent Cards (A2A v1.0-shaped,
JWS/RS256), policy-gated delegation, and certification-before-hire.
What this is not: it does not talk to live third-party agents and moves no real money. v0.1 is a local implementation: delegation runs against local stub agents and settlement is recorded in zero-value TEST-CREDITS.
Use
$ pip install eclipse-herald
$ eclipse-herald # MCP server over stdio
Or run it as a container: ghcr.io/cyan-eclipse-technologies-llc/eclipse-herald-mcp:0.1.0.
Tools (5)
| Tool | What it does |
|---|---|
card_build |
Build an unsigned Agent Card for a face from its template. |
card_sign |
Build + sign a card; write it to cards/; export the public JWKS. The private key never leaves keys/ (chmod 600). |
card_verify |
Schema-validate a card and verify its JWS signature. |
gateway_delegate |
Governed delegation to a LOCAL test agent: verify card → certify-check → mandate (task hash, budget cap, expiry) → dispatch → receipt-on-delivery. |
receipt_list |
Read the append-only, hash-chained receipts ledger + verify the chain. |
Honest scope
- Local only. No network calls, no live counterparties, no real money in v0.1. Live task endpoints are later-phase scope.
- Key custody. The signing private key is a single local file,
keys/signing-key.json, chmod 600, generated on first use. It is never printed, logged, or embedded in any document; only the public JWKS is exported. - Foreign-agent output informs; it never instructs — deliverables pass through a quarantine ingest that strips instruction-shaped lines before anything downstream sees them.
- A signed card is evidence about who an agent claims to be, not an endorsement and not a Bazaar listing claim.
Powered by Cyan Eclipse Technologies LLC (cetech.ai) — a Veteran-Owned Small Business. MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for eclipse-herald 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eclipse_herald-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / eclipse_herald-0.1.0-py3-none-any.whl
| Download URL | eclipse_herald-0.1.0-py3-none-any.whl |
|---|---|
| Size | 21.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3ca76410407cb4d61b9e309dc9f6007ca870f69f7ac5fdb0e753c0ca184f0c9
|
|
BLAKE2b-256 checksum How to use checksums |
5d649b748298aec7790687f68328953538668c795d11f50e64b4185df825c36e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for eclipse-herald 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for eclipse_herald-0.1.0-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
