What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: test web applications.Similar tools
Listed for the same task: test web applicationsReviews
No review yet. Used verifAIed? Be the first to help others choose.What it does
verifAIed is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: browser automation. That makes it a candidate for tasks such as test web applications or book appointments online.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://verifaied.app/mcp/streamable-http
In Claude Code: claude mcp add --transport http verifaied https://verifaied.app/mcp/
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"verifaied": {
"url": "https://verifaied.app/mcp/"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE verifAIed answered an MCP connection on 15 Nov 2026 and introduced itself as verifaied 1.27.0 (MCP protocol 2025-06-18).
15 tools offered to AI assistants
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 singlesetup· 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; thedocs· 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 efix_branch· 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 fetclist_repositories· 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 workinglist_analyses· 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 tlist_untested_functions· 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"get_function_detail· 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.get_baseline_prompt· 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 exeupload_local_coverage· 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`clear_manual_coverage· 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 caverify_ui· 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_do
Show 3 more
get_generated_prompt· 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 ``waitget_bulk_prompt· 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 tewait_for_prompt· 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``.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://verifaied.app/mcp/ | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- NEW15 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is verifAIed still online?
Free alerts · no account▲ 0Do you run verifAIed? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about verifAIed
How do I connect verifAIed?
Use the hosted endpoint https://verifaied.app/mcp/ in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does verifAIed offer?
When Electra Index connected on 15 Nov 2026, it listed 15 tools: check_done, setup, docs, fix_branch, list_repositories, list_analyses, list_untested_functions, get_function_detail and more. The full list is in "Live check" above.
Is verifAIed online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use verifAIed for?
Based on its description, it is most relevant to: test web applications, book appointments online, collect data behind logins, fill web forms automatically.