Skills/PyPI/apillow-mcp

apillow-mcp@0.1.8

VERIFIED· not started

Publisher claims: "MCP server for Apillow — Zillow property data API. Search properties, get Zestimates, price history, and more directly from AI agents. Not affiliated with Zillow Group. mcprush.com-c05ca10a8e2927f3bc2c63dd" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server) · listed in the official MCP RegistryPublisher apillow-adam · publishing for 225 daysInstalls 143Last detonated 12 h ago
$claude mcp add apillow-mcp -- uvx apillow-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
APILLOW_API_KEYConfiguration, not credentials: APILLOW_API_URL
Where it talks to
apillow.co (its own)Also zillow.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
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 zillow.com as well as its own vendor. The guard injects APILLOW_API_KEY only into requests to apillow.co (and its subdomains) and refuses the rest.

$vet-skills run --secrets APILLOW_API_KEY=apillow.co -- uvx apillow-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-14 and scored it 93/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.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

LOW
Account verification phishing language detectedREADME.md:17 · Account verification phishing language detected · informational: not an instruction file…nt to sign you up (it calls `signup(email)`), or sign up at https://apillow.co. Verify your email address, and the welcome mail contains your key. Paste the key into the config …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
MEDIUM
Python subprocess execution detectedtests/test_format.py:130 · Python subprocess execution detectedr = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

Cost to the agent

Instructions loaded
≈87 tok
1 file · 20 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

No advisories in OSV for apillow-mcp@0.1.8 as of 11 h ago. This is the package itself, not its dependencies.