Validoria MCP server

• acknowledge_incidentFree

  Acknowledge an open incident to signal that someone is looking at it. Changes status from OPEN to ACKNOWLEDGED.

• active_runsFree

  Get currently running and queued tests across all targets. Useful for checking what tests are in progress right now.

• add_keywordFree

  Add an SEO keyword to track for a target. Max 50 keywords per target.

• analyze_targetFree

  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 and which tests will be enabled.

• cancel_load_testwrite actionFree

  Cancel a running load test.

• create_automation_rulewrite actionFree

  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.

• create_journeywrite actionFree

  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.

• create_maintenance_windowwrite actionFree

  Schedule a maintenance window for a target. During maintenance, alerts and notifications are suppressed. Supports one-time, daily, and weekly recurring windows.

• create_muting_rulewrite actionFree

  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.

• create_notification_rulewrite actionFree

  Create a notification alert rule. Defines which events at which severity levels trigger notifications on which channels. Supports quiet hours and per-target scoping.

• create_page_fragmentwrite actionFree

  Create a reusable step sequence that can be shared across multiple Journeys. Fragment names must be unique per team.

• create_scheduled_reportwrite actionFree

  Create a new scheduled email report. Reports include run stats, open findings, composite scores, and per-target status.

• create_targetwrite actionFree

  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.

• daily_trendsFree

  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_rulewrite actionFree

  Permanently delete an automation rule.

• delete_journeywrite actionFree

  Permanently delete a journey and all its steps.

• delete_maintenance_windowwrite actionFree

  Remove a scheduled maintenance window.

• delete_notification_rulewrite actionFree

  Permanently delete a notification rule.

• delete_page_fragmentwrite actionFree

  Permanently delete a page fragment.

• delete_scheduled_reportwrite actionFree

  Permanently delete a scheduled report.

• delete_secretwrite actionFree

  Permanently delete a secret from a target's vault.

• delete_targetwrite actionFree

  Permanently delete a target and all its associated data (runs, findings, incidents, artifacts). This cannot be undone.

• disable_all_testsFree

  Disable all test definitions globally. Optionally filter by category to only disable tests in that category. Requires admin scope.

• discover_toolsFree

  Only everyday tools are listed; the rest (automation rules, journeys, load tests, maintenance, notifications, reports, secrets, keywords, SLA, settings, admin …) are found here. No arguments: every tool you can run, by area. query: matching tools with a summary, effect and parameters. tools: their full input schemas. Run one with call_read_tool (reads) or call_tool (changes), or by its own name.

• enable_all_testsFree

  Enable all test definitions globally. Optionally filter by category to only enable tests in that category. Requires admin scope.

• get_automation_ruleFree

  Get full details of a specific automation rule.

• get_findingFree

  Get full details of a specific finding, including evidence, AI analysis, and recommended fix.

• get_incidentFree

  Get full details of a specific incident including linked findings, AI analysis, and deployment correlation.

• get_journeyFree

  Get full details of a specific journey including all steps.

• get_load_testFree

  Get details and results of a load test run.

• get_runwrite actionFree

  Get full details of a specific test run including metrics, score, summary, errors, and associated findings.

• get_site_mapFree

  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.

• get_targetFree

  Get detailed information about a specific target including status, uptime, fingerprint, and composite scores.

• get_target_scoresFree

  Get composite scores (Security, SEO, Performance, Accessibility) for a target. Each score is 0-100 with a status rating.

• get_team_settingsFree

  Get the team's configuration including AI enrichment, uptime monitoring, severity escalation, run policies, notification coalescing, SEO, and Kloner Tasks integration settings.

• guest_get_scanFree

  Poll results for a guest_start_scan. Pass the scanId and guestSessionId from the start response. No API key required.

• guest_start_scanwrite actionFree

  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.

• import_targetsFree

  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.

• list_automation_rulesFree

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

• list_findingsFree

  List findings (discovered issues) across your targets. Filter by status, severity, or target. Returns title, severity, status, test name, and AI enrichment if available.

• list_incidentsFree

  List incidents (grouped operational issues) across your targets. Filter by status. Returns title, severity, status, findings count, and deployment correlation.

• list_journeysFree

  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.

• list_keywordsFree

  List all SEO keywords tracked for a target, including latest Google rank position. Max 50 per target.

