About mcp-server-fetch-feedstock

Created By
conda-forgea year ago
A conda-smithy repository for mcp-server-fetch.
Overview

what is mcp-server-fetch-feedstock?

mcp-server-fetch-feedstock is a Model Context Protocol server that provides tools to fetch and convert web content for usage by LLMs (Large Language Models).

how to use mcp-server-fetch-feedstock?

To use mcp-server-fetch, install it from the conda-forge channel using the command:

conda install mcp-server-fetch

You can also use mamba for installation:

mamba install mcp-server-fetch

key features of mcp-server-fetch-feedstock?

  • Fetches web content and converts HTML to markdown.
  • Supports installation via conda and mamba.
  • Provides tools for querying available versions and dependencies.

use cases of mcp-server-fetch-feedstock?

  1. Retrieving and processing web content for LLMs.
  2. Converting web pages into markdown format for easier consumption.
  3. Integrating web content fetching capabilities into applications.

FAQ from mcp-server-fetch-feedstock?

  • What is the license for mcp-server-fetch?

The feedstock is licensed under BSD-3-Clause, while the package itself is under MIT.

  • How can I contribute to mcp-server-fetch?

You can fork the repository, make changes, and submit a pull request for review.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
conda-forge
Star
0
Language
-
License
BSD-3-Clause license

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.

a day ago