MCP endpoint · you are looking at a server

This host does not serve a website. It answers one question, for coding agents.

Point your agent here and ask whether the app it built is fit to carry real users. It runs 118 read-only detectors against your own repository and gets back a graded readiness report — every gap named, every consequence spelled out — and what it would cost to close them.

MCP endpoint https://mcp.prodready.si/mcp streamable HTTP · no key · no account

Install it, in one line

Claude Codeterminal
claude mcp add --transport http prodready https://mcp.prodready.si/mcp --scope user

Then ask, in plain language: use prodready to check whether this app is production ready. Lines for Codex, Cursor, Windsurf and Cline are on the documentation page below.

Two tools, and that is all

prodready_probe(stack?)

Returns the read-only commands and file globs your host should run locally — greps, file counts, git ls-files. Nothing that writes or installs, and nothing a command does calls out.

prodready_assess(evidence)

Takes what your agent collected and returns findings mapped to numbered rules, a 0–100 score across five dimensions with a grade, and the scope of the work to close them.

The rule this server is built on

The report names the gap and its consequence. It never names the remedy. “Three tables carrying an owner column have row security switched off” is a finding; what you do about it is the work we sell. You will not find a patch, a migration, a config snippet or a step list anywhere in the output.

What never happens here

The full documentation is on the site.

What each tool returns, what a report looks like line by line, the five scoring dimensions and the grade bands, what the scan cannot see, how the scope band is worked out, and install lines for Claude Code, OpenAI, Cursor, Windsurf and Cline.

Read the docs