Web Content MCP

Created By
hmalfeea year ago
An MCP server that provides web content to your agent.
Overview

What is Web Content MCP?

Web Content MCP is a server that provides web content to agents, allowing for efficient retrieval of information from the web.

How to use Web Content MCP?

To use Web Content MCP, clone the repository, install dependencies, configure your environment variables, and set it up in your desired environment (Claude Desktop or VSCode).

Key features of Web Content MCP?

  • Fast and efficient web content retrieval
  • Supports both search-based and direct URL access
  • Compatible with Claude Desktop, VSCode, and any agent that supports MCP servers

Use cases of Web Content MCP?

  1. Searching for information on the web and summarizing results.
  2. Directly accessing and scraping content from specific URLs.
  3. Integrating with development environments for automated content retrieval.

FAQ from Web Content MCP?

  • What are the prerequisites for using Web Content MCP?

You need Node.js, pnpm/npm, TypeScript support, and a configured .env file with API keys.

  • Can I use Web Content MCP with any agent?

Yes, it is compatible with any agent that supports MCP servers.

  • How do I troubleshoot connection errors?

Ensure the server is running and the paths in your configuration files are correct.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hmalfee
Star
0
Language
TypeScript
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.

21 hours ago