Mercury Parser

Created By
koichikawamuraa year ago
Overview

what is Mercury Parser?

Mercury Parser is a wrapper for the Mercury Parser library, which is designed to extract content from web pages in a structured format. It is particularly useful for developers looking to integrate web content extraction into their applications.

how to use Mercury Parser?

To use Mercury Parser, you can integrate it into your project using npx. You need to add a specific entry to your claude_desktop_config.json file to configure the MCP server.

key features of Mercury Parser?

  • Easy integration with existing projects using npx
  • Structured content extraction from web pages
  • Maintained fork of the Postlight Parser, ensuring reliability and updates

use cases of Mercury Parser?

  1. Extracting article content from news websites for aggregation.
  2. Building applications that require web scraping and content analysis.
  3. Automating the retrieval of structured data from various online sources.

FAQ from Mercury Parser?

  • What is the main purpose of Mercury Parser?

Mercury Parser is designed to help developers extract and structure content from web pages easily.

  • Is Mercury Parser free to use?

Yes! Mercury Parser is open-source and free to use for everyone.

  • Can I customize the extraction process?

Yes! You can modify the configuration to suit your specific content extraction needs.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

36 minutes ago