# verifAIed (remote · verifaied.app)

Verify what your AI coding agent built: test coverage, recorded browser tests, a done verdict.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `verifaied.app`: 64/100 (this document), [markdown](https://verifymcp.io/servers/app-verifaied-verifaied/verifaied.md), [page](https://verifymcp.io/servers/app-verifaied-verifaied/verifaied)

## Channel facts

- Endpoint: `https://verifaied.app/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5187 tokens (~345/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (20% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the verifAIed MCP server?

verifAIed is a hosted endpoint at https://verifaied.app/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http app-verifaied-verifaied 'https://verifaied.app/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "app-verifaied-verifaied": {
      "url": "https://verifaied.app/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-verifaied-verifaied": {
      "type": "http",
      "url": "https://verifaied.app/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-verifaied-verifaied]
url = "https://verifaied.app/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-verifaied-verifaied": {
      "type": "remote",
      "url": "https://verifaied.app/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-verifaied-verifaied --url 'https://verifaied.app/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-verifaied-verifaied:
    url: "https://verifaied.app/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "app-verifaied-verifaied": {
      "Transport": "http",
      "Url": "https://verifaied.app/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-verifaied-verifaied -t streamable-http -u 'https://verifaied.app/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "app-verifaied-verifaied": {
      "type": "http",
      "url": "https://verifaied.app/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 61)

First indexed and scored.

## MCP tools (15)

### `check_done` (~1028 tokens)

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 rend…

Input parameters:

- `branch`
- `max_gaps` (integer)
- `offset` (integer)
- `repository` (string, required)

### `setup` (~388 tokens)

Set verifAIed up for a repository. **Free.** Call this first after
the verifAIed MCP is connected, and again after each step.

Pass the repository as ``owner/repo`` from the git remote (a repo UUID
also works) and the current git branch; the default branch is used
when ``branch`` is omitted.

Returns an ordered checklist. Each step has a ``status``:

  \- ``done``: the server saw the result (a committed file, an
    analysis for the branch). No action.
  \- ``todo``: required and not done. ``commands`` and ``files`` say
    exactly what to run and write.
  \- ``check_locally``: required, but only your machine can tell (the
    CLI on PATH, the CLI's login). Run ``verify``; carry the step out
    if it fails.
  \- ``recommended``: not required; verifAIed asks you to offer it to
    the user rather than skip it.
  \- ``optional``: not required; mention it once.

\``next_step`` names the step to do now and ``complete`` is true when
no required step is left. A step with ``needs_user`` true needs a
person — for ``cli_token``, to approve the ``verifaied login`` you run
in the browser. This tool never mints or returns a token.

This tool reads the repository through the GitHub App and never
changes it. You write the files; the user commits them. ``facts``
says what was read, and ``facts.github_reachable`` is false when the
tree could not be read, in which case every step the tree would have
settled is ``check_locally``.

Input parameters:

- `branch`
- `repository` (string, required)

### `docs` (~492 tokens)

The verifAIed documentation, for you and for the user's questions.
\**Free.** Call this whenever the user asks how something in verifAIed
works or how to do something with it, and whenever you are unsure what
a tool, a command, a gap or an error means.

Three ways to call it:

  \- no arguments: the table of contents — every page with a one-line
    summary — and how to use the rest.
  \- ``query``: the question, or a few words of it. Returns the
    sections that match best, each with its own text, so one call is
    usually enough to answer from. A hit marked ``truncated`` was cut
    short: read its page for the rest. Start here when you do not
    know which page holds the answer.
  \- ``page``: one whole page as Markdown. Pass a name from the contents
    (the first page is ``overview``); a title or a documentation URL
    also works.

Pass ``page`` or ``query``, not both.

Answer from the returned text rather than from memory, and give the
user the page's ``url`` so they can read it themselves. A page with no
\``url`` is one of the notes for agents: tell the user what it says,
there is no link to give. When nothing
matches, the documentation does not cover it: tell the user that, and
do not infer an answer from what is missing. Pages in the
group "For agents" are reference written for you and are not on the
website: ``agents/gaps`` (what every check_done gap means and what
closes it), ``agents/errors`` (what an error or refusal means and the
fix) and ``agents/formats`` (exact file and JSON formats, exit codes).

Every answer carries ``account``: the user's plan, and on the free
plan a note on what is refused, so you do not suggest a feature this
account cannot use. The table of contents has the full list of paid
tools.

This is the one tool that works with no account: a connection without
credentials can read the documentation, and its ``account`` is null.
Every other tool needs the user to sign in first.

Input parameters:

- `page`
- `query`

### `fix_branch` (~373 tokens)

Return the fix-it prompt the web UI's 'Generate prompt for
everything wrong' button produces for a branch — the common-case
one-shot for "fix everything broken here". Resolves the repo +
branch, finds the latest analysis, generates (or fetches a cached)
bulk prompt, and waits up to ``wait_seconds`` for completion.

\``repository`` is required — pass the GitHub 'owner/repo' for the
project the user is working in. You (the MCP client) almost always
know this from the working directory's git remote, the open
workspace, or the conversation; pass it explicitly rather than
calling ``list_repositories`` first. A repo UUID is also accepted
for callers that already have one.

\``branch`` defaults to the repository's default branch.

\``scope`` selects what to aggregate (default ``"everything"``):
  \- ``untested`` — all functions with no tests yet
  \- ``partial`` — all functions only partially covered
  \- ``failing`` — all failing tests
  \- ``everything`` — failing tests + all untested + partial functions
  \- ``frontend`` — TypeScript components grouped with the handlers and
    render branches inside them that nothing exercises yet;
    Playwright/React-Testing-Library oriented rather than a flat
    function list

Returns the same shape as ``get_bulk_prompt`` — on cache hit /
completed generation, ``{status: "completed", prompt_text, ...}``;
on timeout, ``{status: "pending", generation_id}`` so you can
resume via ``wait_for_prompt``.

Input parameters:

- `branch`
- `force` (boolean)
- `repository` (string, required)
- `scope` (string)
- `wait_seconds` (integer)

### `list_repositories` (~71 tokens)

List the caller's repositories. Wraps the same data the web
UI's repo list shows.

For the common 'fix everything wrong on a branch' workflow, prefer
\``fix_branch`` — it takes 'owner/repo' directly and you usually
know that from the working directory / git remote.

Output parameters:

- `result` (array)

### `list_analyses` (~101 tokens)

List analyses for the given repository, newest first.

\``repository_id`` is the GitHub ``owner/repo`` (a repo UUID also
works). Mirrors the BranchView's per-branch state. ``commit_sha`` is
the commit the analysis was refreshed against.

For the common 'fix everything wrong on a branch' workflow, prefer
\``fix_branch`` — it resolves the latest analysis for you.

Input parameters:

- `repository_id` (string, required)

Output parameters:

- `result` (array)

### `list_untested_functions` (~183 tokens)

List functions in an analysis, filtered by coverage state.

\``state_filter`` is a comma-separated subset of
\``untested,partial,covered``. Default skips fully-covered functions
— those are typically what an agent looking for "tests to write"
cares about.

Rows include React sub-units — an inline JSX handler
(``Component.<onSubmit>``, ``kind="handler"``) or a conditional render
branch (``Component.<branch#1>``, ``kind="render_branch"``) — because
"this component's error state never rendered" is usually the actionable
gap, not "this component is 80% covered". Filter on ``kind`` in
\``("function", "component")`` when you want whole functions only.

Input parameters:

- `analysis_id` (string, required)
- `state_filter` (string)

Output parameters:

- `result` (array)

### `get_function_detail` (~58 tokens)

Source + uncovered lines for one function. The agent typically
calls this after ``list_untested_functions`` to pick a target and
write tests for it directly without going through the prompt
generator.

Input parameters:

- `function_id` (string, required)

### `get_baseline_prompt` (~279 tokens)

Get a ready-to-use test prompt for one function. **Free — no
subscription, no token budget, no rate limit.**

Rendered deterministically from the function's AST plus its coverage
rows: the signature, what to call, which exact lines never execute,
which branches only go one way, what it raises, and which tests
already touch it. Use this as the default way to turn "this function
is untested" into "here is what to write".

\``get_generated_prompt`` is the paid, LLM-polished counterpart — it
adds repo conventions and richer context, but this one is free and
always available, and for most functions it is enough to write the
test from.

Also accepts a React sub-unit id. The prompt then matches what the
unit is: fire this handler on this element and assert the effect, or
render the component in the state that takes this branch. ``kind``
and ``display_label`` come back alongside the prompt.

Errors if the function is already fully covered — there is nothing to
prompt for. The exception is a covered function that no browser test and
no recorded manual session has reached: that still has a real ask (drive
it in a browser), so it returns a prompt saying exactly that.

Input parameters:

- `function_id` (string, required)

### `upload_local_coverage` (~924 tokens)

Upload local coverage + current source and get back what's still
untested — the core self-correction loop for writing tests without
waiting on CI. Works for Python (pytest-cov) and TypeScript/JavaScript
(vitest + Istanbul).

\``coverage_kind`` selects the dimension: ``"unit"`` (default) is the
test-suite coverage flow described here; ``"browser"`` records an
independent per-function *browser-session* dimension from a real browser
run — any coverage format (Istanbul for a frontend harvest, pytest-cov
for a coverage-instrumented backend serving the browser's requests), no
junit. A branch's browser coverage is the **union** of what each
producer last reached — its wrapped suite, and each recorded test's
latest replay — and this upload replaces only the contribution of the
producer it belongs to, per language (a TS-only browser upload never
zeroes the Python dimension, and vice versa). It surfaces as
\``browser_state``
(``exercised``/``partial``/``unexercised``) + ``browser_line_coverage_pct``
on each function and as the ``unexercised_browser`` gap in
\``check_done``, and never changes unit state.

Browser and manual uploads are also recorded in the branch's session
ledger, so the Tests page can say what produced them. Pass
\``session_id`` if you opened one; otherwise this upload becomes its own
session, attributed to ``agent`` — you.

Run your tests with coverage locally first:
  \- Python:  ``pytest --cov --cov-branch --cov-context=test`` then
    ``coverage json --show-contexts -o coverage.json`` (pytest-cov's
    own ``--cov-report=json`` drops the per-test contexts)
  \- TS/JS:   ``vitest run --coverage --coverage.provider=istanbul
    --coverage.reporter=json`` → ``coverage/coverage-final.json``

Pass a ``files`` map of {source_path: contents} for the files under
test, plus **exactly one** of:
  \- ``coverage_json`` — a single parsed report (pytest-cov or Istanbul).
  \- ``coverage_reports`` — a list of parsed reports, merged with
    same-file-later-wins; use this to se…

Input parameters:

- `branch` (string, required)
- `commit_sha`
- `coverage_json`
- `coverage_kind` (string)
- `coverage_reports`
- `files` (object, required)
- `junit_xml`
- `path_prefix`
- `repository_id` (string, required)
- `session_id`

### `clear_manual_coverage` (~238 tokens)

Reset the accumulated **manual-recording** dimension for a branch.

Manual uploads are **additive**: each ``upload_local_coverage`` with
\``coverage_kind="manual"`` unions that hand-driven session into the
branch's manual dimension, so you can build a pass up one flow at a
time. Call this to wipe that accumulation and start over — every
function goes back to Unexercised. The branch's ``manual_languages`` are
kept, so the Manual Recording view stays visible; only the per-function
coverage is cleared.

This does **not** touch browser coverage (``coverage_kind="browser"``),
which has no clear at all: every producer there replaces its own
contribution on its next run, so nothing accumulates to be reset.

\``repository`` is the GitHub 'owner/repo' (a repo UUID also works);
\``branch`` defaults to the repository's default branch. Errors when the
branch has no local analysis to clear. Returns ``cleared_functions`` —
the number of function rows reset.

Input parameters:

- `branch`
- `repository` (string, required)

### `verify_ui` (~529 tokens)

Judge a screenshot of the running UI. **Paid.**

You drive the browser; verifAIed judges what you got. Take a
screenshot of the change you just made, say what it was supposed to
do, and this returns a verdict — plus records it, so ``check_done``
can hold the branch to it.

Two modes:

\- With ``intent`` (recommended): checks one claim. "The error state now
  shows a Retry button" → ``pass`` / ``fail`` / ``unclear``, with a
  confidence and the reasoning. ``unclear`` is a real answer, used when
  the screenshot doesn't show the region the claim is about — treat it
  as "screenshot the right thing and ask again", not as a pass.
\- Without ``intent``: a rubric review (layout, hierarchy, legibility,
  consistency, obvious broken state) returning ``clean`` or ``issues``
  with a defect list.

\``target`` attaches the verdict to one component as
\``path/to/File.tsx::ComponentName``, which is what clears that
component's ``visually_unreviewed`` gap. A target that doesn't resolve
is not an error: the verdict is still recorded against the branch and
the response carries a ``warning`` saying so.

\``screenshot_base64`` is the raw image bytes, base64-encoded (a
\``data:`` URL prefix is fine). PNG, JPEG, GIF or WebP; a viewport-sized
capture is plenty and anything over ~1.5MB of base64 is rejected with a
resize hint. Pass ``console_errors`` when you have them — a visual
defect and a console error are very often the same bug.

The screenshot **is stored** as session evidence: each call opens a
one-moment session in the branch's ledger and attaches the image to it,
so the Tests page can show the frame the verdict was about. The
reasoning text is still the record — the picture is the receipt.

Failing an intent check creates an ``intent_mismatch`` gap; a changed
component with no verdict creates ``visually_unreviewed``. Both
activate only once this branch has at least one verdict, so a repo that
doesn't use this tool never sees them.

Input parameters:

- `branch`
- `console_errors`
- `intent`
- `repository` (string, required)
- `screenshot_base64` (string, required)
- `target`
- `viewport`

### `get_generated_prompt` (~92 tokens)

Return a meta-prompt for writing tests for the function.

Cache hits return immediately. Cache misses enqueue a fresh
generation and poll the row for up to ``wait_seconds``. On
timeout the agent gets the ``generation_id`` and can call
\``wait_for_prompt`` to keep waiting.

Input parameters:

- `force` (boolean)
- `function_id` (string, required)
- `wait_seconds` (integer)

### `get_bulk_prompt` (~246 tokens)

Return a single meta-prompt covering many items in an analysis.

\``scope`` selects which slice to aggregate:
  \- ``untested`` — all functions with no tests yet
  \- ``partial`` — all functions only partially covered
  \- ``failing`` — all failing tests
  \- ``everything`` — failing tests plus all untested + partial functions
  \- ``frontend`` — TypeScript components grouped with the handlers and
    render branches inside them that nothing exercises yet;
    Playwright/React-Testing-Library oriented rather than a flat
    function list

Cache hits return immediately; cache misses enqueue a fresh
generation and poll for up to ``wait_seconds``. On timeout the
caller gets the ``generation_id`` and can call ``wait_for_prompt``
to keep waiting.

For the common 'fix everything wrong on a branch' workflow, prefer
\``fix_branch`` — it takes 'owner/repo' directly and saves the
list_repositories → list_analyses chain.

Input parameters:

- `analysis_id` (string, required)
- `force` (boolean)
- `scope` (string, required)
- `wait_seconds` (integer)

### `wait_for_prompt` (~68 tokens)

Poll a prompt generation row until it transitions to completed
or failed, or until the timeout. The companion to
\``get_generated_prompt`` — call this if the first call returned
\``status: pending``.

Input parameters:

- `generation_id` (string, required)
- `timeout_seconds` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-verifaied-verifaied/verifaied#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 62
- 2026-11-16: 62
- 2026-11-15: 61

## Common questions

### What is the verifAIed MCP server?

verifAIed is an MCP server listed in the public MCP registry as app.verifaied/verifaied. Verify what your AI coding agent built: test coverage, recorded browser tests, a done verdict. This page covers its hosted endpoint (https://verifaied.app/mcp/).

### Is the verifAIed MCP server safe to use?

verifAIed scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the verifAIed MCP server expose?

verifAIed exposes 15 tools: check_done, setup, docs, fix_branch, list_repositories, and 10 more. Their descriptions and schemas cost roughly 5,070 tokens of context every time the server is loaded.

### Does the verifAIed MCP server require authentication?

No. We connected to verifAIed without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the verifAIed MCP server still maintained?

verifAIed is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the verifAIed MCP server?

VerifyMCP ran 12 checks on verifAIed, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about verifAIed: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://verifaied.app/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/app-verifaied-verifaied/verifaied.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-verifaied-verifaied/verifaied/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-verifaied-verifaied/verifaied.json
- HTML version of this page: https://verifymcp.io/servers/app-verifaied-verifaied/verifaied
