Schema | raposa-mcp

raposa-mcp

Official

Describes the environment variables required to run the server.

Name	Required	Description	Default
`RAPOSA_API_KEY`	Yes	Your Raposa API key, read only from RAPOSA_API_KEY and never appears in tool inputs or outputs.
`RAPOSA_API_BASE`	No	Base URL override for the Raposa API.	https://dcescrypt.com/api

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
create_approvalB	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_approvalA	Read an approval by id. Look at `approved` — it is true only when a human approved.
request_human_approvalA	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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentlabbusiness/raposa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server