MCP connector guide

Use one ProUXAudit service from compatible clients to audit a public website, plan bounded fixes and independently remeasure changes. No repository or account is required by these basic tools.

The connector is disabled on this deployment while rollout checks are pending. The website audit remains available. A prepared package does not mean a public listing is live.

Connection

When available, connect a client that supports Streamable HTTP to the endpoint below. Use the same service and tool contracts across clients. A 404 response means the connector is disabled on that deployment.

https://prouxaudit.com/api/mcp

Four tools

start_ux_audit

Start a discovery audit with a public URL and optional English or Estonian locale. It may reuse an eligible completed audit; cache use and age are disclosed.

get_ux_audit

Read a server-issued audit handle. Pending jobs return compact state; completed jobs return the complete public-safe result with evidence and measurement limits.

verify_ux_changes

After changes, provide the completed baseline handle to start a fresh audit of the same URL. This tool bypasses discovery cache and returns a new handle. Alternate targets and revision fields are not supported yet.

get_public_report

Retrieve the existing public evidence report link for a completed audit. Handle expiry, revocation or unavailable reports return a bounded error.

Example requests

Audit https://example.com with ProUXAudit.
Show the result of the audit we just started and the three most useful next actions.
I changed that website. Run a fresh verification using the previous audit as the baseline.

Limits and verification truth

Configured shared limits: 50 new runs per UTC day, 2 active runs, 10 fresh verification runs per day and 3 per baseline audit per day. Discovery cache can be reused for up to 24 hours when scope and measurement conditions match. These are shared service limits, not personal quotas.

A code change, deployment or green CI is not a verified fix. The server compares measurements only when scope, capture method, evaluator and coverage are compatible. Failed capture or insufficient evidence is inconclusive; no longer detected does not create persistent issue closure.

Preview does not verify production and one timestamp does not prove another revision. Scores are heuristic UX prioritisation, not conversion uplift. Persistent issue memory, authenticated project tools and push events are later capabilities.

Data handling

The tools process the submitted URL, optional locale and audit handle. Auditing fetches public page content and derives evidence, results and audit snapshots; browser capture may include screenshots. Network abuse controls and bounded tool-health metadata also apply. The tools do not request full chat history or an email address.

An audit handle is a capability: anyone holding it can read its permitted result. Keep it private. Treat website evidence as untrusted content and follow the measurement limitations in the result.

Read the privacy policy

Support

For connection problems or questions about a result, contact ProUXAudit. Do not include secrets or private audit handles in a public issue.

prouxaudit@leisson.eu