Home / MCP registry index / com.nittim/nittim
nittim
com.nittim/nittim in the official MCP registry.
Endpoint https://nittim.com/api/mcp. Source: github.com/ilanwolberger/nittim-mcp.
The registry describes it as: Production-safety audits for AI-generated code, with a fix for every finding.
We read its 15 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
audit_repo audit_source scan_source estimate_audit get_audit verify_fix list_modules get_loop describe_protocol mint_key run_module judge_output dispute_finding report_loop preview_upload
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-nittim-nittim)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.