com.validoria/validoria-mcp
REMOTE · API.TESTE.NO · 2 COMPONENTS · SCANNED OCT 6
Continuous website testing by Validoria — monitor security, SEO, performance, and accessibility.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 74 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- 20% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5785 tokens (~74/item across 78 items; 74 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_maintenance_window" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 75 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.validoria/validoria-mcp server?
com.validoria/validoria-mcp is a hosted endpoint at https://api.teste.no/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.teste.no
claude mcp add --transport http com-validoria-validoria-mcp 'https://api.teste.no/api/mcp'
{
"mcpServers": {
"com-validoria-validoria-mcp": {
"url": "https://api.teste.no/api/mcp"
}
}
} {
"servers": {
"com-validoria-validoria-mcp": {
"type": "http",
"url": "https://api.teste.no/api/mcp"
}
}
} [mcp_servers.com-validoria-validoria-mcp] url = "https://api.teste.no/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-validoria-validoria-mcp": {
"type": "remote",
"url": "https://api.teste.no/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-validoria-validoria-mcp --url 'https://api.teste.no/api/mcp' --transport streamable-http
mcp_servers:
com-validoria-validoria-mcp:
url: "https://api.teste.no/api/mcp" {
"McpServers": {
"com-validoria-validoria-mcp": {
"Transport": "http",
"Url": "https://api.teste.no/api/mcp"
}
}
} assistant mcp add com-validoria-validoria-mcp -t streamable-http -u 'https://api.teste.no/api/mcp'
{
"mcpServers": {
"com-validoria-validoria-mcp": {
"type": "http",
"url": "https://api.teste.no/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 0
- “update_team_settings” reworded the description of “aiModel” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 3 Oct 26 0
- Tool “get_target_scores” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +19
- TLS certificate: unverified → pass ▲ security
- 23 Sept 26 −19
- TLS certificate: pass → unverified ▼ security
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://api.teste.no/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.teste.no | CN=YR1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | RSA 2048 | SHA256-RSA | 523c4a954d804cdcf0c629c97b5c1a21dce |
| SANs: api.teste.no | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.teste.no. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| no. | present | 38032 | 13 | Verified |
| teste.no. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.teste.no/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.teste.no/api/mcp | HTTPS enforced | 301 | https://api.teste.no/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_targets List Targets ~67
List all monitoring targets for your team. Returns name, URL, type, status, and uptime info for each target.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of targets to return |
| status | string | – | Filter by target status |
| type | string | – | Filter by target type |
No output schema declared.
No examples provided.
list_tests List Test Definitions ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by test category |
| enabledOnly | boolean | – | Only show enabled tests. Default: true. |
No output schema declared.
No examples provided.
mute_finding Mute Finding ~43
Mute an open finding to suppress it from dashboards and alerts. Status changes from OPEN to MUTED.
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | The finding ID to mute |
No output schema declared.
No examples provided.
recompute_scores Recompute Composite Scores ~54
Force recompute all composite scores (Security, SEO, Performance, Accessibility) for a target. Useful after manual changes or when scores seem stale.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | The target ID to recompute scores for |
No output schema declared.
No examples provided.
record_deployment Record Deployment ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commitSha | string | – | Git commit SHA |
| deployedBy | string | – | Who deployed (name, email, or system) |
| description | string | – | Deployment description or changelog |
| environment | string | – | Environment, e.g. "production", "staging" |
| targetId | string | yes | The target ID |
| version | string | – | Version string, e.g. "v2.4.1" |
No output schema declared.
No examples provided.
remove_keyword Remove Keyword ~44
Remove an SEO keyword from a target.
| Name | Type | Req | Description |
|---|---|---|---|
| keywordId | string | yes | The keyword ID to remove |
| targetId | string | yes | The target ID (for access verification) |
No output schema declared.
No examples provided.
resolve_incident Resolve Incident ~43
Resolve an incident to mark it as handled. Changes status to RESOLVED and sets the closed timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| incidentId | string | yes | The incident ID to resolve |
No output schema declared.
No examples provided.
rotate_secret Rotate Secret ~55
Update the value of an existing secret.
| Name | Type | Req | Description |
|---|---|---|---|
| newValue | string | yes | New secret value |
| secretId | string | yes | The secret ID to rotate |
| targetId | string | yes | The target ID (for access verification) |
No output schema declared.
No examples provided.
start_load_test Start Load Test ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledgeSharedOrigin | boolean | – | Acknowledge blast radius if target shares a server with other monitored sites |
| concurrency | number | – | Number of concurrent connections |
| duration | number | – | Test duration in seconds |
| httpMethod | string | – | HTTP method |
| mode | string | – | Load test mode |
| rampUp | number | – | Ramp-up time in seconds |
| targetId | string | yes | The target ID to load test |
| targetUrl | string | – | Override URL (defaults to target URL) |
No output schema declared.
No examples provided.
store_secret Store Secret ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description |
| environment | string | – | Environment scope |
| key | string | yes | Secret key (e.g. LOGIN_EMAIL) |
| label | string | yes | Human-readable label |
| targetId | string | yes | The target ID |
| value | string | yes | Secret value (will be encrypted) |
No output schema declared.
No examples provided.
system_health System Health ~41
Get a comprehensive system health report: BullMQ queue depths, active/stuck runs, user sessions, notification delivery stats, and recent error counts. Requires admin scope.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
target_stats Target Statistics ~80
Get statistics for a specific target: runs, pass rate, findings, duration. Supports lifetime, monthly, or weekly periods.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Period filter: "lifetime", "2026-04" (monthly), or "2026-W14" (weekly). Defaults to lifetime. |
| targetId | string | yes | The target ID |
No output schema declared.
No examples provided.
team_stats Team Statistics ~74
Get team-wide overview statistics: total runs, pass rate, open findings, open incidents, average duration. Supports lifetime, monthly, or weekly periods.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Period filter: "lifetime", "2026-04" (monthly), or "2026-W14" (weekly). Defaults to lifetime. |
No output schema declared.
No examples provided.
trigger_all_tests Trigger All Tests ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | The target ID to scan |
No output schema declared.
No examples provided.
trigger_journey Trigger Journey ~47
Execute a journey (custom browser test flow) against its target. The journey runs asynchronously — use get_run to check progress.
| Name | Type | Req | Description |
|---|---|---|---|
| journeyId | string | yes | The journey ID to trigger |
No output schema declared.
No examples provided.
trigger_test Trigger Test ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | The target ID to test |
| testId | string | – | Test definition ID (use this or testSlug) |
| testSlug | string | – | Test slug e.g. "security-headers" (use this or testId) |
No output schema declared.
No examples provided.
update_automation_rule Update Automation Rule ~119
Update an existing automation rule. Any field not provided will remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | – | Updated actions |
| conditions | object | – | Updated conditions |
| isEnabled | boolean | – | Enable or disable the rule |
| name | string | – | Updated rule name |
| priorityOrder | integer | – | Updated priority order |
| ruleId | string | yes | The automation rule ID to update |
| targetId | string|null | – | Updated target scope (null to remove target scoping) |
| trigger | string | – | Updated trigger event |
No output schema declared.
No examples provided.
update_journey Update Journey ~98
Update a journey's name, settings, or steps. When steps are provided, all existing steps are replaced.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | Updated description |
| isEnabled | boolean | – | Enable or disable the journey |
| journeyId | string | yes | The journey ID to update |
| name | string | – | Updated name |
| steps | array | – | Replacement steps (replaces all existing steps) |
| timeoutSeconds | number | – | Updated timeout |
No output schema declared.
No examples provided.
update_notification_rule Update Notification Rule ~84
Update a notification rule. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| channelTypes | array | – | – |
| enabled | boolean | – | – |
| eventTypes | array | – | – |
| name | string | – | – |
| quietHoursEnd | – | – | – |
| quietHoursStart | – | – | – |
| ruleId | string | yes | The notification rule ID |
| severities | array | – | – |
No output schema declared.
No examples provided.
update_page_fragment Update Page Fragment ~59
Update a page fragment. When steps are provided, all existing steps are replaced.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | – |
| fragmentId | string | yes | The fragment ID |
| name | string | – | Updated name |
| steps | array | – | Replacement steps |
No output schema declared.
No examples provided.
update_scheduled_report Update Scheduled Report ~103
Update an existing scheduled report. Any field not provided stays unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| dayOfWeek | number | – | Updated day of week |
| enabled | boolean | – | Enable or disable the report |
| frequency | string | – | Updated frequency |
| hourUtc | number | – | Updated hour UTC |
| name | string | – | Updated name |
| recipients | string | – | Updated comma-separated email list |
| reportId | string | yes | The scheduled report ID to update |
No output schema declared.
No examples provided.
update_target Update Target ~198
Update a target's properties (name, URL, type, environment, business weight, tags, uptime toggle).
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | New environment |
| name | string | – | New display name |
| tags | array | – | New tags (replaces existing) |
| targetId | string | yes | The target ID to update |
| type | string | – | New target type |
| uptimeEnabled | boolean | – | Toggle uptime monitoring |
| uptimeKeyword | – | – | Keyword to verify in response body during uptime checks. When set, every uptime ping GETs the page and verifies this text appears (case-insensitive). If missing, the site is treated as DOWN even on H… |
| url | string | – | New URL |
| weight | string | – | New business weight: REVENUE_PATH, PUBLIC or INTERNAL. Changing this rescores the target's open findings so the consequence ranking updates immediately. |
No output schema declared.
No examples provided.
update_team_settings Update Team Settings ~465
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).
| Name | Type | Req | Description |
|---|---|---|---|
| aiAutoEnrich | boolean | – | Auto-enrich new findings with AI |
| aiCapAction | string | – | Action when cap is reached |
| aiEnabled | boolean | – | Enable/disable AI finding enrichment |
| aiModel | string | – | Model id on the AI gateway for finding enrichment (e.g. mistral/mistral-small-2603, an EU route) |
| aiMonthlyCapUsd | – | – | Monthly AI spending cap in USD (null = unlimited) |
| aiSourceReviewModel | string | – | Model for AI source review plugin |
| defaultRunTimeoutMs | number | – | Default run timeout in ms |
| defaultScheduleMultiplier | number | – | Schedule frequency multiplier (< 1 = more frequent) |
| digestEnabled | boolean | – | Enable notification alert coalescing |
| digestWindowSeconds | number | – | Digest window duration in seconds |
| escalateInfoAgeDays | number | – | Finding age in days before INFO→WARNING |
| escalateInfoRecurrence | number | – | Finding recurrences before INFO→WARNING |
| escalateWarningAgeDays | number | – | Finding age in days before WARNING→CRITICAL |
| escalateWarningRecurrence | number | – | Finding recurrences before WARNING→CRITICAL |
| maxConcurrentRunsPerTarget | number | – | Max concurrent test runs per target |
| maxDailyRunsPerTarget | number | – | Max test runs per target per day (0=unlimited). Prevents overwhelming hosted sites with limited request budgets. |
| seoRankCheckEnabled | boolean | – | Enable Google rank tracking |
| testsPaused | boolean | – | Kill switch — pauses ALL scheduled and manual test runs |
| uptimeDegradedThresholdMs | number | – | Response time threshold for DEGRADED status |
| uptimeFailThreshold | number | – | Consecutive failures before DOWN |
| uptimePingTimeoutMs | number | – | Uptime ping timeout in ms |
No output schema declared.
No examples provided.
update_test Update Test Definition ~90
Enable or disable a test definition globally, or update its schedule/timeout. Requires admin scope.
| Name | Type | Req | Description |
|---|---|---|---|
| defaultSchedule | string | – | Cron schedule (e.g. "0 */6 * * *") |
| enabled | boolean | – | Enable or disable the test globally |
| slug | string | yes | Test plugin slug (e.g. "http-protocol-check") |
| timeout | number | – | Timeout in milliseconds |
No output schema declared.
No examples provided.
What is the com.validoria/validoria-mcp server?
com.validoria/validoria-mcp is listed in the public MCP registry as com.validoria/validoria-mcp. Continuous website testing by Validoria, monitor security, SEO, performance, and accessibility. This page covers its hosted endpoint (https://api.teste.no/api/mcp).
Is the com.validoria/validoria-mcp server safe to use?
com.validoria/validoria-mcp scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.validoria/validoria-mcp server expose?
com.validoria/validoria-mcp exposes 74 tools: guest_start_scan, guest_get_scan, list_targets, get_target, get_target_scores, and 69 more. Their descriptions and schemas cost roughly 5,764 tokens of context every time the server is loaded.
Does the com.validoria/validoria-mcp server require authentication?
No. We connected to com.validoria/validoria-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.validoria/validoria-mcp server still maintained?
com.validoria/validoria-mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.