Mmcp.market

Site Spy MCP server

by vkuprin·io.github.vkuprin/site-spy·v0.3.0

MCP server for Site Spy — lets AI agents monitor websites for changes

C55/100grade C
What users say
No reviews yet
Be the first
Safety scan
C55/100

full report

Adoption
New

38 downloads/wk

Reviews

Write one

Nobody has reviewed Site Spy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Site Spy tools (19, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • auth_status

    Check whether the MCP server is currently authenticated with Site Spy.

  • authenticate

    Connect to Site Spy with an API key. If the user doesn't have one, ask them to open … to log in and copy their key from the Settings > API tab. The key is held in memory only and is lost when the server restarts — set SITE_SPY_API_KEY to persist it.

  • create_watchwrite action

    Start monitoring a URL for changes. Returns the UUID of the new watch.

  • delete_watchwrite action

    Stop monitoring a URL and delete the watch with all its history.

  • fetch_url

    Fetch a single known URL through Site Spy. Do NOT use this for discovery — use web_search to find URLs first, then fetch_url on each result. Do NOT fetch google.com / bing.com directly (they always block — wastes the cascade budget). For known static sites prefer fetch_backend: 'html_requests' (≤10s). For SPAs use 'html_webdriver'. For Cloudflare-protected pages use 'flaresolverr'. 'auto' cascades

  • generate_rss_token

    Generate or regenerate an RSS feed token. Use the token to build feed URLs: {server}/rss?token={token} for all watches, {server}/rss/watch/{uuid}?token={token} for a single watch. Regenerating invalidates all existing feed URLs, so any reader already subscribed will stop receiving updates.

  • get_ai_summary

    Get the AI-generated plain-English summary of a watch's most recent change. Requires a Pro or Business plan. Returns the summary text if available, or a message if no summary exists yet.

  • get_change_history

    Get the list of timestamps when changes were detected for a watch. Use these timestamps with get_snapshot or get_diff.

  • get_diff

    Compare page content between two timestamps to see exactly what changed. Use get_change_history to find valid timestamps. Output is capped at … characters by default — raise max_chars if you need more.

  • get_notifications

    Get the current notification settings (email, Telegram, web push, etc.).

  • get_rss_settings

    Get the current RSS feed settings including whether feeds are enabled and the feed token.

  • get_snapshot

    Get the page content captured at a specific timestamp. Use get_change_history first to find valid timestamps. Content is capped at … characters by default — raise max_chars if you need more.

  • get_watch

    Get full details of a specific watch including its configuration, last check status, and change history summary.

  • list_watches

    List all monitored websites. Returns an object keyed by watch UUID, each with its URL, title, status, and last checked/changed timestamps.

  • revoke_rss_token

    Revoke the RSS feed token, disabling all RSS feed access immediately.

  • search_watches

    Search across all watches by URL, title, or content. Returns matching watches.

  • trigger_recheck

    Force an immediate recheck of every watch. Useful when you need fresh data now rather than waiting for the next scheduled check. Manual rechecks are capped per day by plan.

  • update_watchwrite action

    Update a watch's configuration. Use this to pause/resume, change check interval, update title, or modify notification settings.

  • web_search

    Search the web via DuckDuckGo HTML and return a list of result URLs with titles and snippets. Use this BEFORE fetch_url when the user asks you to 'search', 'find', 'look up', or otherwise discover content — instead of guessing google.com (which always blocks). Pipeline: web_search(query) -> pick relevant results -> fetch_url(result.url, fetch_backend: 'html_requests') on each. Returns up to 20 res

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

1 low
  • Code scan2 source files scanned25/25
  • Live reliabilityno gateway calls yet and no remote to proben/a
  • Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 55/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

Runs npx -y @site-spy/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add site-spy -- npx -y @site-spy/mcp-server
Add to Cursor

Site Spy: common questions

Is Site Spy MCP server safe?
With care: it is graded C, so read the findings first (55/100). Read the Site Spy safety report
How do I install Site Spy?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Site Spy need an API key?
Yes. The registry entry asks for SITE_SPY_API_KEY.
Is Site Spy maintained?
The latest release is v0.3.0.

More from vkuprin