io.github.louissarvin/proctor
NPM · PROCTOR-MCP · SCANNED SEP 25
Human oversight for AI agents: block a tool call on a verified human, with on-chain proof.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @grpc/grpc-js 1.12.6, reached via @x402/hedera > @hiero-ledger/sdk > @grpc/grpc-js. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 105 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 180 tokens (~180/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.louissarvin/proctor MCP server?
io.github.louissarvin/proctor runs locally as an npm package, launched with npx -y proctor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · proctor-mcp
claude mcp add louissarvin-proctor -- npx -y proctor-mcp
{
"mcpServers": {
"louissarvin-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp"
]
}
}
} {
"servers": {
"louissarvin-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp"
]
}
}
} codex mcp add louissarvin-proctor -- npx -y proctor-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"louissarvin-proctor": {
"type": "local",
"command": [
"npx",
"-y",
"proctor-mcp"
],
"enabled": true
}
}
} openclaw mcp add louissarvin-proctor --command npx --arg -y --arg proctor-mcp
mcp_servers:
louissarvin-proctor:
command: "npx"
args: ["-y", "proctor-mcp"] {
"McpServers": {
"louissarvin-proctor": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"proctor-mcp"
]
}
}
} assistant mcp add louissarvin-proctor -t stdio -c npx -a -y proctor-mcp
{
"mcpServers": {
"louissarvin-proctor": {
"command": "npx",
"args": [
"-y",
"proctor-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 15 Sept 26 +5
- Source repository: unverified → pass ▲ security
- 14 Sept 26 −5
- Provenance: pass → unverified ▼ security
- 11 Sept 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/proctor-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 9 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-5375-pq7m-f5r2 | CVE-2026-48068 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-99f4-grh7-6pcq | CVE-2026-48069 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-94rc-8x27-4472 | CVE-2026-54270 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-f38q-mgvj-vph7 | CVE-2026-54269 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-j3f2-48v5-ccww | CVE-2026-59877 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-jfj6-75fj-8934 | CVE-2026-59876 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-wcpc-wj8m-hjx6 | CVE-2026-48712 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-58qx-3vcg-4xpx | CVE-2026-45736 | medium | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-96hv-2xvq-fx4p | CVE-2026-48779 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Deprecated | 1 |
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
request_human_approval Request human approval ~149
Block until a verified human who is NOT the operator of this agent approves or refuses a high-risk action. Fails closed: no answer before the deadline is a refusal. Returns a tamper-evident citation on a Hedera topic with no admin key, so the decision can be proven to a third party later. Use before any irreversible or high-value action.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What the agent is about to do, in plain language. |
| amount | string | – | Amount, as a decimal string. Drives the policy threshold. |
| counterparty | string | – | Who receives the value. |
| ttlSeconds | number | – | Deadline. Default 300, max 900. |
| Name | Type | Req | Description |
|---|---|---|---|
| approved | boolean | yes | – |
| decisionHash | string | – | – |
| escalated | boolean | – | False when policy allowed it without a human. |
| evidence | string | – | Where the record can be verified. |
| outcome | string | yes | APPROVE, REFUSE or EXPIRE. |
No examples provided.
What is the io.github.louissarvin/proctor MCP server?
io.github.louissarvin/proctor is an MCP server listed in the public MCP registry as io.github.louissarvin/proctor. Human oversight for AI agents: block a tool call on a verified human, with on-chain proof. This page covers its npm package (proctor-mcp).
Is the io.github.louissarvin/proctor MCP server safe to use?
io.github.louissarvin/proctor scores 73 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.louissarvin/proctor MCP server expose?
io.github.louissarvin/proctor exposes 1 tool: request_human_approval. Their descriptions and schemas cost roughly 149 tokens of context every time the server is loaded.
Is the io.github.louissarvin/proctor MCP server still maintained?
io.github.louissarvin/proctor is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.louissarvin/proctor MCP server under?
io.github.louissarvin/proctor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.