mcp-registry/com.captureoneai/web-perception · v1.0.0
As of 2026-10-22 23:18 UTC, the Captureoneai Web Perception MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Give agents eyes on any web page: structured context, and changes explained in plain language.
Claude Code
claude mcp add --transport http captureoneai-web-perception-mcp-server https://captureoneai.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"captureoneai-web-perception-mcp-server": {
"type": "http",
"url": "https://captureoneai.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
9 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.captureoneai%2Fweb-perception/fixes
{
"name": "check_monitor",
"description": "Triggers an immediate check for a monitor instead of waiting for its next scheduled run, and returns any detected changes.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"monitorId"
],
"properties": {
"monitorId": {
"type": "string",
"description": "The monitor ID from create_semantic_monitor or list_monitors"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Check a monitor now"
}{
"name": "create_semantic_monitor",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri"
},
"label": {
"type": "string",
"maxLength": 100
},
"intent": {
"type": "string",
"maxLength": 500,
"description": "What you care about, in plain language, e.g. \"alert me about pricing or plan changes\""
},
"schedule": {
"type": "string",
"description": "Cron expression, e.g. \"*/30 * * * *\". Defaults to every 10 minutes."
},
"callbackUrl": {
"type": "string",
"format": "uri",
"description": "Where to POST the change payload when something changes"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create a semantic monitor"
}{
"name": "find_elements",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri"
},
"width": {
"type": "integer",
"maximum": 3840,
"minimum": 100
},
"height": {
"type": "integer",
"maximum": 2160,
"minimum": 100
},
"dismissCookies": {
"type": "boolean"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Find interactive elements"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.captureoneai/web-perception"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.captureoneai/web-perception"}) over MCP.
create_semantic_monitor ~252 tokenscapture_context ~193 tokensfind_elements ~185 tokensget_monitor_changes ~129 tokenscheck_monitor ~118 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.captureoneai%2Fweb-perception?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.captureoneai%2Fweb-perception?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.captureoneai%2Fweb-perception.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.captureoneai%2Fweb-perception.svg :target: https://glimind.com/server/mcp-registry%2Fcom.captureoneai%2Fweb-perception?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6e4030982be6bcf3…, first seen 2026-10-17, included at leaf 564 of 48,699. Version history · verify what your client received.
Compare: most reliable browser servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 23:18 UTC, the Captureoneai Web Perception MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Captureoneai Web Perception MCP server advertises 6 tools, including capture_context, check_monitor, create_semantic_monitor, find_elements, get_monitor_changes.
Point your MCP client at this streamable-http endpoint: https://captureoneai.com/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.