Skip to content

Scout MCP server

io.github.schybo/scoutschybostreamable-httpv0.1.1Scanned

Watch public store collection pages; your AI agent adds, pauses, and scans watches over MCP.

7 tools: 1 can delete or cancel things, 3 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Scout MCP server can do

The Scout MCP server is published by the GitHub account schybo. It has 7 tools. It can delete or cancel things (1 tool: delete_watch) and create or change data (3 tools: add_watch, update_watch and trigger_scan). 3 tools only read.

1 tool reads private data (account_status); 1 tool brings in text other people can write (account_status); 1 tool can send data out of your system (add_watch). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Deletes or cancels 1Claude Code: deny
  • delete_watchRemove a watch.No findings

    Why it is in this group

    • The name "delete_watch" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Remove a watch. The watch is archived (no further scans or emails); its stored items stay in Scout history.
Changes things 3Claude Code: ask
  • add_watchStart watching a public store collection or category URL (e.g.Can send data outNo findings

    Why it is in this group

    • The name "add_watch" says "add": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • trigger_scanRun a scan of one watch right now.No findings

    Why it is in this group

    • The name "trigger_scan" says "trigger": a word for a change.
    Description, as the server wrote it
    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.
  • update_watchUpdate one of the account's watches: rename it, change its check frequency, change when it emails you, add notes, or pause/resume scanning.No findings

    Why it is in this group

    • The name "update_watch" says "update": a word for a change.
    Description, as the server wrote it
    Update one of the account's watches: rename it, change its check frequency, change when it emails you, add notes, or pause/resume scanning.
Only reads 3Show 3 read-only tools
  • account_statusShow the Scout account's plan, watch limit, allowed cadences, and how digest emails are delivered.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "account_status" says "status": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "show" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "show" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Show the Scout account's plan, watch limit, allowed cadences, and how digest emails are delivered.
  • get_watchInspect one watch in detail: its settings, the most recent scan result, and the newest products seen on the page.No findings

    Why it is in this group

    • The name "get_watch" says "get": a word for reading.
    Description, as the server wrote it
    Inspect one watch in detail: its settings, the most recent scan result, and the newest products seen on the page.
  • list_watchesList the signed-in Scout account's watches (store collection URLs being monitored), including cadence, active state, and last check time.No findings

    Why it is in this group

    • The name "list_watches" says "list": a word for reading.
    Description, as the server wrote it
    List the signed-in Scout account's watches (store collection URLs being monitored), including cadence, active state, and last check time.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__scout__add_watch"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://scout.clarved.com/mcp: tools/list returned 7 tools to an anonymous client, including delete_watch (destructive), add_watch (write), update_watch (write), trigger_scan (write)

    What this check looks for

Posture changes

  1. Nov 15, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 4 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http scout https://scout.clarved.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http scout https://scout.clarved.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__scout__list_watches",
      "mcp__scout__get_watch",
      "mcp__scout__account_status"
    ],
    "ask": [
      "mcp__scout__add_watch",
      "mcp__scout__update_watch",
      "mcp__scout__trigger_scan"
    ],
    "deny": [
      "mcp__scout__delete_watch"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as scout. Review it before you use it.

Capability tags behind 2 rules
  • mcp__scout__add_watch outbound
  • mcp__scout__account_status private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.schybo/scout/verify?hash=479c1a9dce47dcd6ab50492fbed9a13b6f563a162491f877a1b37eb8c009a339" | jq -e '.changed == false'

Pinned hash 479c1a9dce47, from Nov 10, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.schybo/scout/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.schybo/scout
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.schybo/scout.svg)](https://radar.anlyon.com/servers/io.github.schybo/scout)

Source: MCP Registry · repository. Synced Nov 10, 2026, 02:17 UTC.

Scout MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Scout MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Scout MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_watch.

Can the Scout MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Scout MCP server have?

7 tools: 1 destructive, 3 write, 3 read. delete_watch, add_watch, update_watch, trigger_scan, list_watches, get_watch and account_status.

Does the Scout MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Scout MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): add_watch.

Has the Scout MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.