MCP.Market

CARBON MCP server

by jarbon·io.github.jarbon/carbon·v1.32.22-free.17·2 stars
No reviews yet

AI testing harness with Jay: risk-based checks, bug investigation, and local evidence reports.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

2 stars211 downloads/wk

Reviews

Write one

Nobody has reviewed CARBON yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

CARBON tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it

1 medium
  • Code scan62 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    background/engine.test.mjs: …writeFileSync(path.join(root,'app.js'),'eval(oldInput);\nconst unchanged=1;\n');git([…
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How CARBON compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
GitHub stars
2
more than 75% of 28,688 servers
Downloads a week
211
more than 76% of 12,191 servers with a package

Install CARBON in Claude Code, Cursor or VS Code

Runs npx -y @testers-ai/carbon-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add carbon -- npx -y @testers-ai/carbon-mcp
Add to Cursor

What the publisher says

From the CARBON repository's README, as published. We do not edit it. Read it on GitHub

Testers.ai CARBON Test Harness

Your agent's plan. Your local workspace.

Use the model access you already have. In Claude Code, Codex, and other coding agents, CARBON's default testing workflows use the host's configured model access. When the host uses an eligible subscription, CARBON uses that allowance—no separate CARBON model API key is required. If the host uses API credentials or a company LLM proxy, that billing and data policy apply instead. Plan limits and extra-usage charges still apply; CARBON Pro licensing is separate.

Local execution and local reports—not a promise that no data leaves your machine. For local runs, project files, test evidence, and reports are stored in your local workspace. Your coding agent can send selected code, screenshots, prompts, and other context to its configured model provider. Local CARBON is not automatically offline or air-gapped. Cloud runs, external integrations, and optional direct-model checks have separate data flows and may have separate costs. Command-usage analytics vary by edition; review that edition's privacy policy and settings.

To confirm your billing route, check /status in Claude Code or codex login status in Codex. A configured API key can select API billing instead of subscription usage. Standalone MCP clients must supply their own model access and execution tools; installing an MCP server does not include a model subscription.

Light edition. AI software testing and quality assurance inside Claude.

AI testing inside your coding agent. Built by testers.ai.

CARBON gives your coding agent risk-based testing instructions and a local evidence runtime. The agent inspects your authorized project, runs checks using its available browser, terminal or API tools, and records findings in a live report. CARBON's MCP server does not independently run the investigation or manufacture results.

New in 1.32.22-free.7

Four compact report views help you move from a decision to its evidence:

  • Release Brief: findings, next actions and outcomes for the selected checks.
  • Evidence Lens: page screenshots linked to checks, reproduction and fixes.
  • Journey Atlas: recorded paths and step outcomes, without invented connections.
  • Live Investigation: the current check, its purpose and recent activity.

Zoom screenshots, keep the full record one click away, and export portable HTML/JSON. Live reports retain their last good snapshot and quietly reconnect after interruption. Unknown and deferred checks remain distinct from passing checks.

Role-based AI testing team

Jay, the AI test manager, now introduces the assessment and appears in reports. Specialist profiles use role-based names and new light/dark icon identities rather than human names and photographs. They remain AI perspectives, not human reviewers. See the AI testing team, visual profile gallery, command guide, and MCP tool reference. The eight-command scope, license, data handling and permission boundaries are unchanged.

Eight workflows

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

CARBON: common questions

Is CARBON MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the CARBON safety report
How do I install CARBON?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does CARBON need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is CARBON maintained?
The last commit was 13 days ago (2026-10-22). The latest release is v1.32.22-free.17.
How does CARBON compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers); downloads a week 211 (more than 76% of 12,191 servers with a package). Full comparison.