Skip to content
External endpointresponds

Duvo MCP

Governed retail, FMCG, and CPG operational tools: runs, cases, approvals, audit-ready execution.

Endpoint URL
https://api.duvo.ai/v1/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
204 ms
Response record
1 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.duvoai/duvo

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
duvo-public-api
Version
1.0.0
Capability keys
tools
Instructions excerpt

Duvo terminology — UI labels and API/tool names refer to the same concepts: - "Agent" (UI) = "agent" / agent_id (a configured AI worker). - "Run" (UI) = "run" / agent_run_id (a single execution of an Agent). - "Connections" (UI) = "integrations". - "Files" (UI) = "knowledge base". - "AOP" (UI) = an Agent's instructions. - "Start Work" (UI) = creating a run. Tool names and parameters use the API terms; user-facing language uses the UI terms. Team context — most tools act on a single team and take a `team_id`: - Pass `team_id` explicitly. A user can belong to several teams and can have more than one open at once, so the right team is the one this request is about — not whichever one happened to be used last. - Take it from what the user asked for, or from the context you were invoked in. Act on another team only when the request points there; do not survey the user's teams and act on them speculatively. - Use `listMyTeams` to look up an id once you know which team you need

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. needs a key
    MCP initialize · 8s limit · HTTP 401 · 283ms
  2. needs a key
    MCP initialize · 8s limit · HTTP 401 · 213ms
  3. needs a key
    MCP initialize · 8s limit · HTTP 401 · 209ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 204ms