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.

CaptureOneAI Web Perception

REMOTE · CAPTUREONEAI.COM

Give agents eyes on any web page: structured context, and changes explained in plain language.

Available components

0 this week 87 Trust /100

Last scanned (15 hours ago)

Scores higher than 90% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Browser Automation

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 Security83
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 459 tokens (~76/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 44% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 22 Nov 2026 · Probed https://captureoneai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=captureoneai.com CN=YE2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 5c3574960af08c7d0351ed661edb8e42079
SANs: *.captureoneai.com, captureoneai.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of captureoneai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
captureoneai.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://captureoneai.com/mcp Verified 200
http (plaintext) http://captureoneai.com/mcp HTTPS enforced 301 https://captureoneai.com/mcp
MCP tools · 6 exposed · ~459 tokens

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
capture_context ~90

Returns the structured representation of a web page: visible text with coordinates, interactive elements, forms and tables. Use this to let an agent read and understand a page without parsing raw HTML.

NameTypeReqDescription
dismissCookiesboolean–Auto-dismiss cookie/consent banners before reading. Default true.
heightinteger––
urlstringyesThe page to read
widthinteger––

No output schema declared.

No examples provided.

check_monitor ~51

Triggers an immediate check for a monitor instead of waiting for its next scheduled run, and returns any detected changes.

NameTypeReqDescription
monitorIdstringyesThe monitor ID from create_semantic_monitor or list_monitors

No output schema declared.

No examples provided.

create_semantic_monitor ~146

Watches a URL on a schedule and reports what changed and whether it matters, explained by AI — not just a pixel-diff percentage. Use this for competitor pricing pages, changelogs, status pages, or any page whose changes should trigger a workflow.

NameTypeReqDescription
callbackUrlstring–Where to POST the change payload when something changes
intentstring–What you care about, in plain language, e.g. "alert me about pricing or plan changes"
labelstring––
schedulestring–Cron expression, e.g. "*/30 * * * *". Defaults to every 10 minutes.
urlstringyes–

No output schema declared.

No examples provided.

find_elements ~98

Returns only the interactive elements of a page (buttons, links, inputs) with role, label, CSS selector and pixel coordinates. Use this before acting on a page (computer-use / Set-of-Marks style grounding) instead of capture_context when you only need to know what can be clicked and where.

NameTypeReqDescription
dismissCookiesboolean––
heightinteger––
urlstringyes–
widthinteger––

No output schema declared.

No examples provided.

get_monitor_changes ~53

Returns the recent check history for a monitor, including detected changes with their relevance and explanation.

NameTypeReqDescription
limitinteger–Max number of recent checks to return. Default 20.
monitorIdstringyes–

No output schema declared.

No examples provided.

list_monitors ~21

Lists your active monitors and their IDs, URLs and schedules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the CaptureOneAI Web Perception MCP server?

CaptureOneAI Web Perception is a hosted endpoint at https://captureoneai.com/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 · captureoneai.com

# add to Claude Code
claude mcp add --transport http com-captureoneai-web-perception 'https://captureoneai.com/mcp'
Common questions

What is the CaptureOneAI Web Perception MCP server?

CaptureOneAI Web Perception is an MCP server listed in the public MCP registry as com.captureoneai/web-perception. Give agents eyes on any web page: structured context, and changes explained in plain language. This page covers its hosted endpoint (https://captureoneai.com/mcp).

Is the CaptureOneAI Web Perception MCP server safe to use?

CaptureOneAI Web Perception scores 87 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.

What tools does the CaptureOneAI Web Perception MCP server expose?

CaptureOneAI Web Perception exposes 6 tools: capture_context, find_elements, create_semantic_monitor, list_monitors, check_monitor, get_monitor_changes. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.

Does the CaptureOneAI Web Perception MCP server require authentication?

Yes. CaptureOneAI Web Perception 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 CaptureOneAI Web Perception MCP server still maintained?

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

What did VerifyMCP test on the CaptureOneAI Web Perception MCP server?

VerifyMCP ran 13 checks on CaptureOneAI Web Perception, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.