Is the Validoria MCP server down?

mcp-registry/com.validoria/validoria-mcp · v1.0.0

healthy
Last checked 2026-10-26 18:21 UTC · handshake 587ms

As of 2026-10-26 18:21 UTC, the Validoria MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.9%
checks observed
4,947
outages (90d)
24
tools
78

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

Point your MCP client at this streamable-http endpoint: https://api.teste.no/api/mcp

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 6 warning(s) across 78 tool(s); ~15,814 tokens of tool definitions.
Scores higher than 4% of 15,768 MCP servers Glimind has audited.
Its tool list costs an agent ~15,814 tokens per session — more than 85% of servers.
66 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions88
Safety hints0
Token cost64
Client compatibility70
Protocol100
Reliability85
Stability68

What to fix (8)

1 tool definition(s) exceed ~1,200 tokens each (largest: update_team_settings, ~1,229).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~629 tokens every session. How to fix →

Tools: update_team_settings · saves ~629 tokens/session

78 of 78 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: accept_visual_baseline, acknowledge_incident, active_runs, add_keyword, analyze_target and 73 more

78 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

29 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: active_runs, cancel_load_test, create_automation_rule, create_journey, create_maintenance_window and 24 more

8 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: update_notification_rule, update_page_fragment

Handshake + tools/list takes ~1,934 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 8 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 69 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp/fixes

active_runs 1 change
{
  "name": "active_runs",
  "description": "Get currently running and queued tests across all targets. Useful for checking what tests are in progress right now.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "targetId": {
        "type": "string",
        "description": "Filter by target ID"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Active Runs"
}
add_keyword 1 change
{
  "name": "add_keyword",
  "description": "Add an SEO keyword to track for a target, optionally for one page (pageUrl). Max 50 keywords per target.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "targetId",
      "keyword"
    ],
    "properties": {
      "keyword": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1,
        "description": "The keyword to track"
      },
      "pageUrl": {
        "type": "string",
        "format": "uri",
        "maxLength": 2048,
        "description": "The page this keyword is written for (absolute URL on the site)"
      },
      "targetId": {
        "type": "string",
        "description": "The target ID"
      },
      "isPrimary": {
        "type": "boolean",
        "default": false,
        "description": "Mark as primary keyword"
      },
      "pageScope": {
        "type": "string",
        "maxLength": 500,
        "description": "URL pathname pattern to scope the keyword to (e.g. /kategori/*)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add Keyword"
}
analyze_target 1 change
{
  "name": "analyze_target",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "format": "uri",
        "description": "URL to analyze, e.g. \"https://example.com\""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Analyze Target"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.validoria/validoria-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.validoria/validoria-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.validoria%2Fvalidoria-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:db4c5238b3c438e1…, first seen 2026-10-26, included at leaf 72536 of 74,681. Version history · verify what your client received.

Tools (78)

Compare: most reliable devops servers · most reliable communication servers · most reliable data servers · most reliable other servers · most reliable web servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Validoria MCP server down right now?

As of 2026-10-26 18:21 UTC, the Validoria MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Validoria MCP server provide?

Validoria MCP server advertises 78 tools, including accept_visual_baseline, acknowledge_incident, active_runs, add_keyword, analyze_target.

How do I install Validoria MCP server?

Point your MCP client at this streamable-http endpoint: https://api.teste.no/api/mcp

Is the Validoria MCP server safe to connect to an AI agent?

Glimind scanned all 78 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Validoria MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve