Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Duvo MCP

REMOTE · API.DUVO.AI · SCANNED OCT 15

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

Available components

−5 this week 88 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security92
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 49057 tokens (~120/item across 407 items; 393 tools + 14 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management65
  • Stability check failed: schema churn in the 20 days we've observed: 7 tool removals, 1 breaking changes, 0 auth/transport breaks, 19 additions. See how to fix → Fail
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety99
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 58 of 61 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "getEvalScores" implies "eval" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 395 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
Install

How do I install the Duvo MCP server?

Duvo MCP is a hosted endpoint at https://api.duvo.ai/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.duvo.ai

# add to Claude Code
claude mcp add --transport http duvoai-duvo 'https://api.duvo.ai/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "duvoai-duvo": {
      "url": "https://api.duvo.ai/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "duvoai-duvo": {
      "type": "http",
      "url": "https://api.duvo.ai/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.duvoai-duvo]
url = "https://api.duvo.ai/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "duvoai-duvo": {
      "type": "remote",
      "url": "https://api.duvo.ai/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add duvoai-duvo --url 'https://api.duvo.ai/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  duvoai-duvo:
    url: "https://api.duvo.ai/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "duvoai-duvo": {
      "Transport": "http",
      "Url": "https://api.duvo.ai/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add duvoai-duvo -t streamable-http -u 'https://api.duvo.ai/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "duvoai-duvo": {
      "type": "http",
      "url": "https://api.duvo.ai/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 15 Oct 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Oct 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 13 Oct 26 +2
    • Stability: 0.57 → fail ▼ security
    • Judged manipulation: unverified → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “removeConfigSection”, which the server declares destructive security
    • New tool “removeAutomationQueue”, which the server declares destructive security
    • New tool “removeAutomationAgent”, which the server declares destructive security
    • New tool “deleteSkillRevisionFile”, which the server declares destructive security
    • Tool “updateSchedule” rewrote its description, which is the text the model reads security
    • Tool “updateClarityProcess” rewrote its description, which is the text the model reads security
    • Tool “updateCase” rewrote its description, which is the text the model reads security
    • Tool “replaceEvalRubrics” rewrote its description, which is the text the model reads security
    • Tool “replaceCaseQueueEvalRubrics” rewrote its description, which is the text the model reads security
    • Tool “markNotificationRead” rewrote its description, which is the text the model reads security
    • Tool “markNotificationBatchRead” rewrote its description, which is the text the model reads security
    • Tool “listSecrets” rewrote its description, which is the text the model reads security
    • Tool “listRuns” rewrote its description, which is the text the model reads security
    • Tool “listIntegrations” rewrote its description, which is the text the model reads security
    • Tool “listConnections” rewrote its description, which is the text the model reads security
    • Tool “listConfigFields” rewrote its description, which is the text the model reads security
    • Tool “listClarityProcessMembers” rewrote its description, which is the text the model reads security
    • Tool “listAgentSchedules” rewrote its description, which is the text the model reads security
    • Tool “setClarityLandscapeNodePlacement” rewrote its description, which is the text the model reads security
    • Tool “getClarityProcessTree” rewrote its description, which is the text the model reads security
    • Tool “getClarityHierarchyPeople” rewrote its description, which is the text the model reads security
    • Tool “getAutomationCurrent” rewrote its description, which is the text the model reads security
    • Tool “getAutomation” rewrote its description, which is the text the model reads security
    • Tool “exportCases” rewrote its description, which is the text the model reads security
    • Tool “deleteTeamInvite” rewrote its description, which is the text the model reads security
    • Tool “deleteSchedule” rewrote its description, which is the text the model reads security
    • Tool “deleteClarityProcess” rewrote its description, which is the text the model reads security
    • Tool “createSkillRevision” rewrote its description, which is the text the model reads security
    • Tool “createSchedule” rewrote its description, which is the text the model reads security
    • Tool “createEvalRubric” rewrote its description, which is the text the model reads security
    • Tool “createClarityTeamDocumentUploadUrl” rewrote its description, which is the text the model reads security
    • Tool “createClarityProcessNode” rewrote its description, which is the text the model reads security
    • Tool “createClarityOrganizationDocumentUploadUrl” rewrote its description, which is the text the model reads security
    • Tool “createClarityLandscapeNode” rewrote its description, which is the text the model reads security
    • Tool “createClarityImageUploadUrl” rewrote its description, which is the text the model reads security
    • Tool “createClarityDocumentUploadUrl” rewrote its description, which is the text the model reads security
    • Tool “createCases” rewrote its description, which is the text the model reads security
    • Tool “createCaseQueueEvalRubric” rewrote its description, which is the text the model reads security
    • Tool “createAutomation” rewrote its description, which is the text the model reads security
    • Tool “createAgent” rewrote its description, which is the text the model reads security
    • Tool “bulkUpdateCaseStatus” rewrote its description, which is the text the model reads security
    • Tool “bulkReprocessCases” rewrote its description, which is the text the model reads security
    • Tool “assignClarityExtraCaptureRequest” rewrote its description, which is the text the model reads security
    • New resource “code-step-author/references/sdk.md” functional
    • New resource “code-step-author/SKILL.md” functional
    • New resource “clarity-mapping/SKILL.md” functional
    • New resource “aop-writer/agent.md” functional
    • New tool “updateSkillAskDuvo” functional
    • New tool “updateConfigFieldDefinition” functional
    • New tool “updateConfigField” functional
    • New tool “updateAutomationTabs” functional
    • New tool “setCaseJsonDataFields” functional
    • New tool “sendClarityInterviewInvites” functional
    • New tool “resumeBuilderRun” functional
    • New tool “restoreConfigField” functional
    • New tool “reorderConfigSections” functional
    • New tool “renameConfigSection” functional
    • New tool “moveAutomationsToFolder” functional
    • New tool “listPulseDataSources” functional
    • New tool “listOrgRuns” functional
    • New tool “listConfigSections” functional
    • New tool “listClarityInterviewInvites” functional
    • New tool “listAllAgentSchedules” functional
    • New tool “hideConfigField” functional
    • New tool “getBuilderRun” functional
    • New tool “generateRevision” functional
    • New tool “duplicateAutomation” functional
    • New tool “disconnectPulseDataSource” functional
    • New tool “declineRevisionGeneration” functional
    • New tool “createWorkspace” functional
    • New tool “connectPulseDataSource” functional
    • New tool “cancelBuilderRun” functional
    • New tool “addConfigSection” functional
    • New tool “addConfigField” functional
    • New tool “addAutomationQueue” functional
    • New tool “addAutomationAgent” functional
    • New tool “acceptRevisionGeneration” functional
    • “updateRevision” added an optional parameter “handoverOptions” cosmetic
    • “updateClarityProcess” added an optional parameter “independentInterviews” cosmetic
    • “updateCase” added an optional parameter “json_data” cosmetic
    • “startClarityExport” added an optional parameter “processOwnerRef” cosmetic
    • “startClarityExport” added an optional parameter “processApproverRef” cosmetic
    • “saveClarityProcessSnapshot” added an optional parameter “lanes” cosmetic
    • “removeClarityLandscapeNodePerson” added an optional parameter “pendingOnly” cosmetic
    • “markNotificationRead” added an optional parameter “openedFrom” cosmetic
    • “markNotificationBatchRead” added an optional parameter “openedFrom” cosmetic
    • “listRuns” added an optional parameter “include_total” cosmetic
    • “listRuns” added an optional parameter “cursor” cosmetic
    • “listConfigFields” added an optional parameter “include_hidden” cosmetic
    • “listClarityProcessMembers” added an optional parameter “contributorsAfter” cosmetic
    • “listCases” added an optional parameter “awaiting_my_approval” cosmetic
    • “listAgentRevisions” added an optional parameter “status” cosmetic
    • “getClarityProcessTree” added an optional parameter “ownerTeamId” cosmetic
    • “getClarityHierarchyPeople” added an optional parameter “userId” cosmetic
    • “getClarityHierarchyPeople” added an optional parameter “search” cosmetic
    • “getClarityHierarchyPeople” added an optional parameter “ownerTeamId” cosmetic
    • “createTeamInvite” added an optional parameter “process_role_id” cosmetic
    • “createTeamInvite” added an optional parameter “interviewRequested” cosmetic
    • “createRevision” added an optional parameter “handover_options” cosmetic
    • “createAutomation” added an optional parameter “first_agent” cosmetic
    • “upsertAgentTrigger” reworded the description of “trigger_type” cosmetic
    • “updateQueue” reworded the description of “name” cosmetic
    • “updateCase” reworded the description of “data” cosmetic
    • “respondToHumanRequest” reworded the description of “answers” cosmetic
    • “listRuns” reworded the description of “offset” cosmetic
    • “listRuns” reworded the description of “has_issues” cosmetic
    • “listRuns” reworded the description of “automation_id” cosmetic
    • “generateClarityProcessSnapshot” reworded the description of “transformation_aggressiveness” cosmetic
    • “createRevision” reworded the description of “source_build_id” cosmetic
    • “createRevision” reworded the description of “handover_target_ids” cosmetic
    • “createAgent” reworded the description of “source_build_id” cosmetic
    • “bulkReprocessCases” reworded the description of “agent_id” cosmetic
  • 12 Oct 26 −6

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “removeConfigSection”, which the server declares destructive security
    • New tool “removeAutomationRevisionQueue”, which the server declares destructive security
    • New tool “removeAutomationRevisionAgent”, which the server declares destructive security
    • New tool “removeAutomationQueue”, which the server declares destructive security
    • New tool “removeAutomationAgent”, which the server declares destructive security
    • New tool “deleteSkillRevisionFile”, which the server declares destructive security
    • New tool “deleteAutomationRevision”, which the server declares destructive security
    • Tool “updateSchedule” rewrote its description, which is the text the model reads security
    • Tool “updateClarityProcess” rewrote its description, which is the text the model reads security
    • Tool “updateCase” rewrote its description, which is the text the model reads security
    • Tool “setClarityLandscapeNodePlacement” rewrote its description, which is the text the model reads security
    • Tool “markNotificationRead” rewrote its description, which is the text the model reads security
    • Tool “markNotificationBatchRead” rewrote its description, which is the text the model reads security
    • Tool “listSecrets” rewrote its description, which is the text the model reads security
    • Tool “listRuns” rewrote its description, which is the text the model reads security
    • Tool “listIntegrations” rewrote its description, which is the text the model reads security
    • Tool “listConnections” rewrote its description, which is the text the model reads security
    • Tool “listConfigFields” rewrote its description, which is the text the model reads security
    • Tool “listClarityProcessMembers” rewrote its description, which is the text the model reads security
    • Tool “listAgentSchedules” rewrote its description, which is the text the model reads security
    • Tool “getClarityProcessTree” rewrote its description, which is the text the model reads security
    • New resource “code-step-author/references/sdk.md” functional
    • New resource “code-step-author/SKILL.md” functional
    • New resource “clarity-mapping/SKILL.md” functional
    • New resource “aop-writer/agent.md” functional
    • New tool “addAutomationQueue” functional
    • New tool “updateSkillAskDuvo” functional
    • New tool “updateConfigFieldDefinition” functional
    • New tool “updateConfigField” functional
    • New tool “updateAutomationTabs” functional
    • New tool “setCaseJsonDataFields” functional
    • New tool “setAutomationRevisionQueue” functional
    • New tool “setAutomationRevisionAgent” functional
    • New tool “sendClarityInterviewInvites” functional
    • New tool “resumeBuilderRun” functional
    • New tool “restoreConfigField” functional
    • New tool “reorderConfigSections” functional
    • New tool “renameConfigSection” functional
    • New tool “moveAutomationsToFolder” functional
    • New tool “listPulseDataSources” functional
    • New tool “listOrgRuns” functional
    • New tool “listConfigSections” functional
    • New tool “listClarityInterviewInvites” functional
    • New tool “listAllAgentSchedules” functional
    • New tool “hideConfigField” functional
    • New tool “getBuilderRun” functional
    • New tool “generateRevision” functional
    • New tool “duplicateAutomation” functional
    • New tool “disconnectPulseDataSource” functional
    • New tool “declineRevisionGeneration” functional
    • New tool “createWorkspace” functional
    • New tool “createAutomationRevision” functional
    • New tool “connectPulseDataSource” functional
    • New tool “cancelBuilderRun” functional
    • New tool “addConfigSection” functional
    • New tool “addConfigField” functional
    • New tool “addAutomationAgent” functional
    • New tool “activateAutomationRevision” functional
    • New tool “acceptRevisionGeneration” functional
    • “updateRevision” added an optional parameter “handoverOptions” cosmetic
    • “updateClarityProcess” added an optional parameter “independentInterviews” cosmetic
    • “updateCase” added an optional parameter “json_data” cosmetic
    • “startClarityExport” added an optional parameter “processOwnerRef” cosmetic
    • “startClarityExport” added an optional parameter “processApproverRef” cosmetic
    • “removeClarityLandscapeNodePerson” added an optional parameter “pendingOnly” cosmetic
    • “markNotificationRead” added an optional parameter “openedFrom” cosmetic
    • “markNotificationBatchRead” added an optional parameter “openedFrom” cosmetic
    • “listRuns” added an optional parameter “include_total” cosmetic
    • “listRuns” added an optional parameter “cursor” cosmetic
    • “listConfigFields” added an optional parameter “include_hidden” cosmetic
    • “listClarityProcessMembers” added an optional parameter “contributorsAfter” cosmetic
    • “listCases” added an optional parameter “awaiting_my_approval” cosmetic
    • “getClarityProcessTree” added an optional parameter “ownerTeamId” cosmetic
    • “upsertAgentTrigger” reworded the description of “trigger_type” cosmetic
    • “updateQueue” reworded the description of “name” cosmetic
    • “updateCase” reworded the description of “data” cosmetic
    • “listRuns” reworded the description of “offset” cosmetic
    • “listRuns” reworded the description of “has_issues” cosmetic
    • “listRuns” reworded the description of “automation_id” cosmetic
  • 10 Oct 26 −2

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 15 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 13 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 11 Sept 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

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 15 Oct 2026 · Probed https://api.duvo.ai/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=duvo.ai CN=WR3,O=Google Trust Services,C=US 14 Sept 2026 13 Dec 2026 RSA 2048 SHA256-RSA 5039dac58085db1410a340b5334ca95f
SANs: duvo.ai, *.duvo.ai
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.duvo.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
duvo.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://api.duvo.ai/.well-known/oauth-protected-resource", scope="openid profile email offline_access"

Bearer realm="mcp", resource_metadata="https://api.duvo.ai/.well-known/oauth-protected-resource", scope="openid profile email offline_access"

Protected resource metadata

Document https://api.duvo.ai/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://api.duvo.ai
Authorisation server https://login.duvo.ai/

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.duvo.ai/v1/mcp Verified 200
http (plaintext) http://api.duvo.ai/v1/mcp HTTPS enforced 301 https://api.duvo.ai:443/v1/mcp
MCP tools · 393 exposed · ~46,925 tokens partial

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 →

Tool Tokens
acceptClarityCaptureSuggestion ~44

No description provided.

NameTypeReqDescription
nodeIdstringyes–
suggestionIdstringyes–

No output schema declared.

No examples provided.

acceptClarityLandscapeNode ~96

No description provided.

NameTypeReqDescription
nodeIdstringyes–
orgIdstringyes–

No output schema declared.

No examples provided.

acceptClarityProcessJoin ~29

No description provided.

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

acceptClarityTeamAssignmentSuggestion ~48

No description provided.

NameTypeReqDescription
nodeIdstringyes–
suggestionIdstringyes–

No output schema declared.

No examples provided.

acceptRevisionGeneration ~91

No description provided.

NameTypeReqDescription
build_idstringyes–
builder_run_idstringyes–
expected_started_at–yes–

No output schema declared.

No examples provided.

addAutomationAgent ~105

No description provided.

NameTypeReqDescription
agent_idstringyes–
automation_idstringyes–

No output schema declared.

No examples provided.

addAutomationQueue ~106

No description provided.

NameTypeReqDescription
automation_idstringyes–
case_queue_idstringyes–

No output schema declared.

No examples provided.

addClarityLandscapeNodePerson ~116

No description provided.

NameTypeReqDescription
email–––
name–––
nodeIdstringyes–
orgIdstringyes–
role–––
teamIdstring––
teamRole–––

No output schema declared.

No examples provided.

addConfigField ~298

No description provided.

NameTypeReqDescription
automation_idstringyes–
bindingsarray––
columnsarray––
example–––
fill_modestring––
guidance–––
keystring––
labelstringyes–
optionsarray––
questionstringyes–
rolesarray––
section–––
typestringyes–

No output schema declared.

No examples provided.

addConfigSection ~146

No description provided.

NameTypeReqDescription
after_keystring––
automation_idstringyes–
namestringyes–

No output schema declared.

No examples provided.

answerPulseDashboardQuestion ~67

No description provided.

NameTypeReqDescription
answersobjectyes–
artifactIdstringyes–
toolCallIdstringyes–

No output schema declared.

No examples provided.

assignCaseLabels ~63

No description provided.

NameTypeReqDescription
case_idstringyes–
labelsarrayyes–
queue_idstringyes–

No output schema declared.

No examples provided.

assignClarityExtraCaptureRequest ~99

No description provided.

NameTypeReqDescription
process_idstringyes–
request_idstringyes–
transformation_proposal_idstringyes–
user_id–yes–

No output schema declared.

No examples provided.

assignClarityLandscapeCaptureRequest ~60

No description provided.

NameTypeReqDescription
nodeIdstringyes–
requestIdstringyes–
userId–yes–

No output schema declared.

No examples provided.

assignClarityLandscapeNodeTeam ~156

No description provided.

NameTypeReqDescription
intentstring––
nodeIdstringyes–
orgIdstringyes–
teamId–yes–

No output schema declared.

No examples provided.

assignClarityProcessLabels ~40

No description provided.

NameTypeReqDescription
idstringyes–
labelIdsarray––
labelsarray––

No output schema declared.

No examples provided.

attachPulseDashboardConnection ~53

No description provided.

NameTypeReqDescription
artifactIdstringyes–
connection_idstringyes–

No output schema declared.

No examples provided.

attachQueueJsonSchema ~63

No description provided.

NameTypeReqDescription
family_idstringyes–
queue_idstringyes–

No output schema declared.

No examples provided.

attachRevisionIntegrations ~246

No description provided.

NameTypeReqDescription
agent_idstringyes–
build_idstringyes–
integration_idsarrayyes–
selected_automation_revision_id–––

No output schema declared.

No examples provided.

attachRevisionLogin ~73

No description provided.

NameTypeReqDescription
agentIdstringyes–
buildIdstringyes–
exposedCredentialIdstringyes–

No output schema declared.

No examples provided.

attachRevisionSecret ~71

No description provided.

NameTypeReqDescription
agentIdstringyes–
buildIdstringyes–
credentialIdstringyes–

No output schema declared.

No examples provided.

authorizeMcpOAuth ~418

No description provided.

NameTypeReqDescription
custom_integration_idstring––
integration_typestring––
mcp_server_urlstringyes–
namestringyes–
oauth_client_idstring––
oauth_client_secretstring––
reconnect_instance_idstring––
return_urlstring––
team_idstring––

No output schema declared.

No examples provided.

batchAddClarityLandscapeNodePeople ~70

No description provided.

NameTypeReqDescription
nodeIdsarrayyes–
orgIdstringyes–
peoplearrayyes–

No output schema declared.

No examples provided.

buildClarityAutomation ~135

No description provided.

NameTypeReqDescription
process_idstringyes–
transformation_proposal_idstring––

No output schema declared.

No examples provided.

bulkCreateTeamInvites ~242

No description provided.

NameTypeReqDescription
frontendUrlstring––
membersarrayyes–
team_idstring––

No output schema declared.

No examples provided.

bulkReprocessCases ~215

No description provided.

NameTypeReqDescription
agent_idstring––
all_matchingboolean––
case_idsarray––
filtersobject––
queue_idstringyes–
searchstring––

No output schema declared.

No examples provided.

bulkUpdateCasePriority ~190

No description provided.

NameTypeReqDescription
all_matchingboolean––
case_idsarray––
filtersobject––
prioritystringyes–
queue_idstringyes–
searchstring––

No output schema declared.

No examples provided.

bulkUpdateCaseStatus ~302

No description provided.

NameTypeReqDescription
all_matchingboolean––
case_idsarray––
filtersobject––
queue_idstringyes–
searchstring––
statusstringyes–

No output schema declared.

No examples provided.

cancelBuilderRun ~53

No description provided.

NameTypeReqDescription
builder_run_idstringyes–
statusstringyes–

No output schema declared.

No examples provided.

checkMcpOAuth ~91

No description provided.

NameTypeReqDescription
mcp_server_urlstringyes–

No output schema declared.

No examples provided.

completeClarityArtifactImport ~119

No description provided.

NameTypeReqDescription
capture_idstringyes–
content_typestringyes–
file_namestringyes–
process_idstringyes–

No output schema declared.

No examples provided.

completeClarityDocumentUpload ~60

No description provided.

NameTypeReqDescription
captureIdstringyes–
fileNamestringyes–
idstringyes–

No output schema declared.

No examples provided.

completeClarityImageUpload ~62

No description provided.

NameTypeReqDescription
captureIdstringyes–
fileNamestringyes–
idstringyes–

No output schema declared.

No examples provided.

completeClarityOrganizationDocumentUpload ~72

No description provided.

NameTypeReqDescription
fileNamestringyes–
interviewIdstringyes–
orgIdstringyes–

No output schema declared.

No examples provided.

completeClarityTeamDocumentUpload ~128

No description provided.

NameTypeReqDescription
fileNamestringyes–
interviewIdstringyes–
team_idstring––

No output schema declared.

No examples provided.

completeClarityVideoUpload ~60

No description provided.

NameTypeReqDescription
captureIdstringyes–
fileNamestringyes–
idstringyes–

No output schema declared.

No examples provided.

connectPulseDataSource ~83

No description provided.

NameTypeReqDescription
artifact_idstringyes–
queue_idstringyes–

No output schema declared.

No examples provided.

consumeAgentSuggestion ~159

No description provided.

NameTypeReqDescription
create_new_draftboolean––
idstringyes–
revision_idstring––
selected_automation_revision_id–––

No output schema declared.

No examples provided.

createAgent ~302

No description provided.

NameTypeReqDescription
automation_id–––
buildobject––
namestringyes–
source_build_id–––
team_idstring––
thread_id–––
typestring––

No output schema declared.

No examples provided.

createAgentCaseTrigger ~183

No description provided.

NameTypeReqDescription
agent_idstringyes–
case_queue_idstringyes–
concurrency–––
enabledbooleanyes–

No output schema declared.

No examples provided.

createAgentFolder ~114

No description provided.

NameTypeReqDescription
namestringyes–
parent_folder_id–––
team_idstring––

No output schema declared.

No examples provided.

createAgentSlackTrigger ~346

No description provided.

NameTypeReqDescription
agent_idstringyes–
channel_idstringyes–
channel_namestringyes–
integration_instance_idstring––
is_privateboolean––
match_rule–yes–
slack_team_idstring––
trigger_typestringyes–

No output schema declared.

No examples provided.

createAutomation ~209

No description provided.

NameTypeReqDescription
first_agentobject––
namestringyes–
team_idstring––

No output schema declared.

No examples provided.

createCaseAttachmentUploadUrl ~102

No description provided.

NameTypeReqDescription
case_idstringyes–
filenamestringyes–
mime_typestringyes–
queue_idstringyes–
size_bytesintegeryes–

No output schema declared.

No examples provided.

createCaseQueueEvalRubric ~176

No description provided.

NameTypeReqDescription
descriptionstringyes–
queue_idstringyes–
titlestringyes–

No output schema declared.

No examples provided.

createCases ~323

No description provided.

NameTypeReqDescription
caseobject––
casesarray––
queue_idstringyes–

No output schema declared.

No examples provided.

createClarityArtifactImportUploadUrl ~141

No description provided.

NameTypeReqDescription
content_typestringyes–
extra_capture_request_idstring––
file_namestringyes–
process_idstringyes–

No output schema declared.

No examples provided.

createClarityDocumentUploadUrl ~101

No description provided.

NameTypeReqDescription
contentTypestringyes–
extraCaptureRequestIdstring––
fileNamestringyes–
idstringyes–

No output schema declared.

No examples provided.

createClarityFolder ~92

No description provided.

NameTypeReqDescription
namestringyes–
team_idstring––

No output schema declared.

No examples provided.

createClarityGuidance ~47

No description provided.

NameTypeReqDescription
contentstringyes–
idstringyes–

No output schema declared.

No examples provided.

Common questions

What is the Duvo MCP server?

Duvo MCP is listed in the public MCP registry as io.github.duvoai/duvo. Governed retail, FMCG, and CPG operational tools: runs, cases, approvals, audit-ready execution. This page covers its hosted endpoint (https://api.duvo.ai/v1/mcp).

Is the Duvo MCP server safe to use?

Duvo MCP scores 88 out of 100 on VerifyMCP. 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.

Does the Duvo MCP server require authentication?

Yes. Duvo MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Duvo MCP server still maintained?

Duvo MCP is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.