verifAIed
v1.0.0Verify what your AI coding agent built: test coverage, recorded browser tests, a done verdict.
Endpoint health
online- Last checked
- 11/20/2026, 9:16:53 AM
- Latency
- 95 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:app.verifaied%2Fverifaied
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"app.verifaied/verifaied": {
"url": "https://verifaied.app/mcp/"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
15 shown · authentication unknown
check_done
Am I done? The stop condition for a coding loop. **Free — no subscription, no token budget, no rate limit.** Composes what verifAIed already knows about a branch — failing tests plus the coverage of the functions you changed — into a single verdict you can gate on: - ``done`` (bool): ``true`` only when there are no gaps at all. This is the strict signal to stop. - ``status``: ``"done"`` | ``"done-with-warnings"`` | ``"not-done"``. ``done-with-warnings`` means the only remaining gaps are ones the repo owner marked non-blocking — read this yourself if you want to stop early. - ``scope``: ``"changed-functions"`` when a default-branch base exists (only added/modified functions are judged), else ``"all-functions"``. - ``gaps``: each remaining problem with a ``ref``, the id to act on (``function_id``/``test_id``), and a ``next_action`` pointing at ``get_baseline_prompt`` (free) or ``fix_branch`` (paid). Gap kinds: - ``failing_test`` — a test that failed or errored. - ``untested_function`` / ``partial_function`` — a changed function with no coverage, or only some. - ``unexercised_browser`` — a changed function that no browser reached, in either the browser-coverage or the manual dimension. Only judged once one of them exists. - ``visually_unreviewed`` — a changed component nobody has looked at. ``intent_mismatch`` — somebody looked and it didn't do what the change claimed. Both only judged once the branch has at least one ``verify_ui`` verdict. - ``unverified_recorded_test`` — a recorded test this branch has never run, or whose last run failed. Re-run it with ``verifaied test run "<feature path>/<name>"`` — the feature path is optional and may nest. Branch-wide, not diff-scoped. Absent entirely for a repo with no recorded tests. - ``visual_defect`` — something ``verifaied audit`` measured in the rendered page (overflow, contrast, a broken image, a console error), from the most recent audit of the branch. **The one kind that is a warning by default**, so it routes to ``done-with-warnings`` rather than blocking unless the repo owner turned it on. Only judged once the branch has been audited at least once. Gaps are ordered so a component's own gaps are immediately followed by its handlers' and render branches'; a sub-unit gap carries ``parent_ref`` (the parent's ``file::Name``) so you can group or indent them without parsing refs. The clustering is presentation only — every gap is still individually actionable by its own ``ref`` / ``function_id``. - ``not_checked``: signals that couldn't be evaluated (e.g. failing tests when no junit.xml was uploaded, or ``unexercised_browser`` when functions exist but no browser coverage was uploaded) — surfaced so a green verdict is never silently green. Pagination: ``gaps`` is capped at ``max_gaps`` per call (default 50) to stay within tool-result limits — a low-coverage branch can have hundreds. ``done``, ``status``, ``scope`` and ``gaps_total`` ALWAYS reflect the full gap set, never just the returned page, so a truncated page is never mistaken for a clean branch. When more gaps remain, ``has_more`` is ``true``, ``next_offset`` is the offset to pass next, and ``note`` spells out how to fetch the rest — call again with that ``offset`` until ``has_more`` is ``false``. The intended loop: run your tests with coverage (pytest → coverage.json, or ``vitest run --coverage --coverage.provider=istanbul`` → coverage/coverage-final.json) → ``upload_local_coverage`` → ``check_done`` → fix each gap (``get_baseline_prompt`` / ``fix_branch``) → re-upload → repeat until ``done`` is ``true``. ``repository`` is the GitHub 'owner/repo' (a repo UUID also works); ``branch`` defaults to the repository's default branch. Errors with an actionable message when no analysis exists for the branch yet — upload coverage first.
Connections
streamable-http
https://verifaied.app/mcp/