# wachete [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://www.wachete.com  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wachete

## Description
Create, read and monitor Wachete website-change wachets for a signed-in user.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "wachete": {
    "command": "npx",
    "args": ["-y","wachete"]
  }
}
```

## Documentation

## What wachete MCP server does

The wachete MCP server works with Wachete website-change wachets for a signed-in user. Its documented scope covers three operations: creating wachets, reading wachets, and monitoring wachets. A wachet represents a Wachete website-change monitoring item, so the server is relevant when an agent needs to manage those items rather than simply retrieve a webpage.

This places the wachete MCP server in the 📊 Monitoring category. It can fit workflows where website-change checks are created or reviewed through an authenticated Wachete account. The available description does not identify particular website types, comparison modes, notification channels, schedules, or result formats.

## Tools and capabilities

The documented capabilities are:

- Create Wachete website-change wachets.
- Read Wachete website-change wachets.
- Monitor Wachete website-change wachets.

These capabilities are stated at the operation level only. The source material does not provide tool names, argument schemas, return fields, filtering options, update or delete operations, or controls for configuring how Wachete detects changes.

## Setup and configuration

Use of the wachete MCP server requires a signed-in Wachete user. The provided material does not explain how authentication is supplied, whether an API key or session is used, how the MCP process is started, or which client configuration is required. It also does not list environment variables or installation commands.

Before adopting it, verify the authentication procedure and confirm that the intended MCP client can pass the required signed-in Wachete context. The available information supports the account requirement, but not a specific setup recipe.

## Limitations and notes

The wachete MCP server should be evaluated as an account-based interface for Wachete website-change wachets. No claim can be made from the available description about browser automation, arbitrary web scraping, alert delivery, historical change data, or monitoring frequency. Those functions may depend on Wachete itself, but they are not documented here as server capabilities.

The source does not identify supported MCP clients, licensing terms, server version, or compatibility details. It also does not state whether the server can modify an existing wachet beyond the listed create, read, and monitor operations. For implementation planning, treat the documented scope as limited to managing website-change wachets for a signed-in user and consult the Wachete source for operational details.

_Full upstream README: https://allmcps.com/mcp/wachete/readme_