ai.testiv/mcp
NPM · @TESTIVAI/MCP · SCANNED SEP 20
Local-first visual regression for AI agents: verdicts, diff images, explain_snapshot. No API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 63 of 186 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to mcbuddy/testivai-oss). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 30 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 449 tokens (~56/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 ai.testiv/mcp server?
ai.testiv/mcp runs locally as an npm package, launched with npx -y @testivai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @testivai/mcp
claude mcp add ai-testiv-mcp -- npx -y @testivai/mcp
{
"mcpServers": {
"ai-testiv-mcp": {
"command": "npx",
"args": [
"-y",
"@testivai/mcp"
]
}
}
} {
"servers": {
"ai-testiv-mcp": {
"command": "npx",
"args": [
"-y",
"@testivai/mcp"
]
}
}
} codex mcp add ai-testiv-mcp -- npx -y @testivai/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-testiv-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@testivai/mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-testiv-mcp --command npx --arg -y --arg @testivai/mcp
mcp_servers:
ai-testiv-mcp:
command: "npx"
args: ["-y", "@testivai/mcp"] {
"McpServers": {
"ai-testiv-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@testivai/mcp"
]
}
}
} assistant mcp add ai-testiv-mcp -t stdio -c npx -a -y @testivai/mcp
{
"mcpServers": {
"ai-testiv-mcp": {
"command": "npx",
"args": [
"-y",
"@testivai/mcp"
]
}
}
} 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.
- 20 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.77 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −3
- Stability: pass → 0.80 functional
- 7 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@testivai/mcp@0.5.7
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mcbuddy/testivai-oss |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mcbuddy/testivai-oss/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2303189239 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b92e4ca3541c5dc04b993b007d314ef7f87a79ea338630c7aaafcb065dc19e9bd575a0ea93b8bf640ca902d72a88789f4fc3db0d37a1428abf9d025ac |
Background: How many MCP packages publish verified provenance →
Dependencies 186 packages
| Packages resolved | 186 |
|---|---|
| Stale | 63 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
approve_all Approve all pending snapshots as baselines ~55
Promote every pending capture under .testivai/temp/ to committed baselines (same as `testivai approve --all`). Only run this after a reviewer has confirmed the changes; then commit .testivai/baselines/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
approve_snapshot Approve one snapshot as the new baseline ~64
Promote .testivai/temp/<name>/ to the committed baseline (same as `testivai approve <name>`). Only approve changes a reviewer has confirmed are intended; then commit .testivai/baselines/.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Snapshot name to approve |
No output schema declared.
No examples provided.
explain_snapshot Explain what changed in one snapshot ~73
Layered evidence for one snapshot: pixel regions with bounding boxes, element attribution (which selectors shifted vs changed, whole-page shift detection), the DOM/style signal, and interpretation guidance. Use this to explain WHY a diff happened — pair with get_diff for the images.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Snapshot name from the results |
No output schema declared.
No examples provided.
get_diff View snapshot diff images ~54
Return the baseline, current, and diff images for one changed snapshot so you can see what changed visually. Use get_report / get_visual_results first to find snapshot names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Snapshot name from the results |
No output schema declared.
No examples provided.
get_report Get the raw visual report (results.json) ~44
Return the machine-readable results.json payload verbatim (summary + per-snapshot status, diff %, DOM signal, and region→selector attribution). Parse this instead of scraping CLI output.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_snapshot_diff View snapshot diff images ~55
Return the baseline, current, and diff images for one changed snapshot so you can see what changed visually. Use get_report / get_visual_results first to find snapshot names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Snapshot name from the results |
No output schema declared.
No examples provided.
get_visual_results Get visual test results ~80
Read the latest TestivAI visual regression results (visual-report/results.json). Returns a per-snapshot verdict combining the pixel diff and the DOM signal: DOM-identical diffs are likely render noise; DOM changes are real and need human review. Run the test suite first (e.g. `npx playwright test`) if results are stale or missing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_baselines List committed baselines ~24
List the snapshot baselines committed under .testivai/baselines/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ai.testiv/mcp server?
ai.testiv/mcp is listed in the public MCP registry as ai.testiv/mcp. Local-first visual regression for AI agents: verdicts, diff images, explain_snapshot. No API key. This page covers its npm package (@testivai/mcp).
Is the ai.testiv/mcp server safe to use?
ai.testiv/mcp scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 ai.testiv/mcp server expose?
ai.testiv/mcp exposes 8 tools: get_visual_results, get_diff, get_snapshot_diff, get_report, approve_snapshot, and 3 more. Their descriptions and schemas cost roughly 449 tokens of context every time the server is loaded.
Is the ai.testiv/mcp server still maintained?
ai.testiv/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ai.testiv/mcp server under?
ai.testiv/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.