Skrape MCP Server

Created By
skrapeaia year ago
MCP Server for skrape.ai, lets you input any URL and it returns clean markdown for the LLM
Overview

What is Skrape MCP Server?

Skrape MCP Server is a tool that converts any webpage into clean, LLM-ready Markdown format, making it ideal for integrating web content into language models like Claude and GPT.

How to use Skrape MCP Server?

To use the Skrape MCP Server, input any URL into the server, and it will return a structured Markdown output. You can install it via Smithery or manually configure it with your API key.

Key features of Skrape MCP Server?

  • Converts web pages to clean, structured Markdown
  • Removes ads and irrelevant content for clarity
  • Supports JavaScript rendering for dynamic content
  • Provides an optional JSON response format for advanced integrations

Use cases of Skrape MCP Server?

  1. Feeding web content into LLMs for processing
  2. Generating structured documentation from web pages
  3. Simplifying the integration of web data into applications

FAQ from Skrape MCP Server?

  • Can Skrape MCP Server handle all types of web pages?

Yes! It can convert any webpage into Markdown, regardless of its structure.

  • Is there a cost associated with using Skrape MCP Server?

The server is free to use, but you need an API key from skrape.ai.

  • How does Skrape MCP Server ensure clean output?

It automatically removes unnecessary elements like ads and menus, focusing on the main content.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
skrapeai
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago