CLI and MCP server
Run the same verifiers from the command line or expose them to an assistant over MCP. One implementation, asserted by the test suite.
CLI & MCP
BETAThe verifiers are pure modules with no UI dependency, so the same code runs from a shell and from a coding agent. There is no second implementation of any verification rule — the test suite asserts that the web module, the CLI and the MCP adapter return identical findings for the same fixture.
CLI
Stateless and non-interactive. Exit code 0 for PASS, 1 for FAIL, 2 for invalid input. Warnings do not fail unless you pass --strict.
npm run verify -- verify json --expected-file expected.json --actual-file response.json
npm run verify -- verify regex --pattern '^[a-z]+$' --cases-file cases.csv
npm run verify -- verify cron --expr '30 2 * * *' --timezone America/New_York
npm run verify -- verify jwt --token "$TOKEN" --audience api
npm run verify -- verify diff --patch-file change.patch
npm run verify -- verify url 'https://auth.example.com/authorize?...'
# Machine-readable output for a CI step
npm run verify -- verify json --expected-file a.json --actual-file b.json --format jsonMCP server
A stdio JSON-RPC server exposing nine deterministic tools: verify_json_schema_drift, test_regex_cases, preview_cron_schedule, inspect_jwt, inspect_url, review_patch, validate_yaml, inspect_env and review_sql.
Add it to a Claude- or Codex-compatible MCP client:
{
"mcpServers": {
"hakeemify-devtools": {
"command": "npm",
"args": ["run", "--silent", "mcp"],
"cwd": "/path/to/devtools-hakeemify"
}
}
}The adapter is stateless, performs no network I/O, never writes artifacts or secrets to a log, bounds responses to 100 findings, and versions every payload with schemaVersion. Agents must treat findings marked heuristic: true as suggestions to review, not as defects to fix.