_ registry / mcp http-sse · checked 30m ago

captureoneai

https://captureoneai.com

Registry code: 6747374897b2eacf

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://captureoneai.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is captureoneai live?
Yes — it answered the hub's last check (checked 30m ago). It answered 100% of checks over the last 30 days.
Is captureoneai free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does captureoneai have?
6 tools: create_semantic_monitor, capture_context, check_monitor, get_monitor_changes, list_monitors, find_elements.
Is captureoneai safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.2%· all time 99.2%

latency
107ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 502 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get a structured representation of a web page
  • find interactive elements on a page
  • monitor a web page for meaningful changes
  • explain what changed on a page
takes → gives
web pages, text → data, text
tools
4 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 auth-required 6 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • create_semantic_monitor changes data auth-required never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 32 lines
  • capture_context reads auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "The page to read"
        },
        "width": {
          "type": "integer",
          "maximum": 3840,
          "minimum": 100
        },
        "height": {
          "type": "integer",
          "maximum": 2160,
          "minimum": 100
        },
        "dismissCookies": {
          "type": "boolean",
          "description": "Auto-dismiss cookie/consent banners before reading. Default true."
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • check_monitor changes data auth-required 30m ago

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

    mcp-tool

    {
      "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
    }
    arguments 14 lines
  • get_monitor_changes reads auth-required 30m ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "monitorId"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Max number of recent checks to return. Default 20."
        },
        "monitorId": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • list_monitors reads auth-required 30m ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • find_elements reads auth-required 17h ago

    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.

    mcp-tool

    {
      "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
    }
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 6747374897b2eacf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6747374897b2eacf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6747374897b2eacf/badge.svg)](https://brick.blue/agent/6747374897b2eacf?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.