signet-eval MCP server
io.github.jmcentire/signet-eval·v3.12.2·4 starsDeterministic policy enforcement and MCP management for AI agent tool calls.
4 stars
Reviews
Write oneNobody has reviewed signet-eval yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
signet-eval tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 17 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How signet-eval compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 42% of 4,460 AI and agents servers
- GitHub stars
- 4
- more than 77% of 2,711 AI and agents servers
Install signet-eval in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the signet-eval repository's README, as published. We do not edit it. Read it on GitHub
signet-eval
Deterministic policy enforcement for AI agent tool calls. Integrated tool calls pass through user-defined rules before execution. No LLM in the authorization path. Advisory nudges are separate from authorization.
Install
# crates.io
cargo install signet-eval
# from source
git clone https://github.com/wandercom/signet-eval
cd signet-eval
cargo install --path .There is no npm or PyPI package for signet-eval. The public distribution path is crates.io plus source install from GitHub. The MCP Registry listing points at the repository metadata; the runtime is the local signet-eval serve stdio server.
Quick Start
The command-hook adapters below remain supported and independent. For Claude Code's optional early-access function hooks, see the function adapter. It is disabled by default; installing/building this package does not activate it or change user settings.
1. Hook into Claude Code — add to ~/.claude/settings.json:
{
"hooks": {
"PreToolUse": [{
"matcher": "",
"hooks": [{"type": "command", "command": "signet-eval", "timeout": 2000}]
}]
}
}For Codex, enable hooks in ~/.codex/config.toml or /.codex/config.toml:
[features]
codex_hooks = trueThen add ~/.codex/hooks.json or /.codex/hooks.json:
{
"hooks": {
"PreToolUse": [{
"matcher": "*",
"hooks": [{
"type": "command",
"command": "signet-eval --adapter codex",
"timeout": 30000,
"statusMessage": "Checking Signet policy"
}]
}],
"PermissionRequest": [{
"matcher": "*",
"hooks": [{
"type": "command",
"command": "signet-eval --adapter codex-permission",
"timeout": 30000,
"statusMessage": "Checking Signet approval policy"
}]
}]
}
}For Antigravity, add this block to ~/.gemini/config/hooks.json (merge it with any existing hook groups):
{
"signet": {
"enabled": true,
"PreToolUse": [{
"matcher": "*",
"hooks": [{
"type": "command",
"command": "/bin/bash -lc 'source ~/.profile >/dev/null 2>&1 || true; exec signet-eval --adapter antigravity'",
"timeout": 30,
"statusMessage": "Checking Signet policy"
}]
}]
}
}The same configuration is available at hooks/antigravity-hooks.json.
2. Done. Every tool call now passes through policy evaluation. The default policy blocks destructive operations, protects its own configuration, and allows everything else.
3. (Optional) Customize — talk to Claude with the MCP server:
claude mcp add --scope user --transport stdio signet -- signet-eval serveThen say: "Add a $50 limit for amazon orders" or "Block all rm commands".
Default Policy
Self-protection rules are locked — they cannot be removed, edited, or reordered by the AI agent, even through the MCP management server. This prevents the agent from disabling its own guardrails.
Custom Policy
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
signet-eval: common questions
- Is signet-eval MCP server safe?
- Mostly: it is graded B (73/100). Read the signet-eval safety report
- Does signet-eval need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is signet-eval maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v3.12.2.
- What can I use instead of signet-eval?
- Servers from other publishers that do the same job: Ausca MCP server and AKShare MCP server.
- How does signet-eval compare with other AI and agents MCP servers?
- safety score 73/100 (higher than 42% of 4,460 AI and agents servers); github stars 4 (more than 77% of 2,711 AI and agents servers). Full comparison.
Alternatives to signet-eval
Same job from other publishers: the closest match first, then the best rated.