scout

endpoint

https://scout.clarved.com/mcp

protocol

streamable-http ·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 scout live?

Yes — it answered the hub's last check (checked 27m ago). It answered 100% of checks over the last 30 days.

Is scout 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 scout have?

7 tools: list_watches, delete_watch, account_status, get_watch, add_watch, update_watch, trigger_scan.

Is scout 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.

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.

• list_watches auth-required 27m ago

  List the signed-in Scout account's watches (store collection URLs being monitored), including cadence, active state, and last check time.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• delete_watch auth-required never probed

  Remove a watch. The watch is archived (no further scans or emails); its stored items stay in Scout history.

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "watchId": {
        "type": "string",
        "description": "Watch id from list_watches."
      }
    },
    "additionalProperties": false
  }

  arguments 10 lines copy
• account_status auth-required 27m ago

  Show the Scout account's plan, watch limit, allowed cadences, and how digest emails are delivered.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• get_watch auth-required 27m ago

  Inspect one watch in detail: its settings, the most recent scan result, and the newest products seen on the page.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "properties": {
      "watchId": {
        "type": "string",
        "description": "Watch id from list_watches."
      },
      "itemLimit": {
        "type": "number",
        "description": "How many recent items to return (default 20, max 50)."
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• add_watch auth-required never probed

  Start watching a public store collection or category URL (e.g. a Shopify /collections/new-arrivals page) and email the account owner when new products appear. The first scan is a baseline: nothing is emailed. Watch out: the dogfood plan caps watches per account.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "properties": {
      "url": {
        "type": "string",
        "description": "Public collection or category page URL (https)."
      },
      "email": {
        "enum": [
          "instant",
          "daily",
          "weekly"
        ],
        "type": "string",
        "description": "When to email about this watch: instant emails right after a scan finds something; daily/weekly hold finds for one roll-up email at the account's chosen slot. Default: instant."
      },
      "label": {
        "type": "string",
        "description": "Optional human name for the watch."
      },
      "notes": {
        "type": "string",
        "description": "Optional free-text note."
      },
      "cadence": {
        "enum": [
          "hourly",
          "six_hours",
          "daily",
          "weekly"
        ],
        "type": "string",
        "description": "How often to re-check the page. Default: daily."
      }
    },
    "additionalProperties": false
  }

  arguments 37 lines copy
• update_watch auth-required never probed

  Update one of the account's watches: rename it, change its check frequency, change when it emails you, add notes, or pause/resume scanning.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041

  {
    "type": "object",
    "properties": {
      "email": {
        "enum": [
          "instant",
          "daily",
          "weekly"
        ],
        "type": "string",
        "description": "When to email about this watch: instant, or held for the daily/weekly roll-up."
      },
      "label": {
        "type": "string",
        "description": "New name for the watch."
      },
      "notes": {
        "type": "string",
        "description": "Free-text note."
      },
      "active": {
        "type": "boolean",
        "description": "false pauses the watch, true resumes it."
      },
      "cadence": {
        "enum": [
          "hourly",
          "six_hours",
          "daily",
          "weekly"
        ],
        "type": "string",
        "description": "New check frequency."
      },
      "watchId": {
        "type": "string",
        "description": "Watch id from list_watches."
      }
    },
    "additionalProperties": false
  }

  arguments 41 lines copy
• trigger_scan auth-required never probed

  Run a scan of one watch right now. This on-demand scan does NOT email a digest; scheduled scans send the digest emails. Scans are locked for a few minutes, so repeat calls may report the in-flight scan instead.

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "watchId": {
        "type": "string",
        "description": "Watch id from list_watches."
      }
    },
    "additionalProperties": false
  }

  arguments 10 lines copy

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

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.