Raposa Aval — human approval
PYPI · RAPOSA-MCP · SCANNED SEP 22
Human approval for AI agents: a named person approves or rejects, silence is not consent.
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 18 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 281 tokens (~93/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Raposa Aval — human approval MCP server?
Raposa Aval — human approval runs locally as a PyPI package, launched with uvx raposa-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · raposa-mcp
claude mcp add group-raposa-raposa-mcp -- uvx raposa-mcp
{
"mcpServers": {
"group-raposa-raposa-mcp": {
"command": "uvx",
"args": [
"raposa-mcp"
]
}
}
} {
"servers": {
"group-raposa-raposa-mcp": {
"command": "uvx",
"args": [
"raposa-mcp"
]
}
}
} codex mcp add group-raposa-raposa-mcp -- uvx raposa-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"group-raposa-raposa-mcp": {
"type": "local",
"command": [
"uvx",
"raposa-mcp"
],
"enabled": true
}
}
} openclaw mcp add group-raposa-raposa-mcp --command uvx --arg raposa-mcp
mcp_servers:
group-raposa-raposa-mcp:
command: "uvx"
args: ["raposa-mcp"] {
"McpServers": {
"group-raposa-raposa-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"raposa-mcp"
]
}
}
} assistant mcp add group-raposa-raposa-mcp -t stdio -c uvx -a raposa-mcp
{
"mcpServers": {
"group-raposa-raposa-mcp": {
"command": "uvx",
"args": [
"raposa-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.
- 22 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 17 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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +4
- Stability: unverified → 0.23 ▲ functional
- 7 Sept 26 −15
- Malware scan: pass → unverified ▼ 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 22 Sept 2026 · Analysed pypi/raposa-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
create_approval ~85
Create an approval request and return its id immediately (no waiting). Use with a webhook_url, or poll with get_approval. risk: low | medium | high.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| context | string | yes | – |
| expires_in_sec | – | – | – |
| requested_by | string | – | – |
| risk | string | yes | – |
| webhook_url | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_approval ~38
Read an approval by id. Look at `approved` — it is true only when a human approved.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
request_human_approval ~110
Ask an authorised human to approve an action and wait for the answer. Returns {approved: bool, status, decided_by, ...}. Proceed ONLY if approved is true — a timeout, an expiry or a rejection means do not proceed. risk: low | medium | high.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| context | string | yes | – |
| expires_in_sec | – | – | – |
| requested_by | string | – | – |
| risk | string | yes | – |
| wait_sec | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Raposa Aval — human approval MCP server?
Raposa Aval — human approval is an MCP server listed in the public MCP registry as group.raposa/raposa-mcp. Human approval for AI agents: a named person approves or rejects, silence is not consent. This page covers its PyPI package (raposa-mcp).
Is the Raposa Aval — human approval MCP server safe to use?
Raposa Aval — human approval scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. 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 Raposa Aval — human approval MCP server expose?
Raposa Aval — human approval exposes 3 tools: create_approval, get_approval, request_human_approval. Their descriptions and schemas cost roughly 233 tokens of context every time the server is loaded.
Is the Raposa Aval — human approval MCP server still maintained?
Raposa Aval — human approval is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.