Skills/PyPI/vfa-mcp

vfa-mcp@1.0.5

VERIFIED· not started

Publisher claims: "VFA — Visual & Functional Auditor: auditoria web autonoma (visual + funcional) expuesta como servidor MCP, con Playwright local y motor universal LiteLLM." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher aidevteam-red.line.v.o.s · publishing for 20 daysInstalls 753Last detonated 40 min ago
$claude mcp add vfa-mcp -- uvx vfa-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
VFA_LICENSE_KEYConfiguration, not credentials: BROWSER_CDP_TIMEOUT_MS, BROWSER_CDP_URL, HEADLESS, LITELLM_LOG, SSL_VERIFY, VFA_ACTION_TIMEOUT_MS, VFA_AGENT_MAX_ITERATIONS, VFA_ALLOW_LOCAL_HOST, VFA_ARTIFACTS_DIR, VFA_BROWSER, VFA_LICENSE_SERVER_URL, VFA_LLM_CHECKS_PER_SECOND, VFA_LLM_PROVIDER, VFA_LLM_REQUESTS_PER_SECOND, VFA_LLM_TEMPERATURE, VFA_LLM_TIMEOUT, VFA_MAX_MODULES, VFA_QUARANTINE, VFA_SCREENSHOT_FULL_PAGE, VFA_SESSION_POOL_ENABLED, VFA_SESSION_POOL_MAX_SIZE, VFA_SESSION_POOL_TTL, VFA_SESSION_STORAGE_STATE, VFA_SHARD, VFA_TEST_MAX_CASES, VFA_VISION_PROVIDER
Where it talks to
no vendor host named in the codeAlso workers.dev — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names workers.dev as well as its own vendor. The guard injects VFA_LICENSE_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx vfa-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsapp/llm_config.py:15 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Cargar variables de entorno desde .env (si existe). Idempotente: app.configFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_step_spec.py:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfor url in ("file:///etc/passwd", "javascript:alert(1)", "data:text/html,x"):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsapp/config.py:25 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Cargar variables de entorno desde .env (si existe).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_qa_tools.py:274 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesresult = asyncio.run(qa_tools.qa_audit_url("file:///etc/passwd"))Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈72 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.