Validoria MCP

Last 30 days

Uptime

100%

Response time

175 ms typical, 175 ms slowest 5%

Last check

7 h ago

Next check

any minute now

How to call it

Add it to any MCP client that supports remote servers.

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

74 tools

• 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 secre

• 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.

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks