Eclipse Herald MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.1.1Updated Oct 29, 2026

Signed Agent Cards, policy-gated delegation, certification before hire.

VerifiedSTDIODesktop onlyAI & ML

Overview

AI-generated overview

Local stdio MCP server for signed agent cards, policy-gated delegation and certification checks before hiring an agent.

What you can do
  • The listing gives no tool list, so capabilities are inferred from the short description only.
  • Issue and verify signed agent cards that identify an agent.
  • Apply policy gates to delegation between agents.
  • Run a certification step before an agent is hired.
  • No README or server instructions are available, so the exact operations and their inputs are undocumented.
When to use it
Consider it when you are building or operating multi-agent setups and want an assistant to check agent identity, delegation rules or certification status before handing work to another agent.
Requirements
Runs as a local process over stdio, installed from the PyPI package eclipse-herald with uvx, so a Python environment with uv/uvx is needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Before you install
The server is undocumented beyond one sentence: no tool list, README or instructions, so what it reads, signs or stores cannot be verified. Signed cards and delegation policies imply trust decisions; confirm how keys are handled and whether any action is recorded or sent to a third party before relying on it.

Installation

In SourceWeft

  1. Open Eclipse Herald MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.1LatestOct 29, 2026
  2. v0.1.0Oct 26, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.