For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-20T12:38:06.404473+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://api.duvo.ai/v1/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T12:38:06.404473+00:00",
"registry_status": null,
"subject": {
"id": "io.github.duvoai/duvo",
"kind": "mcp"
},
"tools": {
"names": [
"acceptClarityCaptureSuggestion",
"acceptClarityLandscapeNode",
"acceptClarityProcessJoin",
"acceptClarityTeamAssignmentSuggestion",
"acceptRevisionGeneration",
"addAutomationAgent",
"addAutomationQueue",
"addClarityLandscapeNodePerson",
"addConfigField",
"addConfigSection",
"answerPulseDashboardQuestion",
"assignCaseLabels",
"assignClarityExtraCaptureRequest",
"assignClarityLandscapeCaptureRequest",
"assignClarityLandscapeNodeTeam",
"assignClarityProcessLabels",
"assignPolicyInterview",
"assignProcessMember",
"attachPulseDashboardConnection",
"attachQueueJsonSchema",
"attachRevisionIntegrations",
"attachRevisionLogin",
"attachRevisionSecret",
"authorizeMcpOAuth",
"batchAddClarityLandscapeNodePeople",
"buildClarityAutomation",
"bulkCreateTeamInvites",
"bulkReprocessCases",
"bulkUpdateCasePriority",
"bulkUpdateCaseStatus",
"cancelBuilderRun",
"checkMcpOAuth",
"completeClarityArtifactImport",
"completeClarityDocumentUpload",
"completeClarityImageUpload",
"completeClarityOrganizationDocumentUpload",
"completeClarityTeamDocumentUpload",
"completeClarityVideoUpload",
"connectPulseDataSource",
"consumeAgentSuggestion",
"createAgent",
"createAgentCaseTrigger",
"createAgentFolder",
"createAgentSlackTrigger",
"createAutomation",
"createCaseAttachmentUploadUrl",
"createCaseQueueEvalRubric",
"createCases",
"createClarityArtifactImportUploadUrl",
"createClarityDocumentUploadUrl",
"createClarityFolder",
"createClarityGuidance",
"createClarityImageUploadUrl",
"createClarityInviteLink",
"createClarityLandscapeNode",
"createClarityOrganizationDocumentUploadUrl",
"createClarityProcess",
"createClarityProcessLabel",
"createClarityProcessLink",
"createClarityProcessNode",
"createClarityTeamDocumentUploadUrl",
"createClarityVideoUploadUrl",
"createConnection",
"createCredential",
"createCustomIntegration",
"createEvalRubric",
"createFileUploadUrl",
"createOrgTeam",
"createPulseDashboard",
"createPulseDashboardAttachmentUploadUrl",
"createPulseDashboardComment",
"createPulseDashboardCommentReply",
"createQueue",
"createQueueAggregation",
"createQueueJsonSchema",
"createQueueLabel",
"createRevision",
"createSandbox",
"createSandboxUploadUrl",
"createSchedule",
"createSecret",
"createSkill",
"createSkillRevision",
"createTeamInvite",
"createTeamInviteLink",
"createWorkspace",
"declineClarityLandscapeNode",
"declineRevisionGeneration",
"deleteAgent",
"deleteAgentCaseTrigger",
"deleteAgentFolder",
"deleteAgentTrigger",
"deleteAllNotifications",
"deleteAutomation",
"deleteCase",
"deleteCaseAttachment",
"deleteCaseQueueEvalRubric",
"deleteClarityArtifactChatConversation",
"deleteClarityCapture",
"deleteClarityFolder"
],
"names_truncated": true,
"sha256": "7ab59afbbf0a420f574ec09e2a59fd3d5bddf98e4185f07b45ac21613ac34033"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T12:38:06.404473+00:00",
"version": "2026-05-24"
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology