Should my agent depend on the MCP server com.validoria/validoria-mcp?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

validoria mcp

com.validoria/validoria-mcp

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

— the operator's own registry description reported

Publisher com.validoria · first seen 2026-08-12 · endpoint https://api.teste.no/api/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.935 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency1098 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools74

vs populationhigh

capabilities4

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_a9a4fd35e4fcc2260413f009 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

acknowledge_incident active_runs add_keyword analyze_target cancel_load_test create_automation_rule create_journey create_maintenance_window create_muting_rule create_notification_rule create_page_fragment create_scheduled_report create_target daily_trends delete_automation_rule delete_journey delete_maintenance_window delete_notification_rule delete_page_fragment delete_scheduled_report delete_secret delete_target disable_all_tests enable_all_tests get_automation_rule get_finding get_incident get_journey get_load_test get_run get_site_map get_target get_target_scores get_team_settings guest_get_scan guest_start_scan import_targets list_automation_rules list_findings list_incidents list_journeys list_keywords list_load_tests list_maintenance_windows list_notification_channels list_notification_rules list_page_fragments list_runs list_scheduled_reports list_secrets list_targets list_tests mute_finding recompute_scores record_deployment remove_keyword resolve_incident rotate_secret start_load_test store_secret system_health target_stats team_stats trigger_all_tests trigger_journey trigger_test update_automation_rule update_journey update_notification_rule update_page_fragment update_scheduled_report update_target update_team_settings update_test

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	74/74	✓
has a description	74/74	✓
description is substantive	66/74	66/74
parameters are typed	74/74	✓
parameters are described	72/74	72/74

74 of 74 tools graded · 74 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.0.0

server version teste-no

Capabilities: logging prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:37Z	ok_tools	200	1098	2025-06-18
2026-08-12T05:33:51Z	ok_tools	200	702	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.validoria/validoria-mcp.svg)](https://robinsaige.com/s/com.validoria/validoria-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview