Skip to main content
Glama

prufa-mcp — the QA agent for your vibe-coded app

Vibe-coded apps ship faster than anyone can review them. In June 2026 we audited 49 fresh Show HN launches — 38 had a critical bug on day one: a broken signup, a silent console error, analytics that never fired, a consent banner that did nothing.

Prufa is the agent that catches those before your users do. Point it at a URL and it audits the things humans skip when they're moving fast — broken flows, JS console errors, missing tracking, consent violations, security headers, mobile tap targets, accessibility — and hands back machine-verified findings, graded A–F. This repo is the open-source MCP server that wires that audit straight into your coding agent.

30-second demo

Installing prufa-mcp and wiring it into Claude Code

Related MCP server: Argus

What an audit gives you

Ask your agent to audit https://yourapp.com and prufa_run_audit returns one JSON report. Findings are grouped into graded sections, each finding carries a severity, the impact (why it matters), and a fix hint. Real output, trimmed:

{
  "url": "https://yourapp.com",
  "headline": "2 warnings found",
  "counts": { "critical": 0, "warning": 2, "info": 5 },
  "sections": [
    { "label": "Works",     "grade": "C", "counts": { "warning": 2, "info": 1 } },
    { "label": "Fast",      "grade": "A" },
    { "label": "Found",     "grade": "A" },
    { "label": "Compliant", "grade": "A" }
  ],
  "check_results": [
    {
      "check_id": "ux",
      "findings": [{
        "severity": "warning",
        "title": "2 javascript console error(s) during page load",
        "impact": "Errors at load time often mean broken features visitors never report.",
        "evidence": { "count": 2, "sample": [
          "Access to XMLHttpRequest at 'https://api.fontshare.com/...' blocked by CORS policy",
          "Failed to load resource: net::ERR_FAILED"
        ]}
      }]
    },
    {
      "check_id": "mobile",
      "findings": [{
        "severity": "warning",
        "title": "13 tap target(s) smaller than 24px",
        "impact": "Fingers are not cursors — undersized buttons mean mis-taps on exactly the elements you want pressed.",
        "fix_hint": "Give interactive elements at least 24x24px of hit area (WCAG 2.5.8)."
      }]
    },
    {
      "check_id": "security",
      "findings": [{
        "severity": "info",
        "title": "no Content-Security-Policy header",
        "impact": "Without a CSP, one injected script owns the page — and every third-party tag you load is trusted completely.",
        "fix_hint": "Start with a report-only CSP and tighten from real violation reports."
      }]
    }
  ],
  "report_url": "/r/G82RpzTi_zn-o71_XoMLCprP7uvCQP87"
}

report_url is a shareable HTML version of the same report. The full payload also includes tracking, consent, seo/aeo, a11y, forms, and detected user flows — see the OSS surface below.

Install

The package is on PyPI. Install it globally with pipx (recommended — isolated venv, exposes the prufa-mcp binary on your PATH) or into a project venv with pip:

# Recommended — global install, isolated venv
pipx install prufa-mcp

# Or, into your project venv
pip install prufa-mcp

# Pin a specific version with ==, e.g. pipx install prufa-mcp==0.1.3

# Verify the binary is on PATH
which prufa-mcp
# Should print something like: /Users/you/.local/bin/prufa-mcp

You also need a free Prufa API key. The first audit is free, no card required.

  1. Sign in at prufa.dev (Google OAuth)

  2. Create an API key from the dashboard

Wire into your agent

The MCP server runs as a stdio subprocess, spawned by your agent on first use. The cleanest way to register it is claude mcp add (Claude Code's built-in command — it writes the config to ~/.claude.json correctly, which the ~/.claude/mcp.json path does NOT).

# Get the absolute path of the binary (use whatever `which prufa-mcp` returned)
PRUFA_BIN=$(which prufa-mcp)

# Add the MCP server. The token stays out of your shell history.
read -s -p "Prufa API token: " PRUFA_TOKEN && echo
claude mcp add \
  --scope user \
  --env "PRUFA_API_TOKEN=$PRUFA_TOKEN" \
  prufa \
  -- "$PRUFA_BIN"

Restart Claude Code (config is read at startup), then verify:

/mcp

You should see prufa listed as Connected, with prufa_run_audit and prufa_get_report as available tools.

Cursor / Cline / Continue (hand-edit .mcp.json)

In your project root or in ~/.config/Claude/ etc.:

{
  "mcpServers": {
    "prufa": {
      "command": "/Users/you/.local/bin/prufa-mcp",
      "env": {
        "PRUFA_API_TOKEN": "your-prufa-api-key"
      }
    }
  }
}

Restart the host app. The command path must be the absolute binary path (not ~, not $()) — those don't expand in MCP config.

Prefer config files to env vars? Drop your token in ~/.config/prufa/mcp.json instead — see ADVANCED.md.

Use it

In your agent:

> audit https://my-vibe-coded-app.com and show me the criticals
> run prufa on my staging deploy
> fetch the report for the audit I just ran

prufa_run_audit with wait=true (the default) blocks until the audit completes and returns the JSON report directly — typically 25–60s for a public page. If you set wait=false, the call returns immediately with the queued state plus a share_token you can poll with prufa_get_report.

What you get — the full agent surface

prufa-mcp exposes the whole product over MCP (44 tools). Point your agent at Prufa and it can audit pages, drive multi-step flows, watch for regressions, run chaos tests, run full-auto discovery, and manage the workspace + billing — no dashboard round-trip. Free/anonymous tools need no card; Pro tools return the API's 402 with a checkout link when you're not on a plan (the tool is visible, the paywall is server-side).

Audit & reports

Tool

What it does

prufa_run_audit(url, wait=true)

One-shot public-page audit; blocks and returns findings JSON.

prufa_get_report(run_id?, share_token?)

Fetch a report by UUID or /r/ slug.

prufa_get_run(run_id)

Poll a run's status.

prufa_list_runs(limit)

Recent runs in the workspace.

prufa_get_finding(run_id, finding_key?)

Persisted findings, machine-readable.

prufa_list_alerts()

Alert ledger (newest first, incl. suppressions).

Workspace, usage & conversion

Tool

What it does

prufa_setup_workspace(owner_email, name?)

Create a free, no-card agent_temp workspace (7-day trial) and return an API token once. If a token is already set, returns the real workspace + trial state.

prufa_get_workspace()

Current workspace + inlined usage + a trial block.

prufa_get_usage()

Usage object + trial/upsell blocks — call before metered actions.

prufa_workspace_settings(...)

Usage webhook, auto-recharge, email/Slack switches.

prufa_set_notifications(cells)

The 9-event × {email, slack} routing matrix.

Billing (returns a URL for the human to open — never takes a card)

Tool

What it does

prufa_upgrade_plan(tier)

Stripe checkout URL for a paid plan (starter/pro/team).

prufa_buy_credits(credits)

Stripe checkout URL for a one-time credit pack.

prufa_billing_portal()

Stripe customer portal URL (card, invoices, cancel).

Flows (describe a journey → reviewable spec → run)

Tool

What it does

prufa_create_flow(url, test_case, name?)

Compile a plain-text test case to a draft spec.

prufa_confirm_flow(flow_id, spec?)

Approve a draft — only confirmed flows run.

prufa_run_flow(flow_id, credentials?)

Execute a confirmed flow.

prufa_set_flow_credentials(flow_id, credentials)

Store {{VAR}} values (write-only).

prufa_edit_flow(flow_id, spec)

Edit the spec (returns it to draft).

prufa_get_flow · prufa_list_flows · prufa_delete_flow

Read · list · remove.

Monitors (watch a URL or flow on a schedule)

Tool

What it does

prufa_start_monitor(url, cadence?, flow_id?)

1-click monitor; returns a deploy-hook secret once.

prufa_trigger_monitor(monitor_id)

Run now (rate-capped).

prufa_pause_monitor · prufa_resume_monitor · prufa_get_monitor · prufa_list_monitors · prufa_delete_monitor

Lifecycle.

prufa_rotate_monitor_webhook(monitor_id)

Rotate the deploy-hook secret.

prufa_list_monitor_deliveries(monitor_id)

Deploy-hook delivery log + CI snippets.

Gremlin (chaos QA)

Tool

What it does

prufa_run_gremlin(url, persona?, direction?, credentials?)

Imitate a difficult user; detectors verify what breaks. Mutations dry-run unless authorized; payments never execute.

prufa_rerun_gremlin(run_id)

Re-run a past gremlin with the same intent + saved login.

prufa_authorize_domain(host, allow_mutation?)

Allow real (non-payment) writes on a host you own.

prufa_list_gremlin_domains()

List mutation authorizations.

prufa_gremlin_saved_logins()

Reuse a prior login (owning workspace only — sensitive).

prufa_promote_gremlin_path(share_token, path_index)

Turn a reproduced bug path into a draft flow.

Discovery (full-auto — crawl, infer flows, draft them)

Tool

What it does

prufa_register_discovery_domain(domain)

Register a domain, get the DNS TXT record to publish.

prufa_verify_discovery_domain(domain_id)

Verify the DNS proof.

prufa_list_discovery_domains · prufa_revoke_discovery_domain

Manage authorized domains.

prufa_run_discovery(url)

Crawl a verified site and draft its meaningful flows.

prufa_get_discovery(discovery_id)

Run status + the flows it surfaced.

Plus prufa_health_check() (probe the server/API).

The free trial, and when to upgrade

prufa_setup_workspace mints a free agent_temp workspace: no card, a 7-day trial, and an included credit budget. Monitors, discovery, and full-length gremlin runs work during the trial, then need a paid plan.

The MCP makes this legible to your agent: prufa_get_usage, prufa_setup_workspace, and every metered result carry a trial block (days + credits remaining) and, when you're low on credits or near the trial's end, an upsell block with a message_for_human your agent can relay plus the exact tool to call (prufa_upgrade_plan / prufa_buy_credits). When a Pro tool is called off-plan, the 402 passes through with a checkout_url — no silent failures, no surprise charges.

Examples

Three runnable scripts in examples/:

  • examples/nextjs-app/ — audit a deployed Next.js app

  • examples/vite-spa/ — audit a Vite SPA (focuses on client-side routing audits)

  • examples/stripe-checkout/ — audit a Stripe-checkout page (payment-flow verification)

Each is a copy-pasteable demo:

export PRUFA_API_TOKEN=...
python examples/nextjs-app/audit.py https://your-nextjs-app.com

GitHub Action

Fail a PR when Prufa finds a critical regression:

# .github/workflows/prufa-scan.yml
name: Prufa scan
on: [pull_request]
jobs:
  audit:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.11"
      - run: pip install prufa-mcp
      - name: Run audit
        env:
          PRUFA_API_TOKEN: ${{ secrets.PRUFA_API_TOKEN }}
        run: |
          python -c "
          import asyncio, sys
          from prufa_mcp.audit import run_audit
          report = asyncio.run(run_audit(url='${{ secrets.STAGING_URL }}', wait=True))
          print(report.get('headline', 'audit complete'))
          criticals = report.get('counts', {}).get('critical', 0)
          if criticals:
              print(f'::error::Prufa found {criticals} critical finding(s)', file=sys.stderr)
              sys.exit(1)
          "

See examples/prufa-scan.yml for the full template.

License

Apache-2.0. See LICENSE. Contributions welcome — see CONTRIBUTING.md.

Available Tools

44 tools
prufa_authorize_domainA

Authorize REAL (non-payment) mutations for the gremlin on a host you own or a staging host — logging in and writing on that host stop being dry-run. Set allow_mutation=false to revoke. This is the gremlin mutation opt-in, NOT the discovery DNS-domain verification (a different system). host is a bare hostname (e.g. staging.acme.com). [Pro]

Inputs: host (required), note, allow_mutation.

prufa_billing_portalA

Open the Stripe customer portal for this workspace. Returns a portal_url the HUMAN opens to manage the subscription, update the card, or view invoices. A workspace with no Stripe customer yet returns 409 no_stripe_customer (pass that back to the human — they must subscribe first via prufa_upgrade_plan). Mutating + idempotent. [Pro]

Inputs: return_url, idempotency_key.

prufa_buy_creditsA

Buy a one-time prepaid credit pack for this workspace (no subscription change). Returns a Stripe checkout_url the HUMAN opens to pay by card. Use when the workspace is low on credits but you don't want to change the plan. Mutating + idempotent. [Pro]

Inputs: credits (required), cancel_url, success_url, idempotency_key.

prufa_confirm_flowA

Confirm a DRAFT flow so it becomes runnable — only confirmed flows run. Pass flow_id. Optionally pass a corrected spec object to override the compiled draft before confirming (omit it to confirm the draft as-is). Idempotent.

Inputs: flow_id (required), spec, idempotency_key.

prufa_create_flowA

Compile a plain-language test case into a reviewable DRAFT flow spec. Pass the target url and a plain-text test_case (e.g. 'log in, add the first product to the cart, and check out'); optionally a name. Returns a 201 draft: the compiled step spec plus any {{VARIABLES}} it detected (logins, coupon codes) and a review instruction. The flow does NOT run yet — review the draft, then call prufa_confirm_flow. Only confirmed flows run. Idempotent.

Inputs: url (required), test_case (required), name, idempotency_key.

prufa_delete_flowA

Delete a flow by id. NOTE: a flow still used by a monitor returns 409 flow_in_use — pause or delete that monitor first, then retry. Idempotent.

Inputs: flow_id (required), idempotency_key.

prufa_delete_monitorA

Delete a monitor (stops all future runs and revokes its deploy hook). Past run history is retained. Idempotent. [Pro]

Inputs: monitor_id (required), idempotency_key.

prufa_edit_flowA

Replace a flow's spec. Pass flow_id and the full spec object. NOTE: any edit returns the flow to DRAFT — you must call prufa_confirm_flow again before it can run. Idempotent.

Inputs: spec (required), flow_id (required), idempotency_key.

prufa_get_discoveryA

[Pro] Get a discovery run's status and the draft/advisory flows it surfaced (name, kind, entry_url, status, flow_id, eval_score, detail, confirm_url). Confirm a draft flow (prufa_confirm_flow) to make it runnable.

Inputs: discovery_id (required).

prufa_get_findingA

Get the persisted findings for a run (flat, machine-readable). Pass finding_key to filter to a single finding.

Inputs: run_id (required), finding_key.

prufa_get_flowA

Get a single flow by id: its compiled spec, status (draft|confirmed), and the NAMES of any stored credentials (never their values).

Inputs: flow_id (required).

prufa_get_monitorB

Get one monitor's config + latest state (status, cadence, last run, deploy-hook metadata). [Pro]

Inputs: monitor_id (required).

prufa_get_reportA

Get the JSON report for a run. Accepts EITHER run_id (UUID from audit creation) OR share_token (the slug after /r/ in report_url). The share_token form is the recommended call shape — it is what the audit creation response returns.

Inputs: run_id, share_token.

prufa_get_runB

Get a run's status by id (queued|running|succeeded|failed|blocked|timeout).

Inputs: run_id (required).

prufa_get_usageA

Get this workspace's credit usage (available/included) plus trial state and, when relevant, an upsell block. Use before a costly run to check the balance and relay the message_for_human if credits are low.

Inputs: no named parameters.

prufa_get_workspaceA

Get the current workspace: tier, usage/credits, and trial state (days remaining, what gets gated when the trial ends). Includes an upsell block when the workspace is low on credits or near trial end.

Inputs: no named parameters.

prufa_gremlin_saved_loginsA

SENSITIVE — returns DECRYPTED email+password for logins previously used by gremlin runs in THIS workspace, so a kickoff can reuse them. Only for the owning workspace. Never print these values into logs, transcripts, or files; pass them straight into prufa_run_gremlin's credentials. [Pro]

Inputs: no named parameters.

prufa_health_checkA

Probe the Prufa API and MCP server. Always free, no token required.

Inputs: no named parameters.

prufa_list_alertsA

Alert history (delta-engine ledger), newest first — includes suppressed alerts with their suppression reason. [Pro]

Inputs: no named parameters.

prufa_list_discovery_domainsA

[Pro] List this workspace's discovery domains with id, domain, status (pending|verified), verified_at, verification_method, test_payments_opt_in, and (for pending domains) the verification TXT record to publish.

Inputs: no named parameters.

prufa_list_flowsA

List the flows in this workspace with their status (draft|confirmed) and metadata.

Inputs: no named parameters.

prufa_list_gremlin_domainsA

List the hosts this workspace has authorized for real gremlin mutations, with each host's allow_mutation flag, note, and created_at, plus the default policy. [Pro]

Inputs: no named parameters.

prufa_list_monitor_deliveriesA

List a monitor's last 50 deploy-hook deliveries plus copy-paste CI snippets (curl, github_actions, gitlab_ci). never_fired:true powers the 'your webhook never fired' nudge — surface it to the human. [Pro]

Inputs: monitor_id (required).

prufa_list_monitorsA

List every monitor in this workspace. [Pro]

Inputs: no named parameters.

prufa_list_runsC

List recent runs in this workspace (auth required).

Inputs: limit.

prufa_pause_monitorA

Pause a monitor — it stops running on its cadence until resumed. History is kept. Idempotent. [Pro]

Inputs: monitor_id (required), idempotency_key.

prufa_promote_gremlin_pathA

Import one reproduced gremlin path (by its path_index in the gremlin report) as a DRAFT flow. The flow still needs review + confirmation before it will run — this only creates the draft. Returns flow_id, status='draft', and a review_url. [Pro]

Inputs: path_index (required), share_token (required), idempotency_key.

prufa_register_discovery_domainA

[Pro] Register a domain for full-auto discovery and get the DNS TXT record to publish. For an unverified domain the response carries a 'verification' object {method, record_name, record_type:'TXT', record_value, hint} — publish that TXT record at your DNS provider, then call prufa_verify_discovery_domain. Set test_payments_opt_in to allow discovery to exercise test-mode payment flows. This DNS-ownership authorization is separate from gremlin mutation opt-in.

Inputs: domain (required), idempotency_key, test_payments_opt_in.

prufa_rerun_gremlinA

Re-dispatch a past gremlin run with the SAME intent (original url, persona, direction, and saved login) under the current tier's step cap. Returns a NEW run_id. wait=true (default) blocks until the rerun completes and returns the report; wait=false returns the queued state. [Pro]

Inputs: run_id (required), wait, idempotency_key.

prufa_resume_monitorB

Resume a paused monitor. The next scheduled run fires immediately, then it returns to its cadence. Idempotent. [Pro]

Inputs: monitor_id (required), idempotency_key.

prufa_revoke_discovery_domainA

[Pro] De-authorize a discovery domain. Future discovery on it is refused and any disposable identities created for it are torn down (the response reports identities_torn_down). Idempotent.

Inputs: domain_id (required), idempotency_key.

prufa_rotate_monitor_webhookA

Rotate a monitor's deploy-hook signing secret. The new secret is returned ONCE in the response — store it now; the old secret dies immediately, so update your CI before the next delivery. Idempotent. [Pro]

Inputs: monitor_id (required), idempotency_key.

prufa_run_auditA

Run a one-shot public-page QA audit on a URL. FREE — no key, no card (runs anonymously; a workspace token, if set, just attributes the run and lifts the per-IP limit). Returns findings JSON (broken flows, JS console errors, tracking/consent, security headers, a11y, mobile) graded A-F. Idempotent. wait=true (default) blocks until the audit completes and returns the report; wait=false returns the queued state with run_id + share_token to poll via prufa_get_report. An anonymous result carries a workspace_unlock block: deeper checks (flows, monitors, discovery, gremlin) need a free workspace (prufa_setup_workspace).

Inputs: url (required), wait.

prufa_run_discoveryA

[Pro] Start a full-auto discovery run on a URL. Crawls the site, infers user flows, and drafts the meaningful ones as reviewable draft flows. Requires a paid/trial tier AND a VERIFIED discovery domain covering the URL's host — otherwise the API returns 403 domain_not_authorized (register + verify the domain first) or 404 if discovery isn't enabled on the deployment. Returns {discovery_id, status, url, result_url}; poll with prufa_get_discovery.

Inputs: url (required), idempotency_key.

prufa_run_flowA

Execute a CONFIRMED flow. Returns 202 with run_id + report_url; poll the report via prufa_get_report. Pass per-run credentials as an object mapping the spec's {{VARIABLES}} to values ({'EMAIL': ..., 'PASSWORD': ...}) — these are encrypted in transit and NOT stored (use prufa_set_flow_credentials to store reusable ones). Fails if the flow is still a draft — confirm it first. Idempotent.

Inputs: flow_id (required), credentials, idempotency_key.

prufa_run_gremlinA

Run a gremlin chaos-QA session on a URL: an agent imitates a difficult user (no script) while plain-code detectors verify what breaks. Use to stress-test a real flow beyond the deterministic audit. Mutations are DRY-RUN unless the host is authorized via prufa_authorize_domain; payments are NEVER executed. Optional credentials (a real, non-payment login write) require a signed-in workspace AND mutation authorization for the host. Step budget depends on plan (free teaser 8, Starter 20, Pro 40, Team 60) — call prufa_get_usage for the cap. wait=true (default) blocks until the run completes (can take ~5 min) and returns the report; wait=false returns the queued state with run_id. [Pro]

Inputs: url (required), wait, persona, direction, +2 more.

prufa_set_flow_credentialsA

Store reusable, WRITE-ONLY credentials for a flow so later runs need not resend them. Pass flow_id and a non-empty credentials object mapping the spec's {{VARIABLES}} to values. The response lists the stored variable NAMES only — values are never returned. Idempotent.

Inputs: flow_id (required), credentials (required), idempotency_key.

prufa_set_notificationsA

Set the notification routing matrix: 'cells' is the 9-event x {email, slack} map of booleans deciding which channel each event fires on. The server validates keys and types (422 on unknown/missing keys or non-booleans) and returns {cells, locked_events} (events you can't turn off). [Pro]

Inputs: cells (required).

prufa_setup_workspaceA

Bootstrap or read the Prufa workspace this agent uses. If a token is already configured it returns the current workspace (with trial + upsell state). If NO token is set it CREATES a free 'agent_temp' workspace: no card, no charge, a 7-day trial with an included credit budget. During the trial you can run audits, monitors, discovery, and the full gremlin; after it ends monitors/discovery/gremlin_full_run are gated. The 201 response returns an api_token shown ONCE — persist it as PRUFA_API_TOKEN (or in ~/.config/prufa/mcp.json) and re-run with it set. When credits run low or the trial nears its end, tell your human to upgrade (prufa_upgrade_plan) or buy credits (prufa_buy_credits). Idempotent.

Inputs: name, owner_email, idempotency_key.

prufa_start_monitorA

Start a persistent monitor: re-run a QA audit on a URL on a cadence (daily|hourly) and fire a deploy hook on every regression delta. Pass flow_id to re-run a confirmed flow instead of the plain audit. 1-click setup — the response returns the deploy_hook (url + signing secret, shown ONLY once) which you should store immediately. [Pro] Free-tier workspaces get a 402 with a checkout hint that passes through; do not gate client-side. Idempotent.

Inputs: url (required), cadence, flow_id, idempotency_key.

prufa_trigger_monitorA

Trigger a monitor run right now (out of band). Rate-capped to 1 per 60s; if a run is already queued or running the response is deduped (deduped:true) instead of starting a second one. Idempotent. [Pro]

Inputs: monitor_id (required), idempotency_key.

prufa_upgrade_planA

Subscribe or upgrade this workspace to a paid plan (starter | pro | team). Returns a Stripe checkout_url the HUMAN opens in a browser to start the 7-day card-first trial — the agent never enters card details. Mutating + idempotent. [Pro]

Inputs: tier (required), cancel_url, success_url, idempotency_key.

prufa_verify_discovery_domainA

[Pro] Check the published DNS TXT proof for a registered discovery domain now. Idempotent — returns the domain body with status 'verified' once the TXT record resolves, or still 'pending' if DNS hasn't propagated yet (retry later).

Inputs: domain_id (required), idempotency_key.

prufa_workspace_settingsA

Update workspace settings — pass only the keys you want to change. Covers display_name, usage webhook (url/secret), overage opt-in, auto_recharge (auto-buys credits when a launch is blocked on an empty balance — needs a card on file), auto_recharge_credits / auto_recharge_monthly_limit_cents, and email/slack alert toggles. At least one setting is required. Idempotent. [Pro]

Inputs: display_name, auto_recharge, idempotency_key, opt_in_to_overage, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 44 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap. For example, prufa_create_flow, prufa_edit_flow, prufa_delete_flow, and prufa_confirm_flow are distinct actions on flows; similarly, prufa_run_audit, prufa_run_discovery, prufa_run_gremlin, and prufa_run_flow target different testing modalities. Monitor and billing tools are also well-separated.

    Naming Consistency5/5

    All tool names follow a consistent 'prufa_verb_noun' pattern in snake_case (e.g., prufa_list_flows, prufa_get_flow, prufa_setup_workspace). There is no mixing of styles or ambiguous verbs. The naming convention is predictable and aids tool selection.

    Tool Count4/5

    With 44 tools, the set is large but justified by the comprehensive nature of the QA platform, covering workspace management, flow lifecycle, monitors, discovery, gremlin testing, billing, and settings. While on the higher end, each tool serves a specific purpose and does not feel excessive for the domain.

    Completeness5/5

    The tool surface covers the full lifecycle of testing: workspace setup, flow creation/editing/deletion/confirmation/execution, monitoring with pause/resume/trigger/rotate, discovery with domain registration/verification/revocation, gremlin run/rerun, billing operations, and settings. No obvious gaps for the intended use case.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Browser-based QA testing for AI-built software. Agents open real browsers (via Selenium), navigate pages, fill forms, click buttons, and report findings. Two modes: targeted tests (30-90s) and full-site discovery scans (3-15min).
      -
    • A
      license
      B
      quality
      B
      maintenance
      Testing MCP for coding agents: exercise real user journeys, independently recheck suspected bugs, and export verified findings as Playwright regression tests. Includes browser interaction, goal coverage, evidence-linked reports, and optional local monitoring. The host agent supplies the model and judgment; Argus needs no separate provider key.
      29
      619 PyPI
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to see, measure, and verify web pages through a real Chrome browser, including screenshots, responsive layout and accessibility audits, pixel diffing against baselines, secure logins, and deployed-fix verification.
      27
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to audit rendered web pages for design and UI defects by measuring geometry, styles, contrast and motion in a local browser and judging them against evidence-tiered rules. Findings come back as short, fixable items expressed in the project's own design tokens, while only sanitized numeric measurements leave the machine.
      Apache 2.0

    Appeared in Searches