Ebenova Scope Guard runs on your own machine — the client starts it, so there is no endpoint to ping. 33 installs a week from npm. Last commit 13 Apr 2026.
AI contract scope violation detector. Detect scope creep, draft responses.
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет @ebenova/scope-guard-mcp ссылается на ebenova/scope-guard-mcp
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add ebenova-scope-guard -e 'EBENOVA_API_KEY=<EBENOVA_API_KEY>' -- npx -y @ebenova/scope-guard-mcp
{
"mcpServers": {
"ebenova-scope-guard": {
"command": "npx",
"args": [
"-y",
"@ebenova/scope-guard-mcp"
],
"env": {
"EBENOVA_API_KEY": "<EBENOVA_API_KEY>"
}
}
}
}
[mcp_servers.ebenova-scope-guard]
command = "npx"
args = ["-y", "@ebenova/scope-guard-mcp"]
env = { EBENOVA_API_KEY = "<EBENOVA_API_KEY>" }
{
"mcpServers": {
"ebenova-scope-guard": {
"command": "npx",
"args": [
"-y",
"@ebenova/scope-guard-mcp"
],
"env": {
"EBENOVA_API_KEY": "<EBENOVA_API_KEY>"
}
}
}
}
{
"servers": {
"ebenova-scope-guard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ebenova/scope-guard-mcp"
],
"env": {
"EBENOVA_API_KEY": "<EBENOVA_API_KEY>"
}
}
}
}
Put your own value in place of
<EBENOVA_API_KEY> (Ebenova API key from ebenova.dev/dashboard).
The author’s registry entry marks it as required.
Read Figlime jobs, screening questions, and candidate responses; draft screening questions.
E-signatures for contracts and NDAs. Draft with AI, review, and send for signature.
AI support agent — ticket classification, response drafting, escalation routing.
Detect when AI code changes exceed declared task scope (MCP server).
Write a freelance service contract: scope, deliverables, rate, termination, liability, signatures.
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.
Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.
Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.
Answers built from our own checks of this server.