@site-spy/mcp-server

Name: @site-spy/mcp-server
Author: Unknown

MCPcommunity

v0.3.0UnknownISCUpdated 3d agonpm

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

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

232Downloads/wk

3d agoLast update

Needs 1 credential before it runs

SITE_SPY_API_KEYAPI keyrequired
Site Spy API key from Settings > API

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

AuthorUnknown

LicenseISC

Version0.3.0

Sourcenpm+mcp-registry

npm@site-spy/mcp-server

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface19 tools · 1 privileged

Security scan✓ Cleanv0.3.0 · todayHow well does this scan work?

EvalsNone

IndexedSep 7, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

19 tools · 1 privileged

Statically extracted from the published packagev0.3.0 · 2h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

authenticateNo description published

This tool published no description. Forge does not invent one.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

get_snapshotNo description published

This tool published no description. Forge does not invent one.

get_diffNo description published

This tool published no description. Forge does not invent one.

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

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

No input schema was published for this tool.

trigger_recheckForce 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.

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.

No input schema was published for this tool.

fetch_urlNo description published

This tool published no description. Forge does not invent one.

web_searchSearch 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 re…

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 re…

No input schema was published for this tool.

get_ai_summaryGet 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 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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

generate_rss_tokenGenerate 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.

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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

15 of 19 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords

mcpmodel-context-protocolsite-spywebsite-monitoringai-agents

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-07 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.7
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

@site-spy/mcp-server

Tools

Tools exposed

Dependency tree

Declared but not resolved

Topics

Related in monitoring & logging