World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Description from the maker (original English)
Local-first dev utilities: hash, base64, JWT, UUID, cron, URL codec. No network or telemetry.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Passed 2/2 checks · Runs on your computer
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
One time only; it works for every server that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"toolars": {
"command": "npx",
"args": [
"-y",
"@toolars/cli",
"-y",
"-p",
"@toolars/cli",
"toolars-mcp"
]
}
}
}Use Toolars and tell me what you can do for me, then show me one thing✓ If Claude says it is using Toolars or shows a Toolars 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 Toolars yet
Toolars runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Toolars
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)
One time only; it works for every server that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add toolars -- npx -y @toolars/cli -y -p @toolars/cli toolars-mcpYou should see Toolars listed as connected
Use Toolars and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Toolars or shows a Toolars 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)
One time only; it works for every server that needs Node.js
Use Toolars and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Toolars or shows a Toolars 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)
One time only; it works for every server that needs Node.js
Use Toolars and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Toolars or shows a Toolars 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
Claude Code
claude mcp add toolars -- npx -y @toolars/cli -y -p @toolars/cli toolars-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"toolars": {
"command": "npx",
"args": [
"-y",
"@toolars/cli",
"-y",
"-p",
"@toolars/cli",
"toolars-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"toolars": {
"command": "npx",
"args": [
"-y",
"@toolars/cli",
"-y",
"-p",
"@toolars/cli",
"toolars-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"toolars": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@toolars/cli",
"-y",
"-p",
"@toolars/cli",
"toolars-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based 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 11, 2026
The registry name was verified with the GitHub account aixtral, which owns the repo
Code last changed 23 days ago
We have not read this repo from GitHub yet
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
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 2 of 2 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 23 days ago, and the latest version (0.1.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, Claude Flow, Tldraw
Servers in the same category from other makers, sorted 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. 102 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
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.
Use Toolars online for PDF, image, text, and developer tools directly in your browser.
This directory is the source of truth for the code Toolars publishes publicly. It is assembled into a distributable tree by scripts/export-open-source.mjs in the private repository; nothing here is built or bundled into the website.
Every push and every day at 03:17 UTC, the Privacy proof workflow rebuilds both packages from this tree alone, re-runs their test vectors, and re-captures the privacy-proof receipt against the live site. The badge is green only when the latest receipt's outcome is verified.
A failed run is not automatically a privacy finding. The harness distinguishes two outcomes: violation means a measured request crossed the local-processing boundary (the workflow fails on the first attempt, without retrying); inconclusive means the run could not be completed — usually a network problem between the runner and the site — and says nothing about the site in either direction. Inconclusive runs are retried; a persistent one fails the job with an explicit notice. Read the run log before reading anything into a red badge.
| Path | What it is |
|---|---|
evidence-harness/ | A runnable harness that drives the public website in headless Chromium and records every network request, including dedicated Web Worker fetches. It is the tool behind the claim that files never leave the browser. |
packages/cli/ | @toolars/cli — a local stdio CLI and MCP server (hash, base64, JWT decode, UUID/ULID, timestamp, cron, URL encode/decode), shipped as a prebuilt bundle in dist/. |
packages/local-tools/ | @toolars/local-tools — a smaller local stdio CLI and MCP server (JSON formatting, SHA-256), shipped as runnable source. |
All of it is MIT-licensed (see LICENSE). THIRD-PARTY.md states the exact scope and lists third-party components.
This is an open-core distribution, not the whole product. Not included:
packages/*/vendor/ carries the site runner cores these two packages import (15 files for the CLI, 2 for local-tools), because without them the packages could not be rebuilt or re-tested here. The packages/cli bundle also inlines compiled copies of the same cores, since it is the artifact prepared for a future @toolars/cli npm release. Both are covered by this repository's MIT license;That boundary is the point: the harness verifies the deployed site, so independent verification does not require the site's source. See evidence-harness/README.md for exactly what the harness does and does not prove.
cd evidence-harness
npm install npx playwright install chromium npm run verify -- --base-url https://toolars.com
The run writes privacy-proof-receipt.json and exits non-zero if an unexpected request leaves the site's origin, if any request carries the canary marker, or if any request uploads data. Disclosed shell requests are counted separately. A missing or changing release identity also prevents a verified result.
Both packages are published on npm under the @toolars scope: npm install -g @toolars/cli gives you toolars + toolars-mcp, and npm install -g @toolars/local-tools gives you toolars-local + toolars-local-mcp. The bins do not collide.
cd packages/cli
node dist/cli.mjs hash --sha256 "hello" node dist/mcp.mjs # stdio MCP server
dist/ is committed and copied from the private build output, so running it needs no install and no build. Review that bundle if you want to see the code you would actually execute: it is unminified, and its section comments name the source file each part came from.
You can also rebuild it here and re-run the same test vectors the private workspace runs. Each package carries the exact site core closure it depends on under vendor/, so neither needs the private repository:
cd packages/cli
npm install # esbuild + vitest, declared as devDependencies npm run build # writes dist/ from src/ plus vendor/ npm test # shared digest vectors and CLI/MCP boundary tests
cd packages/local-tools
npm install # esbuild + prettier node build.mjs # regenerates src/json-core.mjs from vendor/ node --test test/*.test.mjs
vendor/ holds copies of the site runner cores these packages import, produced by the exporter and byte-identical to the private ones. They are published as source on purpose: a reader who can rebuild the package and re-run its vectors can check the results instead of trusting them. Rebuilding in the exported layout changes source-path comments in the CLI bundles and local-tools generated core. Compare executable content separately from these comments; a rebuild is not claimed to reproduce the original manifest byte for byte.
Both packages are local-stdio only. Their inputs and results enter the calling client's context and may reach that client's model provider; the website's privacy promise does not extend to the client. Each package's README states this scope.
Open an issue on the public repository. Security reports follow the process in that repository's SECURITY.md.
MIT — see LICENSE. Scope and third-party components: THIRD-PARTY.md and evidence-harness/fixtures/PROVENANCE.md.