Site Spy

io.github.vkuprinPublished by GitHub account vkuprinv0.3.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyWeb Search & Scraping

Server details

Identifier: io.github.vkuprin/site-spy
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account vkuprin for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.vkuprin%2Fsite-spy.svg)](https://sourceweft.com/mcp/io.github.vkuprin%2Fsite-spy?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Site Spy's local MCP server lets an AI assistant monitor websites for changes through the Site Spy service.

What you can do: Connect an assistant to a Site Spy account so it can work with website change monitoring from the chat session. The manifest lists no individual tools, so the exact operations are not documented here; the server is described only as letting AI agents monitor websites for changes.
When to use it: Worth considering if you already use Site Spy to watch web pages and want an assistant to set up or check that monitoring without leaving the conversation.
Requirements: Runs as a local process on the user's machine via the npm package, so a Node.js runtime is needed. Requires a Site Spy account and an API key supplied in the SITE_SPY_API_KEY environment variable, obtained from the service's Settings > API page. Desktop only; no web executable.

Before you install

The server needs a Site Spy API key, which is a credential for your account; keep it out of shared configuration and logs. Monitoring activity and the pages you track are handled by the Site Spy service, a third party. The manifest lists no tools, so review what the server can change in your account before relying on it.

Installation

In SourceWeft

Open Site Spy in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.1LatestSep 23, 2026
v0.3.0Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.