Verifies agent mandates by checking identity, principal alignment, expiry, and allowed actions before an agent performs a task.
Also known as jdkabattles/forgingstack-mandate-check, forgingstack-mandate-check
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.1
- Last commit
- Nov 4, 2026
- License
- MIT
What is ForgingStack Mandate Check MCP?
ForgingStack Mandate Check verifies agent mandates by checking identity, principal alignment, expiry, and allowed actions before an agent performs a task.
Summary generated from the project's README
About ForgingStack Mandate Check MCP server
ForgingStack Mandate Check provides a verification layer for AI agents to ensure they possess the necessary authorization before executing tasks. This public client connects to a private service that evaluates four specific criteria: agent identity matching, principal alignment, expiration dates, and allowed actions. It functions as a remote service accessed via a local MCP server using the stdio transport method.
Developers must set the FORGINGSTACK_API_KEY environment variable to use the server. The system operates on a credit-based model where each check costs one credit, though idempotent replays using an Idempotency-Key are free. Users interact with the service through specific tools including check_mandate, get_credits, and get_receipt. The service focuses strictly on mandate fit rather than judging the safety or legality of an action.
What you can do with it
- 1Monitor remaining creditsCheck the current balance of available credits for the agent or primary account.
- 2Retrieve verification proofsObtain a hash-chained receipt to document the result of a mandate check.
- 3Manage agent sub-keysCreate or revoke specific keys for individual agents to control their credit usage.
Written from the project's README. Every use case is checked against a quote from it.
How to install ForgingStack Mandate Check MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ForgingStack Mandate Check MCP in Claude Code
$ claude mcp add --env 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' forgingstack-mandate-check -- uvx forgingstack-mandate-checkInstall ForgingStack Mandate Check MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"forgingstack-mandate-check": {
"command": "uvx",
"args": [
"forgingstack-mandate-check"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Install ForgingStack Mandate Check MCP in VS Code
.vscode/mcp.json
{
"servers": {
"forgingstack-mandate-check": {
"type": "stdio",
"command": "uvx",
"args": [
"forgingstack-mandate-check"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Install ForgingStack Mandate Check MCP in VS Code CLI
$ code --add-mcp '{"name":"forgingstack-mandate-check","type":"stdio","command":"uvx","args":["forgingstack-mandate-check"],"env":{"FORGINGSTACK_API_KEY":"<YOUR_FORGINGSTACK_API_KEY>"}}'Install ForgingStack Mandate Check MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"forgingstack-mandate-check": {
"command": "uvx",
"args": [
"forgingstack-mandate-check"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Install ForgingStack Mandate Check MCP in Codex
$ codex mcp add forgingstack-mandate-check --env 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' -- uvx forgingstack-mandate-checkInstall ForgingStack Mandate Check MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.forgingstack-mandate-check] command = "uvx" args = ["forgingstack-mandate-check"] [mcp_servers.forgingstack-mandate-check.env] FORGINGSTACK_API_KEY = "<YOUR_FORGINGSTACK_API_KEY>"
Install ForgingStack Mandate Check MCP in Gemini CLI
$ gemini mcp add -s user -e 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' forgingstack-mandate-check uvx -- forgingstack-mandate-checkInstall ForgingStack Mandate Check MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"forgingstack-mandate-check": {
"command": "uvx",
"args": [
"forgingstack-mandate-check"
],
"env": {
"FORGINGSTACK_API_KEY": "<YOUR_FORGINGSTACK_API_KEY>"
}
}
}
}Configuration
FORGINGSTACK_API_KEYRequiredSecretAPI key for Mandate Check. Sign up via POST /v1/signup (key shown once).
FORGINGSTACK_API_BASEMandate Check API base URL. Live default.
| Name | Description | |
|---|---|---|
| FORGINGSTACK_API_KEY | API key for Mandate Check. Sign up via POST /v1/signup (key shown once). | RequiredSecret |
| FORGINGSTACK_API_BASE | Mandate Check API base URL. Live default. |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablejdkabattles/forgingstack-mandate-check is public and reachablegithub.com/jdkabattles/forgingstack-mandate-check ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-04github.com/jdkabattles/forgingstack-mandate-check ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from forgingstack-mandate-checkPass
- No critical advisory in the package or its dependencies1 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubForgingStack Mandate Check
Before your agent acts, check its mandate. One call, one receipt.
mcp-name: io.github.jdkabattles/forgingstack-mandate-check
This is the public client for Mandate Check. The service itself — the decision logic, the receipt chain, the key store, and billing — runs on ForgingStack's private service and is not in this repo. Copying this repo does not give you the service: you still need an API key and credits, from signup below.
Live API: https://forgingstack-mandate-check.jkbattles.workers.dev
What it checks, in order
- Mandate agent matches the calling agent
- Mandate principal matches the principal the agent acts for
- Mandate expiry is parseable and in the future
- Action is in the mandate's allowed actions
Pass or fail, you get a reason and a hash-chained receipt.
What it does not do: decide if an action is wise, legal, or safe. Mandate fit only.
Signup (v1)
curl -X POST https://forgingstack-mandate-check.jkbattles.workers.dev/v1/signup \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com"}'
Returns an API key once and 100 starter credits. Save the key immediately — it is stored only as a hash and cannot be shown again. Email verification is pending, and credit-pack billing is not live yet, so do not expect a purchase flow in v1.
Agent sub-keys
A signed-up human creates a key for each agent, capped and revocable:
curl -X POST https://forgingstack-mandate-check.jkbattles.workers.dev/v1/keys \
-H "X-API-Key: YOUR_PRIMARY_KEY" -H "Content-Type: application/json" \
-d '{"agent_name":"my-agent","credits":20}'
List with GET /v1/keys, revoke with DELETE /v1/keys/{id} —
revoking returns unused credits to the primary account.
Use it (MCP, stdio)
Set the key, then run the MCP server in this repo:
export FORGINGSTACK_API_KEY="your-key-here"
python -m app.mcp_server
Tools: check_mandate, get_credits, get_receipt.
See SKILL.md for when to use it and when not to.
Price
1 credit per check call. A failed decision still costs 1 credit —
the check was performed. An idempotent replay (same
Idempotency-Key) is free and returns the original receipt.
Files in this repo
app/mcp_server.py— MCP wrapper client (stdio, stdlib only)SKILL.md— when to use it, how to read pass/failagent-card.json— A2A-style discovery cardserver.json— MCP Registry metadata (draft until PyPI publish)pyproject.toml— package metadata for the MCP client
ForgingStack Mandate Check MCP questions
How do I add ForgingStack Mandate Check MCP to Claude Code?
Run claude mcp add --env 'FORGINGSTACK_API_KEY=<YOUR_FORGINGSTACK_API_KEY>' forgingstack-mandate-check -- uvx forgingstack-mandate-check in your terminal. Add --scope user to make it available in every project.
How do I add ForgingStack Mandate Check MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What specific criteria does the mandate check?
The service checks if the mandate agent matches the calling agent, if the principal matches, if the expiry is in the future, and if the action is allowed.
How much does each check cost?
Each check call costs 1 credit, including failed decisions, though idempotent replays are free.
Can I recover my API key if I lose it?
No, the API key is only shown once during signup and is stored only as a hash.