Jarroba Tools · Test audit

Official registry Security

Audits tests instead of writing them: what each one really asserts. 4 tools, local.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @jarroba/mcp-tests
Claude Code
claude mcp add jarroba-tools-test-audit -e 'JARROBA_MCP_DOMAINS=<JARROBA_MCP_DOMAINS>' -- npx -y @jarroba/mcp-tests@0.3.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "jarroba-tools-test-audit": {
            "command": "npx",
            "args": [
                "-y",
                "@jarroba/mcp-tests@0.3.0"
            ],
            "env": {
                "JARROBA_MCP_DOMAINS": "<JARROBA_MCP_DOMAINS>"
            }
        }
    }
}

Environment variables

  • JARROBA_MCP_DOMAINS Which tool domains to publish, comma-separated. Defaults to what this package is for. Valid: core, calc, diagram, kg, db, ai, logs, queue, project, tests, api, chip, chem, access, archsim, security, experiments, payroll. Fewer domains means less of your context window spent on tool definitions.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Jarroba Tools — MCP servers

Source of the @jarroba/mcp family of MCP servers: deterministic tools for AI agents that run on your machine and upload nothing. The packages and their documentation are in mcp/. Minimal examples of an MCP server with the SDK v2, in TypeScript and Python, are in mcp/examples/.

The tools reuse the engines of jarroba.com/tools: they live under src/app/, with the same layout as in the web app, so that the code here is the code that runs there.

This repository is a read-only mirror, generated from the private repository of Jarroba Tools at each release. Issues are welcome; pull requests cannot be merged here.

Build and test

npm install            # engines' dependencies (root)
cd mcp && npm install
npm run build && npm test && npm run test:paquete

Security: see SECURITY.md — report vulnerabilities privately, not in a public issue.

Changes per version: CHANGELOG.md. How to report bugs and propose tools: CONTRIBUTING.md.

License: MIT (see LICENSE). Third-party notices ship in each package's dist/.

Frequently asked questions

What is Jarroba Tools · Test audit?

Audits tests instead of writing them: what each one really asserts. 4 tools, local.

How do I install Jarroba Tools · Test audit?

It runs on your machine. In Claude Code: claude mcp add jarroba-tools-test-audit -e 'JARROBA_MCP_DOMAINS=<JARROBA_MCP_DOMAINS>' -- npx -y @jarroba/mcp-tests@0.3.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Jarroba Tools · Test audit need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Jarroba Tools · Test audit open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Jarroba Tools · Test audit?

It is published by Invarato. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.