Eclipse Steward MCP
Governance MCP server that gates agent posting in team chat under a signed mandate
- Platforms
- Slack, teams, discord
- Version
- 0.1.0
- Listing updated
- today
Similar MCP servers
About Eclipse Steward MCP
Eclipse Steward MCP is an MCP server for security. It is available on Slack, teams, discord and API.
The README describes a signed, version-chained mandate as the sole source of authority for an agent working in team chat. The agent surface exposes no dispatch verb and holds no credential; instead, a gate re-checks the mandate, kill state, disclosure, quiet windows and caps at the moment of dispatch, and every read is receipted.
According to the registry entry, chat content never changes the rules: an in-chat amendment to the mandate is refused, even when it comes from the workspace owner. The stated goal is to govern the agent's behaviour rather than monitor the people in the channel.
The listing describes a local or simulator v0.1 with fixture adapters for Slack, Teams and Discord, and no live platform or real messages. It suits teams experimenting with how an agent should be constrained before it is given access to real conversations.
Tools this server provides (10)
Taken from the project documentation; the running server may differ.
- workspace_bind
- Binds a workspace to the governed agent.
- mandate_issue
- Issues a signed mandate.
- mandate_amend
- Amends an existing mandate.
- draft_approve
- Approves a proposed draft.
- gate_dispatch
- Checks an action at dispatch time.
- kill_issue
- Issues a kill signal.
- disclosure_check
- Checks disclosure requirements.
- receipt_verify
- Verifies a receipt.
- read
- Reads through the governed surface with a receipt.
- draft_propose
- Proposes a draft for approval.
What it does
- Signed mandate authority
- A version-chained, signed mandate defines everything the agent is allowed to do.
- Dispatch-time gate
- Each action is checked against mandate, kill switch, disclosure, quiet windows and caps before it runs.
- No credential on agent surface
- The agent-facing tools hold no dispatch verb and no platform credential.
- Receipted reads
- Every read operation leaves a receipt that can be verified afterwards.
- Draft approval flow
- Drafts are proposed and must be approved before they are sent.
Good for
- Limiting what a chat agent may post in a shared Slack or Teams channel
- Keeping an auditable record of every agent read in a team workspace
- Stopping an agent quickly with a kill switch when a channel needs to go quiet
Eclipse Steward MCP FAQ
Does Steward read or monitor people in the chat?
The registry entry says it governs the agent and never monitors the people.
Does it connect to live chat platforms?
No. The v0.1 build uses fixture adapters for Slack, Teams and Discord, with no live platform and no real messages.
Can a chat message change the agent's mandate?
No. The listing says an in-chat mandate amendment is refused, even from the workspace owner.
What are the best alternatives to Eclipse Steward MCP?
The closest alternatives to Eclipse Steward MCP are Eclipse Tether MCP, signet-eval, Sanction, Golem Context and agent-custody.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.