Skills/PyPI/scrapely-mcp

scrapely-mcp@0.3.16

VERIFIED· not started

Publisher claims: "Model Context Protocol server for Scrape.ly: find, run and inspect Actors, and read their results." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher scrapely-app · publishing for 33 daysInstalls 2,292Last detonated 57 min ago
$claude mcp add scrapely-mcp -- uvx scrapely-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
SCRAPELY_TOKENSENTRY_DSNConfiguration, not credentials: SCRAPELY_ACTORS, SCRAPELY_MCP_HOST, SCRAPELY_MCP_MAX_REMOTE_INFLIGHT_BYTES, SCRAPELY_MCP_MAX_REMOTE_RESPONSE_BYTES, SCRAPELY_MCP_PORT, SCRAPELY_MCP_UI, SCRAPELY_MCP_VALIDATION_BUDGET_SECS, SCRAPELY_TELEMETRY_ENDPOINT, SCRAPELY_TOOLS, UI_MODE
Where it talks to
no vendor host named in the codeAlso scrape.ly, gstatic.com, segment.io — 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 scrape.ly, gstatic.com, segment.io as well as its own vendor. The guard injects SCRAPELY_TOKEN, SENTRY_DSN only into requests to the host you bind (and its subdomains) and refuses the rest.

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

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

What changed since 0.3.10

vet-skills diff scrapely-mcp 0.3.10 0.3.16

This version reaches for something 0.3.10 did not: 3 new hosts (gstatic.com, scrape.ly, segment.io) · 2 new credential variables (SCRAPELY_TOKEN, SENTRY_DSN). Compared from the two recorded runs, not from source.

New hosts
gstatic.com, scrape.ly, segment.io
New credential variables
SCRAPELY_TOKEN, SENTRY_DSN

0.3.10 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

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-17 and scored it 91/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

MEDIUM
MCP server using network transport (SSE/HTTP)src/scrapely_mcp/remote.py:377 · MCP server using network transport (SSE/HTTP) — data sent over networklog.soft_fail("streamable HTTP connect to MCP-server Actor failed, trying SSE", reason=str(first))Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)src/scrapely_mcp/cli.py:1 · MCP server using network transport (SSE/HTTP) — data sent over network"""Console entry points: `scrapely-mcp-server` (stdio) and `scrapely-mcp-http` (hosted)."""Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

Cost to the agent

Instructions loaded
≈61 tok
1 file · 48 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 scrapely-mcp@0.3.16 as of 21 min ago. This is the package itself, not its dependencies.