World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Records MCP tool calls and itemises the token cost each server adds to your context.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install mcpwatch. Follow https://mcp.popnx.com/i/sreelal727-mcpwatch.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server mcpwatch for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "mcpwatch": { "command": "npx", "args": [ "-y", "@sreelal727/mcpwatch" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the mcpwatch tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"mcpwatch": {
"command": "npx",
"args": [
"-y",
"@sreelal727/mcpwatch"
]
}
}
}Use mcpwatch and tell me what you can do for me, then show me one thing✓ If Claude says it is using mcpwatch or shows a mcpwatch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect mcpwatch yet
mcpwatch runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect mcpwatch
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server mcpwatch for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user mcpwatch -- npx -y @sreelal727/mcpwatch 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the mcpwatch tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user mcpwatch -- npx -y @sreelal727/mcpwatchYou should see mcpwatch listed as connected
Use mcpwatch and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using mcpwatch or shows a mcpwatch tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server mcpwatch for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "mcpwatch": { "command": "npx", "args": [ "-y", "@sreelal727/mcpwatch" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the mcpwatch tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use mcpwatch and tell me what you can do for me, then show me one thing✓ If Cursor says it is using mcpwatch or shows a mcpwatch tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server mcpwatch for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "mcpwatch": { "type": "stdio", "command": "npx", "args": [ "-y", "@sreelal727/mcpwatch" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the mcpwatch tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use mcpwatch and tell me what you can do for me, then show me one thing✓ If VS Code says it is using mcpwatch or shows a mcpwatch tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user mcpwatch -- npx -y @sreelal727/mcpwatchClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"mcpwatch": {
"command": "npx",
"args": [
"-y",
"@sreelal727/mcpwatch"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"mcpwatch": {
"command": "npx",
"args": [
"-y",
"@sreelal727/mcpwatch"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"mcpwatch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sreelal727/mcpwatch"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @sreelal727/mcpwatchBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account Sreelal727, which owns the repo
Code last changed 3 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @sreelal727/mcpwatch@0.4.1
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/sreelal727-mcpwatch)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 months ago, and the latest version (0.4.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one mcpwatch | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Every MCP server you've installed is charging you tokens on every single session. See the bill — then cut it.
mcpwatch records the real traffic between your coding agent (Claude Code, Codex, Cursor, Claude Desktop) and your MCP servers, then itemises what that setup actually costs you in context — and tells you exactly what to delete.
*One command. All local. Zero config. No account, ever.*
Here's what nobody tells you when you install an MCP server: its tool definitions get injected into your agent's context at the start of every single session, whether you use that server or not. A big vendor integration with 50 tools can cost you 15,000+ tokens before you type a word. You pay it again on the next session, and the next.
On top of that you're paying for tool responses that return 200 kB when you needed one row, calls that fail and get retried, and agents re-fetching things they already had.
None of it shows up anywhere. mcpwatch records the actual bytes on the wire and turns them into an itemised bill.
No setup, no restart, no waiting. This starts each MCP server you already have configured, asks it for its tool list the way your client does, measures it, and shuts it down:
npx @sreelal727/mcpwatch audit
Every new session pays ~9,262 tokens ($0.05) to load these tool definitions,
before you type a word:
github 8,825 tokens 52 tools 95% Cursor filesystem 437 tokens 6 tools 5% Cursor 9,262 tokens every session
At 10 sessions a day that is ~2,778,600 tokens a month ($13.89 at $5/M) spent before any work happens.
"github" alone is 95% of that. If you do not use it in every project, moving it to the projects that need it is the single biggest win available to you.
That's the fixed cost, and it's knowable without recording anything.
Which of those tools you *call* does need real traffic. Instrument once, work normally for a day, and ask:
npx @sreelal727/mcpwatch init # then restart your client
npx @sreelal727/mcpwatch cost # a day later
Your MCP setup costs ~12,486 tokens per session before you type a word ($0.06 at $5/M tokens).
PER-SESSION TAX — tool definitions loaded into every new session: github 10,762 tokens 46 tools, none used ← never called filesystem 780 tokens 8 tools, 2 used postgres 944 tokens 9 tools, 1 used 12,486 tokens, every session
AT YOUR ACTUAL PACE — 34.9 server startups/day over 11.3 days: ~4,362,755 tokens/month ($21.81) on tool definitions alone, before any work happens ~4,939,089 tokens/month ($24.70) all in
BIGGEST SAVINGS — ~1,510,287 tokens ($7.55) of the above bought you nothing:
Look at those first two numbers together: $21.81 of that $24.70 monthly bill is tool definitions — the cost of merely having servers configured, before your agent does a single useful thing. And the largest one has never been called.
That's the point of the whole tool. Not "here is a dashboard, go find something," but *delete this one line from your config and stop paying 10,762 tokens every session for a server you have never once used.*
The projection uses your observed startup rate from your recording — it isn't a guess, and it doesn't appear at all until there's enough history to be honest about.
(Install once with npm i -g @sreelal727/mcpwatch and every command is just mcpwatch ….)
init also registers mcpwatch as an MCP server, so your agent gets these tools with no extra setup:
| Tool | The question it answers |
|---|---|
token_costs | "What is my MCP setup costing me, and what should I remove?" |
recent_failures | "What just broke, with what arguments, and what did the server say?" |
server_health | "Is that server crashing, slow, hanging, or corrupting the protocol?" |
find_calls | "Has this tool ever worked? What arguments did I use last time?" |
get_call | "Show me the exact request and response JSON for call #412." |
So you can just ask, in the client you already use:
You: my context keeps filling up, what's eating it?
Agent: *(calls
token_costs)* Yourgithubserver loads 46 tool definitions —
10,762 tokens — into every session, and you haven't called it once in the last 30 days.
That's about 1.4M tokens over the window. Your filesystem server also re-read identical
files 132 times. Want me to take github out of your config?
The descriptions are written as trigger conditions, so the agent reaches for them on its own — recent_failures after a failed tool call, token_costs when you mention context or cost — instead of waiting to be told they exist.
The same recording answers the reliability questions, in one command:
$ mcpwatch doctor
2 error(s) in 19 MCP calls across 3 server(s) in the last 24h.
! web-fetch 5 calls, no errors, avg 152ms last seen 32s ago 1 non-protocol stdout line (this server logs to stdout, which corrupts MCP) ✗ database 7 calls, 2 errors (29%), avg 227ms last seen 34s ago high error rate slowest: run_query at 1.3s ✓ filesystem 7 calls, no errors, avg 54ms last seen 36s ago
[#14] 2s ago database/does_not_exist tool_error (2ms) error: MCP error -32602: Tool does_not_exist not found session fd14d19f · full payloads: get_call(14)
mcpwatch tail streams calls live, one line each. Everything takes --json, so agents with only shell access (Codex in a VS Code terminal, hooks, CI) can read it too. And mcpwatch ui opens a local dashboard on 127.0.0.1 when you'd rather look yourself.
mcpwatch audit prices your configured servers with no instrumentation, no client restart, and no waiting for traffic.mcpwatch cost prices every server's per-session tax, projects it forward from your own usage, and ranks what to remove: unused servers, bloated tool lists, oversized responses, repeated calls, failed calls.token_costs, recent_failures, server_health, find_calls, get_call as MCP tools, plus --json on everything for agents that only have a shell. Your agent stops guessing about its own tool calls.ok / rpc_error / tool_error), including in-band tool failures that clients often swallow silently.--no-redact to disable, MCPWATCH_REDACT_EXTRA to add patterns.mcpwatch export produces one self-contained HTML file: a shareable, scriptless bug report of exactly what happened.mcpwatch http is a recording reverse proxy for Streamable HTTP servers (SSE responses included).mcpwatch gc for retention; delete ~/.mcpwatch and it's gone. No SaaS, no accounts, no telemetry, ever.your agent ──stdio──▶ mcpwatch run ──stdio──▶ your MCP server
▲ │ │ └── tee ──▶ SQLite (~/.mcpwatch) │ │ └──── mcpwatch mcp ◀─────────────────────┤ the agent reads its own history │ mcpwatch ui / doctor / tail ◀──────┘ you read it, when you want to
mcpwatch init rewrites each stdio server entry in your client's config to route through mcpwatch run. The proxy pipes bytes through untouched and parses a *copy* of the stream — capture is wired independently of passthrough, so even if recording fails, your agent keeps working. Passthrough is sacred is design principle #1, enforced in code and covered by end-to-end tests that drive a real MCP client through the proxy.
init also adds mcpwatch itself to your client as an MCP server, which closes the loop: the recorder becomes a tool the agent can call. It is never wrapped by its own proxy — otherwise every question the agent asked about the traffic would become more traffic.
| mcpwatch | MCP Inspector | mcpsnoop | SaaS agent observability | |
|---|---|---|---|---|
| Tells you what your setup costs in tokens | ✅ cost | ❌ | ❌ | partial (spend, not per-server tax) |
| Your agent can query the recording | ✅ MCP tools | ❌ | ❌ | ❌ |
| Real sessions from your actual client | ✅ | ❌ manual dev tool | ✅ | ✅ |
| Headless / terminal-only workflow | ✅ doctor, tail | ❌ | ✅ | ❌ |
| Web dashboard | ✅ | ✅ | ❌ terminal TUI | ✅ |
| One-command whole-client setup | ✅ init | ❌ | ❌ per-server | ❌ SDK/agent changes |
| Live tail | ✅ | ❌ | ✅ | ✅ |
| Self-contained HTML session export | ✅ | ❌ | ❌ | ❌ |
| 100% local, no account | ✅ | ✅ | ✅ | ❌ |
| Policy guardrails | 🔜 v1.0 | ❌ | ❌ | varies |
(All good tools — this is about which job each one is for. Inspector is great for poking a server you're developing; mcpsnoop is a solid terminal viewer; SaaS platforms add fleet features on their infrastructure.)
| Command | What it does |
|---|---|
mcpwatch audit [--json] | Measure the per-session cost of your configured servers right now — no setup |
mcpwatch init [--dry-run] | Instrument your clients and give your agent the mcpwatch tools (backups + reversible) |
mcpwatch cost [--since 30d] [--rate N] [--json] | Itemised token bill: per-session tax, monthly projection, ranked savings |
mcpwatch doctor [--json] | One-shot health report: erroring, crashing, hanging, slow, or protocol-corrupting servers |
mcpwatch tail [--json] | Follow calls live in the terminal, one line each |
mcpwatch mcp | Run mcpwatch as an MCP server (your client starts this; you normally won't) |
mcpwatch connect | Print copy-paste setup for Claude Code / Codex / Cursor |
mcpwatch unwrap | Restore original configs |
mcpwatch status | Show what's instrumented |
mcpwatch ui [--port 4680] | Local dashboard |
mcpwatch run --name X -- | Wrap one stdio server manually |
| mcpwatch http [--port 4681] | Recording reverse proxy for a