Raposa Aval

Human approval for AI agents.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inRU / CISFreeRead-only

What it can do

  • Create Approval: 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.
  • Get Approval: Read an approval by id. Look at `approved` — it is true only when a human approved.
  • Request Human Approval: Ask an authorised human to approve an action and wait for the answer (up to wait_sec, max 50). Returns {approved: bool, status, decided_by, ...}. Proceed ONLY if approved is tr

What data it sees

Do you need an account

No: the server works without sign-in

Human approval for AI agents. request_human_approval(action, context, risk) pauses a high-stakes action (refund, payout, deploy, deletion) until a named person approves or rejects in the console, by email, Telegram or Slack. Silence is not consent: a timeout, expiry or rejection returns approved=false. Every decision is sealed in a hash-chained audit log you can export. EU-hosted (Germany), DPA available. Free sandbox key (100 approvals/month): https://raposa.group/start/

How to connect

How to connect Raposa Aval to Claude

The server address to paste into Claude settings:

https://raposa--agentlabbusiness.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Raposa Aval to ChatGPT

The server address to paste into ChatGPT settings:

https://raposa--agentlabbusiness.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Raposa Aval to Cursor

The server address to paste into Cursor settings:

https://raposa--agentlabbusiness.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (3)

Raw names from tools/list. Only developers need these.

create_approvalCreate an approval request and return its id immediately (no waiting). Use with a webhook_url, or poll with get_approval. risk: low | medium | high.
get_approvalRead an approval by id. Look at `approved` — it is true only when a human approved.
request_human_approvalAsk an authorised human to approve an action and wait for the answer (up to wait_sec, max 50). Returns {approved: bool, status, decided_by, ...}. Proceed ONLY if approved is true — a timeout, an expiry or a rejection means do not proceed. On timeout the request stays open: check later with get_approval. risk: low | medium | high.