# Validoria MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp
Registry id: `mcp-registry/com.validoria/validoria-mcp`
Status: live (checked 2026-10-26T19:11:31.880Z)

## Measurements (30 days)

- Uptime: 99.91%
- Checks: 4957
- Outages (90 days): 24

## Install

```json
{
  "mcpServers": {
    "validoria-mcp-server": {
      "type": "http",
      "url": "https://api.teste.no/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http validoria-mcp-server https://api.teste.no/api/mcp
```

## Tools (78)

- `accept_visual_baseline`: Accept the new look: make a finished visual-regression run's screenshots the baselines later runs compare with, then queue a new run, which closes the visual-ch
- `acknowledge_incident`: Acknowledge an open incident to signal that someone is looking at it. Changes status from OPEN to ACKNOWLEDGED.
- `active_runs`: Get currently running and queued tests across all targets. Useful for checking what tests are in progress right now.
- `add_keyword`: Add an SEO keyword to track for a target, optionally for one page (pageUrl). Max 50 keywords per target.
- `analyze_target`: Fingerprint a URL and get test recommendations before creating a target. Detects platform (Shopify, WordPress, etc.), CDN, server stack, frontend framework, ana
- `cancel_load_test`: Cancel a running load test.
- `create_automation_rule`: Create an automation rule that reacts to events. Triggers: TEST_FAILED, TEST_RECOVERED, INCIDENT_CREATED, INCIDENT_RESOLVED, TARGET_DOWN, TARGET_RECOVERED. Acti
- `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, 
- `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.
- `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, 
- `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 sco
- `create_page_fragment`: Create a reusable step sequence that can be shared across multiple Journeys. Fragment names must be unique per team.
- `create_scheduled_report`: Create a new scheduled email report. Reports include run stats, open findings, composite scores, and per-target status.
- `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 
- `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.
- `delete_automation_rule`: Permanently delete an automation rule.
- `delete_journey`: Permanently delete a journey and all its steps.
- `delete_maintenance_window`: Remove a scheduled maintenance window.
- `delete_notification_rule`: Permanently delete a notification rule.
- `delete_page_fragment`: Permanently delete a page fragment.
- `delete_scheduled_report`: Permanently delete a scheduled report.
- `delete_secret`: Permanently delete a secret from a target's vault.
- `delete_target`: Permanently delete a target and all its associated data (runs, findings, incidents, artifacts). This cannot be undone.
- `disable_all_tests`: Disable all test definitions globally. Optionally filter by category to only disable tests in that category. 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.
- `get_automation_rule`: Get full details of a specific automation rule.
- `get_finding`: Get full details of a specific finding, including evidence, AI analysis, and recommended fix.
- `get_incident`: Get full details of a specific incident including linked findings, AI analysis, and deployment correlation.
- `get_journey`: Get full details of a specific journey including all steps.
- `get_load_test`: Get details and results of a load test run.
- `get_run`: Get full details of a specific test run including metrics, score, summary, errors, and associated findings.
- `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
- `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, AI visibility) for a target. Each score is 0-100 with a status rating, wei
- `get_target_sla`: A target's SLA contract (guaranteed uptime per UTC calendar month, whether DEGRADED counts as down, optional p95 response objective) and its error budget: allow
- `get_team_settings`: Get the team's configuration including AI enrichment, uptime monitoring, severity escalation, run policies, notification coalescing, SEO, and Kloner Tasks integ
- `guest_get_scan`: Poll results for a guest_start_scan. Pass the scanId and guestSessionId from the start response. No API key required.
- `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 con
- `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 — f
- `list_automation_rules`: List all automation rules for the team. Rules automatically react to events (test failures, incidents, downtime) with configurable actions (escalate severity, s
- `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 a
- `list_incidents`: List incidents (grouped operational issues) across your targets. Filter by status. Returns title, severity, status, findings count, and deployment correlation.
- `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
- `list_keywords`: List all SEO keywords tracked for a target, including latest Google rank position, the page each is tracked for, and searchConsole28d: Impressions (Search Conso
- `list_load_tests`: List recent load test runs for a target.
- `list_maintenance_windows`: List maintenance windows for a target. Shows scheduled and recurring maintenance periods that suppress alerts.
- `list_notification_channels`: List all notification channels (Email, Slack, Webhook, SMS, Web Push) configured for the team. Sensitive config values are redacted.
- `list_notification_rules`: List all notification alert rules for the team. Rules map event types + severity levels to notification channels.
- `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
- `list_runs`: List recent test runs. Filter by target, status, or test slug. Returns run status, score, summary, duration, and finding count.
- `list_scheduled_reports`: List all scheduled reports for the team. Reports are automatically generated and emailed on a daily or weekly basis.
- `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_PASS
- `list_targets`: List all monitoring targets for your team. Returns name, URL, type, status, and uptime info for each target.
- `list_tests`: List all available test definitions (plugins). Shows slug, name, category, runner type, weight class, schedule, and enablement status. Useful for knowing which 
- `list_visual_baselines`: The baseline screenshots visual-regression compares a target with, one per viewport and page: when each was taken, and whether a person accepted it (acceptedAt)
- `mute_finding`: Mute an open finding to suppress it from dashboards and alerts. Status changes from OPEN to MUTED.
- `recompute_scores`: Force recompute all composite scores (Security, SEO, Performance, Accessibility, AI-search readiness) and their evidence coverage for a target. Useful after man
- `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 an
- `remove_keyword`: Remove an SEO keyword from a target.
- `resolve_incident`: Resolve an incident to mark it as handled. Changes status to RESOLVED and sets the closed timestamp.
- `rotate_secret`: Update the value of an existing secret.
- `set_target_test`: Turn one test on or off for one target, and set its per-target config and schedule. config replaces the target's config for that test (null clears it; keys are 
- `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_FLO
- `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-25
- `system_health`: Get a comprehensive system health report: BullMQ queue depths, active/stuck runs, user sessions, notification delivery stats, and recent error counts. Per queue
- `target_stats`: Get statistics for a specific target: runs, pass rate, findings, duration. Supports lifetime, monthly, or weekly periods.
- `team_stats`: Get team-wide overview statistics: total runs, pass rate, open findings, open incidents, average duration. Supports lifetime, monthly, or weekly periods.
- `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.
- `trigger_journey`: Execute a journey (custom browser test flow) against its target. The journey runs asynchronously — use get_run to check progress.
- `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 statu
- `update_automation_rule`: Update an existing automation rule. Any field not provided will remain unchanged.
- `update_journey`: Update a journey's name, settings, or steps. When steps are provided, all existing steps are replaced.
- `update_notification_rule`: Update a notification rule. Only provided fields are changed.
- `update_page_fragment`: Update a page fragment. When steps are provided, all existing steps are replaced.
- `update_scheduled_report`: Update an existing scheduled report. Any field not provided stays unchanged.
- `update_target`: Update a target's properties (name, URL, type, environment, business weight, tags, uptime toggle).
- `update_team_settings`: Update team configuration. All fields are optional — only provided fields are changed. Covers: AI enrichment (model, temperature, auto-enrich, spending cap), up
- `update_test`: Enable or disable a test definition globally, or update its schedule/timeout. Requires admin scope.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.