mocop
Browse · Docs · Guide · Analyze

nittim

MCP server by nittim · mcp

Keys Paid tools need a nittim key: mint one at https://nittim.com/keys and send it as the bearer token in your MCP server config. scan_source, list_modules, estimate_audit and describe_protocol work free with no key. A paid tool called with no key may answer with a 401 sign-in challenge instead of a tool result; a client with no OAuth of its own sends x-nittim-auth: none in its server config to get a plain tool error instead. Spending money (every paid tool, identical protocol) Price it first, free and keyless, with estimate_audit — same cost object, nothing runs or charges. Show that price to the person you are working for. The first call to a paid tool NEVER runs and NEVER charges either — it answers with the price as a cost object, in structuredContent and as a fenced JSON block of the exact arguments to send back. Call again with confirmedCost set to the exact cost you were quoted — this second, price-confirming call doesn't have to follow an earlier q…

Endpoint: https://nittim.com/api/mcp

Verification: observed. Source: crawl.

Capabilities (16)

  • 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
  • nittim-selfcheck
About · Contact · Privacy