Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.pulsemcp/pulse-fetch

NPM · @PULSEMCP/PULSE-FETCH · SCANNED SEP 20

MCP server for fetching web resources with content extraction and anti-bot bypass.

Available components

npm · @pulsemcp/pulse-fetch 81
0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 48 of 162 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 750 tokens (~750/item across 1 items; 1 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 Management93
  • Stability observed for 28 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.pulsemcp/pulse-fetch MCP server?

com.pulsemcp/pulse-fetch runs locally as an npm package, launched with npx -y @pulsemcp/pulse-fetch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pulsemcp/pulse-fetch

# add to Claude Code
claude mcp add com-pulsemcp-pulse-fetch -- npx -y @pulsemcp/pulse-fetch
// .cursor/mcp.json
{
  "mcpServers": {
    "com-pulsemcp-pulse-fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@pulsemcp/pulse-fetch"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-pulsemcp-pulse-fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@pulsemcp/pulse-fetch"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-pulsemcp-pulse-fetch -- npx -y @pulsemcp/pulse-fetch
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pulsemcp-pulse-fetch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pulsemcp/pulse-fetch"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-pulsemcp-pulse-fetch --command npx --arg -y --arg @pulsemcp/pulse-fetch
# ~/.hermes/config.yaml
mcp_servers:
  com-pulsemcp-pulse-fetch:
    command: "npx"
    args: ["-y", "@pulsemcp/pulse-fetch"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-pulsemcp-pulse-fetch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pulsemcp/pulse-fetch"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-pulsemcp-pulse-fetch -t stdio -c npx -a -y @pulsemcp/pulse-fetch
// mcp.json
{
  "mcpServers": {
    "com-pulsemcp-pulse-fetch": {
      "command": "npx",
      "args": [
        "-y",
        "@pulsemcp/pulse-fetch"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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 20 Sept 2026 · Analysed npm/@pulsemcp/pulse-fetch@0.3.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 162 packages
Packages resolved 162
Deprecated 2
Stale 47
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~750 tokens

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 →

Tool Tokens
scrape ~750

Scrape webpage content using intelligent automatic strategy selection with built-in caching. This tool fetches content from any URL with flexible result handling options. Result handling modes: - returnOnly: Returns scraped content without saving (uses maxChars for size limits) - saveAndReturn: Saves content as MCP Resource AND returns it (default, best for reuse) - saveOnly: Saves content as MCP Resource, returns only resource link (no content) Example responses by mode: returnOnly: { "content": [ { "type": "text", "text": "Article content here... --- Scraped using: native" } ] } saveAndReturn (embedded resource): { "content": [ { "type": "resource", "resource": { "uri": "scraped://example.com/article_2024-01-15T10:30:00Z", "name": "https://example.com/article", "text": "Full article content..." } } ] } saveOnly (linked resource): { "content": [ { "type": "resource_link", "uri": "scraped://example.com/article_2024-01-15T10:30:00Z", "name": "https://example.com/article" } ] } Caching behavior: - Previously scraped URLs are automatically cached as MCP Resources - Subsequent requests return cached content (unless forceRescrape: true) - saveOnly mode bypasses cache lookup for efficiency Scraping strategies: - native: Direct HTTP fetch (fastest, works for most public sites) - firecrawl: Advanced scraping with JavaScript rendering (requires FIRECRAWL_API_KEY) - brightdata: Premium scraping for heavily protected sites (requires BRIGHTDATA_API_KEY) The tool automatically: 1. Checks cache first (except in saveOnly mode) 2. Tries the most appropriate scraping method based on domain patterns 3. Falls back to alternative methods if needed 4. Remembers successful strategies for future requests

NameTypeReqDescription
cleanScrapeboolean–Whether to clean the scraped content by converting HTML to semantic Markdown of what's on the page, removing ads, navigation, and boilerplate. This typically reduces content size by 50-90% while pres…
forceRescrapeboolean–Force a fresh scrape even if cached content exists for this URL. Useful when you know the content has changed. Default: false
maxCharsnumber–Maximum number of characters to return from the scraped content. Useful for limiting response size. Default: 100000
resultHandlingstring–How to handle scraped content and MCP Resources. Options: "saveOnly" (saves as linked resource, no content returned), "saveAndReturn" (saves as embedded resource and returns content - default), "retu…
startIndexnumber–Character position to start reading from. Use with maxChars for pagination through large documents (e.g., startIndex: 100000 to skip first 100k chars). Default: 0
timeoutnumber–Maximum time to wait for page load in milliseconds. Increase for slow-loading sites (e.g., 120000 for 2 minutes). Default: 60000 (1 minute)
urlstringyesThe webpage URL to scrape (e.g., "https://example.com/article", "https://api.example.com/docs")

No output schema declared.

No examples provided.

Common questions

What is the com.pulsemcp/pulse-fetch MCP server?

com.pulsemcp/pulse-fetch is an MCP server listed in the public MCP registry as com.pulsemcp/pulse-fetch. MCP server for fetching web resources with content extraction and anti-bot bypass. This page covers its npm package (@pulsemcp/pulse-fetch).

Is the com.pulsemcp/pulse-fetch MCP server safe to use?

com.pulsemcp/pulse-fetch scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 com.pulsemcp/pulse-fetch MCP server expose?

com.pulsemcp/pulse-fetch exposes 1 tool: scrape. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.

Is the com.pulsemcp/pulse-fetch MCP server still maintained?

com.pulsemcp/pulse-fetch is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.pulsemcp/pulse-fetch MCP server under?

com.pulsemcp/pulse-fetch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.