Is com.validoria/validoria-mcp up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://api.teste.no/api/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://api.teste.no/api/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://api.teste.no with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 74 tools: 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.
Its tools changed between 2026-09 and 2026-10:
get_target_scores: description changedupdate_team_settings: input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.validoria/validoria-mcp |
|---|---|
| Endpoint | https://api.teste.no/api/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt