ScrapeMole Pkgs
REMOTE · PKGS.SCRAPEMOLE.WORKERS.DEV
Pay-per-call x402 npm and PyPI package metadata, versions, search, download counts.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Code Search and Documentation
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 830 tokens (~138/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 65
First indexed and scored.
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 18 Oct 2026 · Probed https://pkgs.scrapemole.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scrapemole.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6cb5e08b3ab5152b2cf983c23c8751537e4 |
| SANs: *.scrapemole.workers.dev, scrapemole.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pkgs.scrapemole.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pkgs.scrapemole.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://pkgs.scrapemole.workers.dev/mcp | Inconclusive | 405 |
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 →
npm_package ScrapeMole Pkgs: npm and PyPI package metadata for AI agents: npm package metadata ~126
Use when you need the public npm registry card for a package (scoped or unscoped): returns description, homepage, bugs URL, repository, license, keywords, maintainers as names only (emails stripped), number of versions, latest dist-tag version, created/modified times, and last-week download count from the official downloads API. Private packages are not supported. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | npm package name, optionally scoped (@scope/name). |
No output schema declared.
No examples provided.
npm_search ScrapeMole Pkgs: npm and PyPI package metadata for AI agents: npm package search ~107
Use to discover npm packages by keyword or name: returns up to 20 hits with name, version, description, keywords, date, and the registry search score. Publisher and maintainer emails are never returned (names/usernames only when present). Paid tool: x402 USDC on Base, $0.003 per successful call; call without payment to receive the PaymentRequired object.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Max results (1-20). |
| q | string | yes | Search text. |
No output schema declared.
No examples provided.
npm_version ScrapeMole Pkgs: npm and PyPI package metadata for AI agents: npm version details ~123
Use when you need the exact published artifact for an npm version: dependencies, optionalDependencies, peerDependencies, bundledDependencies, engines, os/cpu, dist (tarball URL, integrity, shasum, unpacked size), and the version publish time. Give "latest" as version to resolve the current dist-tag. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | npm package name. |
| version | string | yes | Exact version or "latest". |
No output schema declared.
No examples provided.
pypi_project ScrapeMole Pkgs: npm and PyPI package metadata for AI agents: PyPI project metadata ~109
Use when you need the public PyPI project card: summary, home_page, project_urls, license, requires_python, a subset of classifiers, requires_dist (capped), current version, and yank status. Author/maintainer emails are omitted or redacted; only display names remain when present. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | PyPI project name. |
No output schema declared.
No examples provided.
pypi_release ScrapeMole Pkgs: npm and PyPI package metadata for AI agents: PyPI release files ~128
Use when you need the published artifacts for a specific PyPI version: each file with filename, packagetype (sdist/bdist_wheel…), size, upload time, yank flags, digests (sha256/blake2b/md5) and download URL. Give "latest" as version to use the project's current version. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | PyPI project name. |
| version | string | yes | Exact version or "latest". |
No output schema declared.
No examples provided.
pypi_search ScrapeMole Pkgs: npm and PyPI package metadata for AI agents: PyPI project name lookup ~161
Use when you have a likely PyPI project name (or a few tokens) and need to resolve it to live projects: tries the query as-is, PEP 503 normalization (lowercase, [-_.] → -), and hyphen/underscore/dot variants, then returns up to "limit" matching projects with summary, version, requires_python and license. This is name resolution, not full-text discovery — prefer exact package names when known. Author emails are redacted. Paid tool: x402 USDC on Base, $0.003 per successful call; call without payment to receive the PaymentRequired object.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Max results (1-20). |
| q | string | yes | Project name or name-like query. |
No output schema declared.
No examples provided.
How do I install the ScrapeMole Pkgs MCP server?
ScrapeMole Pkgs is a hosted endpoint at https://pkgs.scrapemole.workers.dev/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 · pkgs.scrapemole.workers.dev
claude mcp add --transport http dev-pages-scrapemole-pkgs 'https://pkgs.scrapemole.workers.dev/mcp'
What is the ScrapeMole Pkgs MCP server?
ScrapeMole Pkgs is an MCP server listed in the public MCP registry as dev.pages.scrapemole/pkgs. Pay-per-call x402 npm and PyPI package metadata, versions, search, download counts. This page covers its hosted endpoint (https://pkgs.scrapemole.workers.dev/mcp).
Is the ScrapeMole Pkgs MCP server safe to use?
ScrapeMole Pkgs scores 68 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 ScrapeMole Pkgs MCP server expose?
ScrapeMole Pkgs exposes 6 tools: npm_package, npm_version, npm_search, pypi_project, pypi_release, pypi_search. Their descriptions and schemas cost roughly 754 tokens of context every time the server is loaded.
Does the ScrapeMole Pkgs MCP server require authentication?
No. We connected to ScrapeMole Pkgs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ScrapeMole Pkgs MCP server still maintained?
ScrapeMole Pkgs is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.