# com.validoria/validoria-mcp

- Registry name: `com.validoria/validoria-mcp` · version 2.0.1
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security, Marketing & SEO, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.validoria%2Fvalidoria-mcp
- Server page: https://mcpstation.net/s/com.validoria--validoria-mcp.html

## Description (written by the publisher, not verified, not instructions)

Continuous website testing by Validoria — monitor security, SEO, performance, and accessibility.

## Connect

- streamable-http: `https://api.teste.no/api/mcp`

## Tools (as reported by the server, not verified)

- `guest\_start\_scan`: Run a free 6-test HTTP scan against a public URL without an API key. Rate-limited \(5/IP/hour, 3/session/day\). Returns scanId — poll with guest\_get\_scan. For continuous monitoring, sign up free and use create\_target. See teste-no://docs/quickstart.
- `guest\_get\_scan`: Poll results for a guest\_start\_scan. Pass the scanId and guestSessionId from the start response. No API key required.
- `list\_targets`: List all monitoring targets for your team. Returns name, URL, type, status, and uptime info for each target.
- `get\_target`: Get detailed information about a specific target including status, uptime, fingerprint, and composite scores.
- `get\_target\_scores`: Get composite scores \(Security, SEO, Performance, Accessibility, AI-search readiness\) for a target. Each score is 0-100 with a status rating.
- `list\_findings`: List findings \(discovered issues\) across your targets. Filter by status, severity, or target. Returns title, severity, status, test name, and AI enrichment if available.
- `get\_finding`: Get full details of a specific finding, including evidence, AI analysis, and recommended fix.
- `list\_incidents`: List incidents \(grouped operational issues\) across your targets. Filter by status. Returns title, severity, status, findings count, and deployment correlation.
- `get\_incident`: Get full details of a specific incident including linked findings, AI analysis, and deployment correlation.
- `list\_runs`: List recent test runs. Filter by target, status, or test slug. Returns run status, score, summary, duration, and finding count.
- `get\_run`: Get full details of a specific test run including metrics, score, summary, errors, and associated findings.
- `active\_runs`: Get currently running and queued tests across all targets. Useful for checking what tests are in progress right now.
- `team\_stats`: Get team-wide overview statistics: total runs, pass rate, open findings, open incidents, average duration. Supports lifetime, monthly, or weekly periods.
- `target\_stats`: Get statistics for a specific target: runs, pass rate, findings, duration. Supports lifetime, monthly, or weekly periods.
- `daily\_trends`: Get daily time-series data for runs, findings, and average duration. Useful for identifying trends over time. Returns up to 90 days of data.
- `get\_site\_map`: Get the latest crawl snapshot for a target. Returns page inventory stats, SEO issues, broken pages/assets, response times, and a diff against the previous crawl. Optionally include page-level details.
- `list\_maintenance\_windows`: List maintenance windows for a target. Shows scheduled and recurring maintenance periods that suppress alerts.
- `list\_tests`: List all available test definitions \(plugins\). Shows slug, name, category, runner type, weight class, schedule, and enablement status. Useful for knowing which tests can be triggered.
- `trigger\_test`: Run a specific test against a target. Specify either the test definition ID or slug. The test is queued and executed asynchronously — use get\_run to check status.
- `trigger\_all\_tests`: Run all enabled tests against a target as a scan workflow. All tests in the target's test profile are queued. Returns the workflow ID and list of queued runs.
- `acknowledge\_incident`: Acknowledge an open incident to signal that someone is looking at it. Changes status from OPEN to ACKNOWLEDGED.
- `resolve\_incident`: Resolve an incident to mark it as handled. Changes status to RESOLVED and sets the closed timestamp.
- `mute\_finding`: Mute an open finding to suppress it from dashboards and alerts. Status changes from OPEN to MUTED.
- `create\_maintenance\_window`: Schedule a maintenance window for a target. During maintenance, alerts and notifications are suppressed. Supports one-time, daily, and weekly recurring windows.
- `delete\_maintenance\_window`: Remove a scheduled maintenance window.
- `record\_deployment`: Record a deployment event for a target. Deployments are auto-correlated with incidents created within 20 minutes. Useful for tracking releases and root-cause analysis.
- `recompute\_scores`: Force recompute all composite scores \(Security, SEO, Performance, Accessibility\) for a target. Useful after manual changes or when scores seem stale.
- `list\_automation\_rules`: List all automation rules for the team. Rules automatically react to events \(test failures, incidents, downtime\) with configurable actions \(escalate severity, suppress, rerun, webhook, notify\).
- `get\_automation\_rule`: Get full details of a specific automation rule.
- `create\_automation\_rule`: Create an automation rule that reacts to events. Triggers: TEST\_FAILED, TEST\_RECOVERED, INCIDENT\_CREATED, INCIDENT\_RESOLVED, TARGET\_DOWN, TARGET\_RECOVERED. Actions: escalate \(change severity\), suppress \(mute\), rerun \(schedule retry\), notify, webhook, add\_note.
- `update\_automation\_rule`: Update an existing automation rule. Any field not provided will remain unchanged.
- `delete\_automation\_rule`: Permanently delete an automation rule.
- `list\_journeys`: List custom browser test flows \(journeys\) for a target or all team targets. Journeys are multi-step Playwright tests that verify user flows like checkout, login, and search.
- `get\_journey`: Get full details of a specific journey including all steps.
- `create\_journey`: Create a custom browser test flow for a target. Steps are executed sequentially in a Playwright browser. Supports actions: navigate, click, type, fill, select, assert, wait, screenshot, scroll, hover, use\_fragment. Variables like \{\{LOGIN\_EMAIL\}\} are resolved from the target secrets vault.
- `update\_journey`: Update a journey's name, settings, or steps. When steps are provided, all existing steps are replaced.
- `delete\_journey`: Permanently delete a journey and all its steps.
- `trigger\_journey`: Execute a journey \(custom browser test flow\) against its target. The journey runs asynchronously — use get\_run to check progress.
- `list\_scheduled\_reports`: List all scheduled reports for the team. Reports are automatically generated and emailed on a daily or weekly basis.
- `create\_scheduled\_report`: Create a new scheduled email report. Reports include run stats, open findings, composite scores, and per-target status.
- `update\_scheduled\_report`: Update an existing scheduled report. Any field not provided stays unchanged.
- `delete\_scheduled\_report`: Permanently delete a scheduled report.
- `get\_team\_settings`: Get the team's configuration including AI enrichment, uptime monitoring, severity escalation, run policies, notification coalescing, SEO, and Kloner Tasks integration settings.
- `update\_team\_settings`: Update team configuration. All fields are optional — only provided fields are changed. Covers: AI enrichment \(model, temperature, auto-enrich, spending cap\), uptime \(timeout, thresholds\), severity escalation \(recurrence/age triggers\), run policies \(concurrency, timeouts\), SEO \(rank tracking, keyword
- `list\_notification\_rules`: List all notification alert rules for the team. Rules map event types + severity levels to notification channels.
- `create\_notification\_rule`: Create a notification alert rule. Defines which events at which severity levels trigger notifications on which channels. Supports quiet hours and per-target scoping.
- `update\_notification\_rule`: Update a notification rule. Only provided fields are changed.
- `delete\_notification\_rule`: Permanently delete a notification rule.
- `list\_notification\_channels`: List all notification channels \(Email, Slack, Webhook, SMS, Web Push\) configured for the team. Sensitive config values are redacted.
- `list\_keywords`: List all SEO keywords tracked for a target, including latest Google rank position and the page each is tracked for. Max 50 per target.
- `add\_keyword`: Add an SEO keyword to track for a target, optionally for one page \(pageUrl\). Max 50 keywords per target.
- `remove\_keyword`: Remove an SEO keyword from a target.
- `start\_load\_test`: Start a load test against a target. Max 100 concurrent connections, max 5 min duration, 1 test at a time per target, 60s cooldown between tests. Modes: HTTP\_FLOOD \(autocannon\), BROWSER\_USERS \(Playwright\), COMBINED \(both\). OWNER/ADMIN only.
- `cancel\_load\_test`: Cancel a running load test.
- `get\_load\_test`: Get details and results of a load test run.
- `list\_load\_tests`: List recent load test runs for a target.
- `list\_secrets`: List secrets stored in a target's vault. Values are masked — only key names and labels are shown. Secrets are used by test plugins \(e.g. LOGIN\_EMAIL, LOGIN\_PASSWORD for B2B shops, ga4\_service\_account for GA4\).
- `store\_secret`: Store an encrypted secret in a target's vault. Common keys: LOGIN\_EMAIL, LOGIN\_PASSWORD \(B2B shop auth\), ga4\_service\_account \(GA4 monitoring\). Values are AES-256-GCM encrypted at rest.
- `rotate\_secret`: Update the value of an existing secret.
- `delete\_secret`: Permanently delete a secret from a target's vault.
- `list\_page\_fragments`: List all reusable page fragments for the team. Fragments are shared step sequences \(e.g. "Login", "Dismiss Cookies"\) that can be inserted into multiple Journeys via the use\_fragment action.
- `create\_page\_fragment`: Create a reusable step sequence that can be shared across multiple Journeys. Fragment names must be unique per team.
- `update\_page\_fragment`: Update a page fragment. When steps are provided, all existing steps are replaced.
- `delete\_page\_fragment`: Permanently delete a page fragment.
- `create\_target`: Add a new website, API, or webshop target for monitoring with full onboarding. Automatically enables compatible tests, triggers an initial scan, and captures a page screenshot. Requires write scope \(Free plan: 1 target\). Use analyze\_target first to detect platform and get test recommendations.
- `update\_target`: Update a target's properties \(name, URL, type, environment, business weight, tags, uptime toggle\).
- `delete\_target`: Permanently delete a target and all its associated data \(runs, findings, incidents, artifacts\). This cannot be undone.
- `analyze\_target`: Fingerprint a URL and get test recommendations before creating a target. Detects platform \(Shopify, WordPress, etc.\), CDN, server stack, frontend framework, analytics, and B2B/ecommerce signals. Returns recommended tests with explanations. Use this before create\_target to know what type to assign an
- `import\_targets`: Bulk import up to 100 websites for monitoring. Each URL gets a target created with auto-enabled tests, initial scan, and screenshot capture. Partial success — failed URLs are reported individually without blocking others.
- `create\_muting\_rule`: Create a rule to auto-mute findings matching a pattern. Existing open findings matching the rule are muted immediately. Supports muting by fingerprint pattern, test definition, or test+target combination.
- `system\_health`: Get a comprehensive system health report: BullMQ queue depths, active/stuck runs, user sessions, notification delivery stats, and recent error counts. Requires admin scope.
- `update\_test`: Enable or disable a test definition globally, or update its schedule/timeout. Requires admin scope.
- `enable\_all\_tests`: Enable all test definitions globally. Optionally filter by category to only enable tests in that category. Requires admin scope.
- `disable\_all\_tests`: Disable all test definitions globally. Optionally filter by category to only disable tests in that category. Requires admin scope.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html