What is nittim MCP Server?
nittim MCP Server is the hosted MCP endpoint for nittim, a security audit for AI-written code: your coding assistant can scan a repo or posted files for committed secrets and known vulnerable dependencies for free, then run a paid audit that returns a verdict, findings and a fix for each.
nittim runs at https://nittim.com/api/mcp over Streamable HTTP. The free tools need no account or key. Paid tools always quote a price first, and no charge goes through until the account owner confirms it on a one-time link. The GitHub repository ilanwolberger/nittim-mcp holds only listing manifests, a Claude Code plugin and the nittim-loop skill; the server itself is operated by nittim.
How to use nittim MCP Server?
No install is needed. Connect the endpoint, then ask for a scan. Free tools (scan_source, list_modules, estimate_audit, get_loop) work right away. For paid audits, mint an API key at nittim.com/keys; the plaintext is shown once. nittim advises keeping the key at user scope and never in a project .mcp.json that gets committed. Clients that cannot sign in over OAuth can use the mint_key tool, which returns a short one-time claim link (never the key itself).
Claude Code
claude mcp add --transport http nittim https://nittim.com/api/mcp
Or install it as a plugin, which also adds the nittim-loop skill:
/plugin marketplace add ilanwolberger/nittim-mcp
/plugin install nittim@nittim
Claude Code's auto mode refuses tools it reads as able to spend money, even a paid tool's first, quote-only call. nittim's README suggests allowing the server in ~/.claude/settings.json or .claude/settings.json:
{ "permissions": { "allow": ["mcp__nittim"] } }
Claude Desktop / claude.ai
Open Settings → Connectors → Add custom connector and paste https://nittim.com/api/mcp.
Cursor
Use the "Add to Cursor" button in the README, or add this to mcp.json:
{
"mcpServers": {
"nittim": {
"url": "https://nittim.com/api/mcp"
}
}
}
VS Code
Use the "Install in VS Code" button, or add it to .vscode/mcp.json:
{
"servers": {
"nittim": {
"type": "http",
"url": "https://nittim.com/api/mcp"
}
}
}
Windsurf
nittim's docs put the entry in mcp_config.json (often ~/.codeium/windsurf/mcp_config.json), where the address field is serverUrl:
{
"mcpServers": {
"nittim": {
"serverUrl": "https://nittim.com/api/mcp"
}
}
}
Key features of nittim MCP Server
- Free deterministic scan: committed secrets and known CVEs (OSV dependency check) over posted source files, with no account, no key and no cap. It returns evidence only, never scores or a verdict.
- Paid AI audit with a verdict: Production Ready, Production Ready with Conditions, High Risk or Not Safe, with security, privacy, reliability and architecture findings, each paired with a fix.
- Price before you pay:
estimate_audit quotes the tier, pass count and exact price for a repo or a manifest of paths and sizes, without uploading anything.
- Owner confirmation: paid calls run in three steps (quote, confirm link, run), and the ledger moves only after the account owner clicks Confirm.
- Fix verification:
verify_fix re-checks one finding against current code and answers fixed, still present or undetermined.
- Free self-review loop:
get_loop returns nittim's public checklist so your assistant can review the code on your own model, with nothing sent to nittim.
nittim MCP Server tools
The server exposes 15 tools.
- Free scanning and pricing:
scan_source (secrets and CVEs over posted files), list_modules (every check, with key, tier and description), estimate_audit (exact price, no charge) and get_loop (the self-review checklist).
- Paid audits:
audit_repo audits a GitHub repository and is the only tool that returns scores and a verdict (fullScan: true buys the wider Full Audit tier); audit_source audits posted source files for projects with no GitHub remote; run_module runs a single module (the secret-scan and dependency-cve modules are free); judge_output runs a cross-vendor judge model over any text and returns findings only.
- Results and follow-up:
get_audit fetches an audit by ID at any stage, verify_fix re-checks a finding, and dispute_finding records that a finding is wrong or confirmed for owner triage.
- Account and protocol:
mint_key, preview_upload (approve a file list ahead of time), report_loop (send anonymised Nittim Loop counts, which can earn a credit reward) and describe_protocol (how quoting, charging, tiers and disputes work).
Use cases of nittim MCP Server
- Pre-ship secret check: "Scan this repo with nittim for committed secrets and vulnerable dependencies."
- Self-review on your own model: "Run nittim's
get_loop and review this repo against it."
- Budgeting an audit: "Estimate what a nittim Full Audit of this repository would cost."
- Agent fix loop: run an audit, fix the top findings, then call
verify_fix on each one.
Troubleshooting nittim MCP Server
- Auto mode blocks the tools: add
mcp__nittim (or mcp__<your-name>) to permissions.allow; the free tools work without this rule.
- Sign-in prompt for free tools: add the header
x-nittim-auth: none to the server entry.
- "NEEDS A KEY" responses: paid tools,
verify_fix, dispute_finding, report_loop and preview_upload need a key from nittim.com/keys.
Comments