Watchdog
NPM · WATCHDOG-MCP · SCANNED OCT 4
Who can change a Solana program or EVM contract, dependency advisories, scans. Paid per call (x402).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 232 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1091 tokens (~136/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 41% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Watchdog MCP server?
Watchdog runs locally as an npm package, launched with npx -y watchdog-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · watchdog-mcp
claude mcp add oxtof-watchdog-mcp -- npx -y watchdog-mcp
{
"mcpServers": {
"oxtof-watchdog-mcp": {
"command": "npx",
"args": [
"-y",
"watchdog-mcp"
]
}
}
} {
"servers": {
"oxtof-watchdog-mcp": {
"command": "npx",
"args": [
"-y",
"watchdog-mcp"
]
}
}
} codex mcp add oxtof-watchdog-mcp -- npx -y watchdog-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"oxtof-watchdog-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"watchdog-mcp"
],
"enabled": true
}
}
} openclaw mcp add oxtof-watchdog-mcp --command npx --arg -y --arg watchdog-mcp
mcp_servers:
oxtof-watchdog-mcp:
command: "npx"
args: ["-y", "watchdog-mcp"] {
"McpServers": {
"oxtof-watchdog-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"watchdog-mcp"
]
}
}
} assistant mcp add oxtof-watchdog-mcp -t stdio -c npx -a -y watchdog-mcp
{
"mcpServers": {
"oxtof-watchdog-mcp": {
"command": "npx",
"args": [
"-y",
"watchdog-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Oct 26 53
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 9 Oct 2026 · Analysed npm/watchdog-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 137 packages
| Packages resolved | 137 |
|---|---|
| Stale | 31 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dependency_advisories Known advisories for pinned dependencies ~192
Use before adding or upgrading a dependency, or to triage a lockfile. Give lockfile_path (a Cargo.lock, package-lock.json or yarn.lock on disk, read locally) or the lockfile text, or a list of up to 100 packages. Rust crates go to Solana Watchdog (RustSec/OSV), npm packages to EVM Watchdog (GitHub/OSV). Only registry packages are checked; workspace and git dependencies are skipped. Costs $0.01 USDC per call (Solana for crates, Base for npm). Settled only if the answer exists.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Required with lockfile text or packages |
| lockfile | string | – | Lockfile text, if not on disk |
| lockfile_path | string | – | Path to Cargo.lock, package-lock.json or yarn.lock |
| packages | array | – | Exact pinned versions |
No output schema declared.
No examples provided.
evm_contract_control Who can change this EVM contract? ~168
Use before approving a token, depositing into, or signing for a contract on Base or Robinhood Chain. Detects the proxy kind (EIP-1967 transparent, UUPS, beacon, legacy zeppelinos, EIP-1167 clone, diamond, EIP-7702), the live implementation, and follows the upgrade controller and owner to the end: one key, a Safe (threshold of owners), a timelock (delay). Sourcify verification for the address and the implementation. Costs $0.05 USDC on Base, paid over x402 from WATCHDOG_EVM_PRIVATE_KEY. An address with no code is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address, 0x… |
| chain | string | – | Chain the contract lives on |
No output schema declared.
No examples provided.
get_scan_report Status and report of a paid scan ~53
Free. Returns the status of a scan started with scan_repo and, once done, its JSON report.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| ecosystem | string | yes | – |
| jobId | string | yes | – |
No output schema declared.
No examples provided.
scan_repo Security scan of a public GitHub repo ~154
Use before a release or an integration: scans a public GitHub repo for advisories on its exact pinned dependencies (split into what ships on-chain and what is tooling), build hygiene, and code leads for known bug classes with file:line. ecosystem 'solana' for Rust/Anchor programs, 'evm' for Solidity (Foundry/Hardhat). Costs $0.50 USDC (Solana or Base). Waits up to wait_seconds for the report; otherwise returns jobId and accessToken for get_scan_report. A scan, not an audit.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | – |
| repo | string | yes | https://github.com/OWNER/REPO |
| wait_seconds | integer | – | – |
No output schema declared.
No examples provided.
solana_program_authority Who can change this Solana program? ~141
Use before signing a transaction for, or depositing into, a Solana mainnet program. Answers who can replace its code: immutable, a single key, a Squads v4 multisig (threshold, members and time lock read on-chain, the vault re-derived as proof), Squads v3 or SPL Governance; plus the last deploy date, OtterSec verified build, embedded security.txt and severity-ranked flags. Costs $0.05 USDC on Solana, paid over x402 from WATCHDOG_SOLANA_PRIVATE_KEY. An address that holds no program is not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| programId | string | yes | Program address, base58 |
No output schema declared.
No examples provided.
watch_create Get alerted when a program, contract or lockfile changes ~198
Use to be told, for 30 days, when something you rely on changes: a Solana program (programId: authority, multisig rules, code upgrade, lost verification), an EVM contract (address + chain: new implementation, controller or owner, weaker Safe or timelock), or a lockfile (lockfile_path: any new advisory). Hourly checks; each change is POSTed to your https webhook, signed with x-watchdog-signature: sha256=HMAC(secret, body). Costs $0.90 USDC for the period (Solana for programs and Cargo.lock, Base for contracts and npm lockfiles). Returns watchId, secret and accessToken, each shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| chain | string | – | – |
| lockfile_path | string | – | – |
| programId | string | – | – |
| webhook | string | yes | Public https URL that receives the signed alerts |
No output schema declared.
No examples provided.
watch_status Events of a watch ~64
Free. Lists what a watch has seen (also kept when the webhook was down), or cancels it with cancel: true.
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | – |
| cancel | boolean | – | – |
| ecosystem | string | yes | – |
| watchId | string | yes | – |
No output schema declared.
No examples provided.
watchdog_wallet Payment setup and spend ~43
Free. Shows which payment wallets this server is configured with (addresses only), the per-call cap, the session budget, what was spent, and the price of each tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Watchdog MCP server?
Watchdog is an MCP server listed in the public MCP registry as io.github.OxToF/watchdog-mcp. Who can change a Solana program or EVM contract, dependency advisories, scans. Paid per call (x402). This page covers its npm package (watchdog-mcp).
Is the Watchdog MCP server safe to use?
Watchdog scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Watchdog MCP server expose?
Watchdog exposes 8 tools: solana_program_authority, evm_contract_control, dependency_advisories, scan_repo, get_scan_report, and 3 more. Their descriptions and schemas cost roughly 1,013 tokens of context every time the server is loaded.
Is the Watchdog MCP server still maintained?
Watchdog is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Watchdog MCP server under?
Watchdog declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.