MCP.Market

Fetchpet MCP server

by pulsemcp.com·com.pulsemcp/fetchpet·v0.1.8·80 stars
No reviews yet

MCP server for Fetch Pet insurance claims management using Playwright automation.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

80 stars62 downloads/wk

Reviews

Write one

Nobody has reviewed Fetchpet yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Fetchpet tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 medium
  • Code scan13 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    shared/server.js: … page .$eval('.react-datepicker__current-month', (el)…
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Fetchpet compares

Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 45% of 867 Scraping and browsing servers
GitHub stars
80
more than 91% of 584 Scraping and browsing servers
Downloads a week
62
more than 43% of 312 Scraping and browsing servers with a package

Install Fetchpet in Claude Code, Cursor or VS Code

Runs npx -y fetchpet-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add fetchpet -- npx -y fetchpet-mcp-server
Add to Cursor

What the publisher says

From the Fetchpet repository's README, as published. We do not edit it. Read it on GitHub

PulseMCP's MCP Servers

We build reliable servers thoughtfully designed for MCP Client-powered workflows.

Design principles

You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:

  1. Purpose-built. LLM-powered MCP clients offer uniquely new user interaction patterns that necessitate a different layer of abstraction than the REST API's from a pre-AI era. We thoughtfully scope drawing lines like building a new server, versus incorporating a new feature in another server. Or deciding where one slew of REST API endpoints might be better packaged as a single Tool call. And more.
  2. Easy set up. Many MCP servers die before ever getting a chance to be used. We offer guides and a frustration-free experience to get going with our MCP servers inside your favorite MCP clients.
  3. Time savings. By minimizing the number of tool chain steps or conversational turns you need to accomplish a task, our MCP servers will save you (and your agents) time waiting for a task to be completed.
  4. Inference cost savings. By minimizing the number of tokens you need to consume to a accomplish a task, our MCP servers will save you on your LLM inference bills.
  5. Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.
  6. Future-proof. We sit on the bleeding edge of the MCP specification, working to push the ecosystem forward. As such, you can be sure that if you commit to baking our server into your workflow, it will self-improve over time to take advantage of the latest and greatest MCP features.

Servers Available

Productionized Servers

These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.

The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/) by the publish-mcp-registry.yml workflow.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Fetchpet: common questions

Is Fetchpet MCP server safe?
Mostly: it is graded B (77/100). Read the Fetchpet safety report
How do I install Fetchpet?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Fetchpet need an API key?
Yes. The registry entry asks for FETCHPET_USERNAME, FETCHPET_PASSWORD.
Is Fetchpet maintained?
The last commit was 66 days ago (2026-08-30). The latest release is v0.1.8.
What can I use instead of Fetchpet?
Servers from other publishers that do the same job: Playwright MCP server, invisible_playwright_mcp MCP server and CloakBrowser MCP server.
How does Fetchpet compare with other Scraping and browsing MCP servers?
safety score 77/100 (higher than 45% of 867 Scraping and browsing servers); github stars 80 (more than 91% of 584 Scraping and browsing servers); downloads a week 62 (more than 43% of 312 Scraping and browsing servers with a package). Full comparison.

Alternatives to Fetchpet

Same job from other publishers: the closest match first, then the best rated.

  • Playwright
    Playwright Tools for MCP
    A
  • invisible_playwright_mcp
    AI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.
    A
  • CloakBrowser MCP
    Playwright MCP-compatible browser automation bridge for CloakBrowser Chromium.
    B
  • Endform
    Find failing, flaky, and slow Playwright tests on Endform and keep your suite healthy as it grows.
    A
  • Cdpilot
    Zero-dependency browser automation over raw CDP — no Puppeteer, Playwright, or Selenium.
    B

More from pulsemcp.com →