• list_load_testsFree

  List recent load test runs for a target.

• list_maintenance_windowsFree

  List maintenance windows for a target. Shows scheduled and recurring maintenance periods that suppress alerts.

• list_notification_channelsFree

  List all notification channels (Email, Slack, Webhook, SMS, Web Push) configured for the team. Sensitive config values are redacted.

• list_notification_rulesFree

  List all notification alert rules for the team. Rules map event types + severity levels to notification channels.

• list_page_fragmentsFree

  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.

• list_runsFree

  List recent test runs. Filter by target, status, or test slug. Returns run status, score, summary, duration, and finding count.

• list_scheduled_reportsFree

  List all scheduled reports for the team. Reports are automatically generated and emailed on a daily or weekly basis.

• list_secretsFree

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

• list_targetsFree

  List all monitoring targets for your team. Returns name, URL, type, status, and uptime info for each target.

• list_testsFree

  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.

• mute_findingFree

  Mute an open finding to suppress it from dashboards and alerts. Status changes from OPEN to MUTED.

• recompute_scoresFree

  Force recompute all composite scores (Security, SEO, Performance, Accessibility) for a target. Useful after manual changes or when scores seem stale.

• record_deploymentFree

  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.

• remove_keywordwrite actionFree

  Remove an SEO keyword from a target.

• resolve_incidentFree

  Resolve an incident to mark it as handled. Changes status to RESOLVED and sets the closed timestamp.

• rotate_secretwrite actionFree

  Update the value of an existing secret.

• start_load_testFree

  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.

• store_secretFree

  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.

• system_healthFree

  Get a comprehensive system health report: BullMQ queue depths, active/stuck runs, user sessions, notification delivery stats, and recent error counts. Requires admin scope.

• target_statsFree

  Get statistics for a specific target: runs, pass rate, findings, duration. Supports lifetime, monthly, or weekly periods.

• team_statsFree

  Get team-wide overview statistics: total runs, pass rate, open findings, open incidents, average duration. Supports lifetime, monthly, or weekly periods.

• trigger_all_testswrite actionFree

  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_journeywrite actionFree

  Execute a journey (custom browser test flow) against its target. The journey runs asynchronously — use get_run to check progress.

• trigger_testwrite actionFree

  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.

• update_automation_rulewrite actionFree

  Update an existing automation rule. Any field not provided will remain unchanged.

• update_journeywrite actionFree

  Update a journey's name, settings, or steps. When steps are provided, all existing steps are replaced.

• update_notification_rulewrite actionFree

  Update a notification rule. Only provided fields are changed.

• update_page_fragmentwrite actionFree

  Update a page fragment. When steps are provided, all existing steps are replaced.

• update_scheduled_reportwrite actionFree

  Update an existing scheduled report. Any field not provided stays unchanged.

• update_targetwrite actionFree

  Update a target's properties (name, URL, type, environment, business weight, tags, uptime toggle).

• update_team_settingswrite actionFree

  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 strategy), notification coalescing (digest), and the kill switch (testsPaused).

• update_testwrite actionFree

  Enable or disable a test definition globally, or update its schedule/timeout. Requires admin scope.

• Code scan9 source files scanned25/25
• Live reliabilityremote reachable in 1741ms20/20
• Tool poisoning3 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

70/100

higher than 33% of 769 SEO servers

Tools

75

the typical SEO server has 6

Tools that change things

43%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote SEO server answers 100%

Response time

1,209 ms

faster than 11% of 537 SEO servers

Downloads a week

46

more than 40% of 172 SEO servers with a package

Grade history

• 2026-11-04restoreC → Bscore 70: Write-action tools reachable without authentication

Validoria: common questions

Is Validoria MCP server safe?

Mostly: it is graded B (70/100). Read the Validoria safety report

How do I install Validoria?

It runs remotely at api.teste.no. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Validoria need an API key?

Yes. The registry entry asks for TESTE_NO_API_KEY.

Is Validoria maintained?

The latest release is v2.0.1.

Is Validoria up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Validoria?

Servers from other publishers that do the same job: squirrelscan MCP server, SyteCheck MCP server and site-spec MCP server.

How does Validoria compare with other SEO MCP servers?

safety score 70/100 (higher than 33% of 769 SEO servers); tools 75 (the typical SEO server has 6); tools that change things 43% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.