Developer · Remote MCP server

nittim

Production-safety audits for AI-generated code, with a fix for every finding.

Visit nittim's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.nittim/nittim
Version
1.1.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-08
Updated
2026-09-08
Publisher
com.nittim
Namespace
Namespace verified by the MCP Registry via the domain nittim.com · how
Website
nittim.com
Repository
github.com/ilanwolberger/nittim-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://nittim.com/api/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
nittim 0.2.0+6125d24 · protocol 2025-06-18
Tools discovered
15 - show namesaudit_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
Checked on
2026-10-05

How the live check works

How to connect nittim

nittim is a remote MCP server: there is nothing to install. Its endpoint is https://nittim.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
NimbusSearch your local Nimbus index and run its built-in agents from any MCP client.Local · stdionpm: @nimbus-dev/mcp
NIRA REPL MCPSecure code execution sandbox for Claude - run Python, JavaScript, and shell commands.Local · stdioPyPI: nira-repl
NiroAI pentester for PRs - finds exploitable bugs and hands your developer agent the fix.Local · stdioMCP Bundle (.mcpb): apxlabs-ai/niro/releases/download/v0.1.61/niro.m
Nis2 Incident Runbook LintReads your incident-response runbook and says which of the three Article 23 clocks it gets wrong.Local · stdionpm: @readystack/nis2-incident-runbook-lint
nlqdb - analytical memory for AI agentsAnalytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.Remote · HTTPLive check: sign-in requiredmcp.nlqdb.com
No CrdDynamic pod spawner & proxy for ephemeral AI agent workspaces on Kubernetes without CRDs.Local · stdionpm: @nogoo9/no-crd
No-Code ExitsNo-code startups for sale, the deal-scoring method behind each pick, and exit stories.Remote · HTTPLive check: ✓ handshakenocodeexits.com
No-Shell Agent Architect MCPTurns vague automation requests into tool stacks, prompts, QA checks, and human boundaries.Remote · HTTPLive check: ✓ handshakeai-automation-operating-pack.vercel.app