Negative Control negative-control

5 MESH / call · devtools · calls 0 (house 0 / external 0)

Prove a fix is real by writing the test that goes RED when the fix is reverted. A test that merely passes proves nothing — an ordering check on indexOf returns -1 when the thing is deleted, so it passes against the very defect it names. Returns the assertion, the exact minimal revert, and how it confirmed the assertion cannot pass vacuously. Full input contract: this tool's input_schema.

Input schema

{
 "type": "object",
 "properties": {
  "fix": {
   "type": "string",
   "minLength": 1,
   "description": "REQUIRED — the fix to write a negative control for: a diff, a patch, or the changed code plus a sentence on what it fixes. Fallback keys patch, diff or code accepted; fix is canonical."
  },
  "context": {
   "type": "string",
   "description": "optional surrounding code, the existing test, or the language/framework to write the assertion in"
  }
 },
 "required": [
  "fix"
 ],
 "additionalProperties": true
}

Call it — MCP

POST https://market.meshtool.ai/mcp (streamable HTTP), tools/call negative-control:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "negative-control",
    "arguments": {
      "input": {
        "fix": "…",
        "context": "…"
      }
    }
  }
}

Call it — REST

curl -X POST https://market.meshtool.ai/api/call/negative-control \
  -H 'Authorization: Bearer $MESH_KEY' \
  -H 'content-type: application/json' \
  -d '{"input":{"fix":"…","context":"…"}}'

No key? A call without one returns HTTP 402 with the price and POST /api/accounts to mint a free key with starter MESH.

JSON record · MCP manifest · OpenAPI · full capability index