Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.
PopNx MCPMCP servers for people who use AI · explained in plain words

Toolars

by aixtralversion 0.1.1i★ 0iRuns on your computer
Registry nameio.github.aixtral/toolars

How to install

Overview

Description from the maker (original English)

Local-first dev utilities: hash, base64, JWT, UUID, cron, URL codec. No network or telemetry.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

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

  1. Install Node.js

    One time only; it works for every server that needs Node.js

    Open the Node.js download page ↗

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "toolars": {
          "command": "npx",
          "args": [
            "-y",
            "@toolars/cli",
            "-y",
            "-p",
            "@toolars/cli",
            "toolars-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    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

What you can do instead

A · Use an app that can connect Toolars

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

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)

  1. Install Node.js

    One time only; it works for every server that needs Node.js

    Open the Node.js download page ↗

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add toolars -- npx -y @toolars/cli -y -p @toolars/cli toolars-mcp
  4. Type /mcp in Claude Code

    You should see Toolars listed as connected

  5. Try it

    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)

  1. Install Node.js

    One time only; it works for every server that needs Node.js

    Open the Node.js download page ↗

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    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)

  1. Install Node.js

    One time only; it works for every server that needs Node.js

    Open the Node.js download page ↗

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    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

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Toolars💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add toolars -- npx -y @toolars/cli -y -p @toolars/cli toolars-mcp

Claude 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.

At a glance

Downloads per weeki
39/wk
Licencei
No licence stated
Connection
Runs on your computer
Latest versioni
0.1.1
Categoryi
Other
Published to registryi
Sep 26, 2026
Code last changedi
Oct 19, 2026
Maker
aixtral
Packages
npm: @toolars/cli
Registry status
Active

Which apps can use it

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

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account aixtral, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 23 days ago

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Discussion

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.

Sign in with Google to post

User reviews

No reviews yet

Sign in with Google to write a review

Compared with others in Otheri

  • More stars than 0% of the other 19139 servers in this category
  • Published to the registry more recently than 50% of the other 19139 servers in this category
  • Basic checks equal to or better than 100% of the other 19139 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Toolars safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed 23 days ago, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, Claude Flow, Tldraw

Alternatives

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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.

by koala73Widely used★ 90.5KUpdated 6 days ago

Runs in the cloud✓ worldmonitor.app

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

by ruvnetWidely used↓ 13.5K/wk★ 81.4KUpdated 14 months ago

Runs on your computer

Tldraw

Draw and visually collaborate with your agents on tldraw's canvas.

by tldrawWidely used★ 51.4KUpdated 8 months ago

Runs in the cloud

README from the maker

Open the README

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.

Toolars open-source distribution

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.

Continuous verification

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.

What is published

PathWhat 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.

What is deliberately _not_ published

This is an open-core distribution, not the whole product. Not included:

  • the website application (routing, SEO layer, catalog, editorial content, the 13 localized content sets);
  • the tool implementations and Web Workers that the website ships, in source form — with one deliberate exception: 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;
  • runtime assets (WASM engines, OCR language packs, fonts, PDF.js);
  • internal engineering, product, and audit documentation;
  • any deployment configuration, credentials, or analytics configuration.

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.

Verifying the local-processing claim yourself

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.

Running the CLI and MCP server

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.

Reporting a problem with this code

Open an issue on the public repository. Security reports follow the process in that repository's SECURITY.md.

License

MIT — see LICENSE. Scope and third-party components: THIRD-PARTY.md and evidence-harness/fixtures/PROVENANCE.md.