CaptureOneAI Web Perception
REMOTE · CAPTUREONEAI.COM · SCANNED SEP 25
Give agents eyes on any web page: structured context, and changes explained in plain language.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add --transport http com-captureoneai-web-perception 'https://captureoneai.com/mcp'
{
"mcpServers": {
"com-captureoneai-web-perception": {
"url": "https://captureoneai.com/mcp"
}
}
} {
"servers": {
"com-captureoneai-web-perception": {
"type": "http",
"url": "https://captureoneai.com/mcp"
}
}
} [mcp_servers.com-captureoneai-web-perception] url = "https://captureoneai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-captureoneai-web-perception": {
"type": "remote",
"url": "https://captureoneai.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-captureoneai-web-perception --url 'https://captureoneai.com/mcp' --transport streamable-http
mcp_servers:
com-captureoneai-web-perception:
url: "https://captureoneai.com/mcp" {
"McpServers": {
"com-captureoneai-web-perception": {
"Transport": "http",
"Url": "https://captureoneai.com/mcp"
}
}
} assistant mcp add com-captureoneai-web-perception -t streamable-http -u 'https://captureoneai.com/mcp'
{
"mcpServers": {
"com-captureoneai-web-perception": {
"type": "http",
"url": "https://captureoneai.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 73
First indexed and scored.
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 25 Sept 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 | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 61131b4fff0553e0d2f0c88eec27f1abc54 |
| 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. | present | 19718 | 13 | Verified |
| captureoneai.com. | absent | 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 |
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 →
capture_context Capture page 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dismissCookies | boolean | – | Auto-dismiss cookie/consent banners before reading. Default true. |
| height | integer | – | – |
| url | string | yes | The page to read |
| width | integer | – | – |
No output schema declared.
No examples provided.
check_monitor Check a monitor now ~51
Triggers an immediate check for a monitor instead of waiting for its next scheduled run, and returns any detected changes.
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | The monitor ID from create_semantic_monitor or list_monitors |
No output schema declared.
No examples provided.
create_semantic_monitor Create a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string | – | Where to POST the change payload when something changes |
| intent | string | – | What you care about, in plain language, e.g. "alert me about pricing or plan changes" |
| label | string | – | – |
| schedule | string | – | Cron expression, e.g. "*/30 * * * *". Defaults to every 10 minutes. |
| url | string | yes | – |
No output schema declared.
No examples provided.
find_elements Find interactive 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dismissCookies | boolean | – | – |
| height | integer | – | – |
| url | string | yes | – |
| width | integer | – | – |
No output schema declared.
No examples provided.
get_monitor_changes Get monitor change history ~53
Returns the recent check history for a monitor, including detected changes with their relevance and explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of recent checks to return. Default 20. |
| monitorId | string | yes | – |
No output schema declared.
No examples provided.
list_monitors 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.
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 75 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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.