Perpage Mcp Server

io.github.Cal-Dev-TechPublished by GitHub account Cal-Dev-Techv0.1.3Updated Oct 24, 2026

Give AI agents clean, LLM-ready web data — scrape any URL to markdown or extract structured JSON.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant fetch web pages and turn them into clean markdown or structured JSON for further use.

What you can do
PerPage is a local MCP server that gives an assistant web-data retrieval tools. According to its description, it can scrape any URL and return the content as LLM-ready markdown or as extracted structured JSON. It runs as a local process over stdio and is intended for desktop use.
When to use it
Useful when an assistant needs readable page content or structured fields from web pages as part of a workflow, rather than raw HTML. Consider it if you already use PerPage or are willing to subscribe to it through RapidAPI.
Requirements
Runs locally as an npm package over stdio, so Node.js is needed. Requires a RapidAPI key supplied through the PERPAGE_API_KEY environment variable, which means subscribing to PerPage on RapidAPI. The optional PERPAGE_API_URL variable overrides the base URL; the default is the RapidAPI gateway, and it can be pointed at the direct API endpoint. Network access is required.
Before you install
The server needs a secret API key, PERPAGE_API_KEY, and sends the URLs you ask it to fetch to a third-party service (RapidAPI or the direct PerPage endpoint), so page content and target URLs leave your machine. The key may be tied to a paid RapidAPI subscription, so check quota and billing before heavy use. No authentication is declared for the MCP connection itself.

Installation

In SourceWeft

  1. Open Perpage Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.