MCP server watchdog
An MCP server can change what its tools say or do without any change in your code. The watchdog checks the remote MCP servers your agent uses once a day and raises an advisory signal when something changes.
What it checks
Once a day Bastyn asks each watched server for its tool list, the same way any MCP client does, and compares it with what it saw last time. It raises a signal when:
- a tool is added or removed,
- a tool’s description changes,
- a tool’s input schema changes, or
- the server reports a new version.
The signal appears on the project’s trust report. Signals are advisory: they do not change the score or the certificate. The first time Bastyn sees a server it only records what it found, so a new server never raises a signal on its own.
Which servers are watched
Remote MCP servers that Bastyn finds when it scans your repository (for example in .mcp.json) are added to the project’s watch list automatically. You can also add one yourself by its address.
An address can be watched when it is a public https address with no password, key or query string in it. Servers that run as a local command are not watched. Anything Bastyn found but could not watch is listed under “Not watched”, with the reason.
- A project can watch up to 10 servers.
- If you remove a server from the list, Bastyn does not add it back.
- Bastyn never removes a server from the list on its own, even if it disappears from your repository.
- You can turn automatic watching off for a project on the watch list.