ForgingStack Mandate Check
Before your agent acts, check its mandate. One call, one receipt.
Open the source (opens github.com) https://github.com/jdkabattles/forgingstack-mandate-check
Before you use it
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: FORGINGSTACK_API_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.jdkabattles.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
pypi package (stdio)
forgingstack-mandate-check@0.2.1
From the server's entry in the official MCP Registry
Settings it asks for
FORGINGSTACK_API_BASE· Mandate Check API base URL. Live default.FORGINGSTACK_API_KEYsecret required · API key for Mandate Check. Sign up via POST /v1/signup (key shown once).
Related
-
ForgingStack Watchtower
MCP serversAn agent that stops checking in is an agent you hear about.
forgingstack-watchtower@0.1.0 -
ForgingStack Ration
MCP serversOne quota pool, many agents, no overruns.
forgingstack-ration@0.1.0 -
ForgingStack Quorum
MCP serversBefore an agent acts alone, get the quorum. One proposal, N approvals, one receipt.
forgingstack-quorum@0.1.0 -
HANRIA agent mandate check
MCP serversCheck an agent action against its operator's mandate before acting: permit, deny or escalate.
-
Mandate
MCP serversTrade on Base through the Mandate module: every batch is checked onchain against the owner's rules
@mandatefi/mcp@0.1.1 -
ID MANDAT — Registry for AI Agents
MCP serversOpen registry for AI agents: check who stands behind an agent and what it may do.