validoria-mcp

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

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

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

    How to connect

    How to connect validoria-mcp to Claude

    The server address to paste into Claude settings:

    https://api.teste.no/api/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect validoria-mcp to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.teste.no/api/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect validoria-mcp to Cursor

    The server address to paste into Cursor settings:

    https://api.teste.no/api/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (74)

    Raw names from tools/list. Only developers need these.

    guest_start_scanRun 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_scanPoll results for a guest_start_scan. Pass the scanId and guestSessionId from the start response. No API key required.
    list_targetsList all monitoring targets for your team. Returns name, URL, type, status, and uptime info for each target.
    get_targetGet detailed information about a specific target including status, uptime, fingerprint, and composite scores.
    get_target_scoresGet composite scores (Security, SEO, Performance, Accessibility) for a target. Each score is 0-100 with a status rating.
    list_findingsList findings (discovered issues) across your targets. Filter by status, severity, or target. Returns title, severity, status, test name, and AI enrichment if available.
    get_findingGet full details of a specific finding, including evidence, AI analysis, and recommended fix.
    list_incidentsList incidents (grouped operational issues) across your targets. Filter by status. Returns title, severity, status, findings count, and deployment correlation.
    get_incidentGet full details of a specific incident including linked findings, AI analysis, and deployment correlation.
    list_runsList recent test runs. Filter by target, status, or test slug. Returns run status, score, summary, duration, and finding count.
    get_runGet full details of a specific test run including metrics, score, summary, errors, and associated findings.
    active_runsGet currently running and queued tests across all targets. Useful for checking what tests are in progress right now.
    team_statsGet team-wide overview statistics: total runs, pass rate, open findings, open incidents, average duration. Supports lifetime, monthly, or weekly periods.
    target_statsGet statistics for a specific target: runs, pass rate, findings, duration. Supports lifetime, monthly, or weekly periods.
    daily_trendsGet 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_mapGet 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_windowsList maintenance windows for a target. Shows scheduled and recurring maintenance periods that suppress alerts.
    list_testsList 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_testRun 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_testsRun 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_incidentAcknowledge an open incident to signal that someone is looking at it. Changes status from OPEN to ACKNOWLEDGED.
    resolve_incidentResolve an incident to mark it as handled. Changes status to RESOLVED and sets the closed timestamp.
    mute_findingMute an open finding to suppress it from dashboards and alerts. Status changes from OPEN to MUTED.
    create_maintenance_windowSchedule a maintenance window for a target. During maintenance, alerts and notifications are suppressed. Supports one-time, daily, and weekly recurring windows.
    delete_maintenance_windowRemove a scheduled maintenance window.
    record_deploymentRecord 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_scoresForce recompute all composite scores (Security, SEO, Performance, Accessibility) for a target. Useful after manual changes or when scores seem stale.
    list_automation_rulesList 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_ruleGet full details of a specific automation rule.
    create_automation_ruleCreate 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_ruleUpdate an existing automation rule. Any field not provided will remain unchanged.
    delete_automation_rulePermanently delete an automation rule.
    list_journeysList 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_journeyGet full details of a specific journey including all steps.
    create_journeyCreate 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_journeyUpdate a journey's name, settings, or steps. When steps are provided, all existing steps are replaced.
    delete_journeyPermanently delete a journey and all its steps.
    trigger_journeyExecute a journey (custom browser test flow) against its target. The journey runs asynchronously — use get_run to check progress.
    list_scheduled_reportsList all scheduled reports for the team. Reports are automatically generated and emailed on a daily or weekly basis.
    create_scheduled_reportCreate a new scheduled email report. Reports include run stats, open findings, composite scores, and per-target status.
    update_scheduled_reportUpdate an existing scheduled report. Any field not provided stays unchanged.
    delete_scheduled_reportPermanently delete a scheduled report.
    get_team_settingsGet the team's configuration including AI enrichment, uptime monitoring, severity escalation, run policies, notification coalescing, SEO, and Kloner Tasks integration settings.
    update_team_settingsUpdate 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).
    list_notification_rulesList all notification alert rules for the team. Rules map event types + severity levels to notification channels.
    create_notification_ruleCreate 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_ruleUpdate a notification rule. Only provided fields are changed.
    delete_notification_rulePermanently delete a notification rule.
    list_notification_channelsList all notification channels (Email, Slack, Webhook, SMS, Web Push) configured for the team. Sensitive config values are redacted.
    list_keywordsList all SEO keywords tracked for a target, including latest Google rank position. Max 50 per target.
    add_keywordAdd an SEO keyword to track for a target. Max 50 keywords per target.
    remove_keywordRemove an SEO keyword from a target.
    start_load_testStart 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_testCancel a running load test.
    get_load_testGet details and results of a load test run.
    list_load_testsList recent load test runs for a target.
    list_secretsList 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_secretStore 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_secretUpdate the value of an existing secret.
    delete_secretPermanently delete a secret from a target's vault.
    list_page_fragmentsList 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_fragmentCreate a reusable step sequence that can be shared across multiple Journeys. Fragment names must be unique per team.
    update_page_fragmentUpdate a page fragment. When steps are provided, all existing steps are replaced.
    delete_page_fragmentPermanently delete a page fragment.
    create_targetAdd 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_targetUpdate a target's properties (name, URL, type, environment, business weight, tags, uptime toggle).
    delete_targetPermanently delete a target and all its associated data (runs, findings, incidents, artifacts). This cannot be undone.
    analyze_targetFingerprint 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.
    import_targetsBulk 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_ruleCreate 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_healthGet a comprehensive system health report: BullMQ queue depths, active/stuck runs, user sessions, notification delivery stats, and recent error counts. Requires admin scope.
    update_testEnable or disable a test definition globally, or update its schedule/timeout. Requires admin scope.
    enable_all_testsEnable all test definitions globally. Optionally filter by category to only enable tests in that category. Requires admin scope.
    disable_all_testsDisable all test definitions globally. Optionally filter by category to only disable tests in that category. Requires admin scope.