ai.clawfetch/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Clawfetch web research/fetch capabilities

What we know

Web intelligence for AI agents: fetch, render, extract, research. x402 micropayments, no API keys. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

npm exact package downloads 564 in 2026-09-09..2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure. Reported action classes: paid research invocations. Complete write authority is not verified.
Refer to first-party setup documentation; do not infer authorization from package existence.
Sensitive access: fetched URLs and fetched content

Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 564 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @clawfetch/mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T03:38:00Z.

All limitations / Review context

Has ai.clawfetch/mcp changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure.
Public tracking suitability is not an installation safety audit.
Refer to first-party setup documentation; do not infer authorization from package existence.
fetched URLs and fetched content
Reviewed write actions: paid research invocations
Sensitive access: fetched URLs and fetched content
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Precise setup/auth/permissions not verified
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Original activity observations

npm exact package downloads 564 in 2026-09-09..2026-10-08

Technical identity

npm/@clawfetch/mcp

Exact implementation source: https://www.npmjs.com/package/@clawfetch/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@clawfetch/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@clawfetch/mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Public hosted MCP endpoint previously observed HTTP 410; local executable presence does NOT verify underlying paid x402 service availability.
HIGH RISK: Ethereum private key used for USDC on Base x402 micro-payments. Do not paste funded wallet keys into shared files.
Only claim static local Setup documented, never functional payment availability.
Exact local npm install from publisher; does not establish upstream service availability.
Publisher README config reproduced as MCP100 structured data; requires real credentials and may require separately installed or built server. Not runtime tested.
Prior reviewed safety note: Never paste a funded wallet private key into shared configuration.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.

Install / connect
Publisher instructions
Publisher documents local npm install -g @clawfetch/mcp then stdio launcher clawfetch-mcp using CLAWFETCH_PRIVATE_KEY; prior hosted public endpoint returned HTTP 410 and must not be recommended.
publisher documented install or registration · Publisher instructions
npm install -g @clawfetch/mcp

Configure / authenticate

MCP100 setup guide

Register `npx -y @clawfetch/mcp` in client (global install is optional).

claude desktop or cursor mcpServers json · Publisher instructions

{
  "mcpServers": {
    "clawfetch": {
      "args": [],
      "command": "clawfetch-mcp",
      "env": {
        "CLAWFETCH_PRIVATE_KEY": "YOUR_DEDICATED_LOW_BALANCE_KEY"
      }
    }
  }
}

Check connection
Suggested check
Use publisher `health_check` tool; avoid paid web fetching as smoke test.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `clawfetch-mcp`, run `claude mcp remove clawfetch-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove clawfetch-mcp

Official Documentation & Sources

What it does

Web intelligence for AI agents: fetch, render, extract, research. x402 micropayments, no API keys. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Clawfetch web research/fetch capabilities

Representative uses

Clawfetch web research/fetch capabilities

Limitations

Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Dated package download count is usage signal, not necessarily a current maintenance release.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.
Permissions: Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure.
Data handling: fetched URLs and fetched content
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure.

Access scope and cautions

Write actions: Not verified paid research invocations
Sensitive access: fetched URLs and fetched content
Risk level: medium
Security notes: Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Clawfetch web research/fetch capabilities.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: paid research invocations. Recorded permission context: Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure.

What data-handling boundary should I consider?

fetched URLs and fetched content Recorded sensitive-access context: fetched URLs and fetched content.

What limitations and risks should I check before use?

Web fetch/extract and x402 payment can send URLs and incur charges; inspect destination/data exposure. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Dated package download count is usage signal, not necessarily a current maintenance release. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.