mcp-server-Bloom

Created By
Robinson777-proga year ago
A Model Context Protocol (MCP) server implementation that integrates with web scraping capabilities.
Overview

What is mcp-server-Bloom?

mcp-server-Bloom is a Model Context Protocol (MCP) server implementation that integrates web scraping capabilities to optimize web content extraction and improve data processing efficiency.

How to use mcp-server-Bloom?

To use mcp-server-Bloom, clone the repository from GitHub, follow the installation instructions in the INSTALL.md file, configure the crawling and extraction options in the config.json file, and run the main script to start the URL discovery and extraction process.

Key features of mcp-server-Bloom?

  • Automatic URL discovery and crawling from an initial seed.
  • Precise web search with content extraction for various formats (text, images, metadata).
  • Automatic retries with exponential backoff for handling temporary failures.
  • Efficient batch processing with built-in rate limiting to comply with web service usage policies.
  • Real-time credit usage monitoring for cloud APIs to manage resources effectively.

Use cases of mcp-server-Bloom?

  1. Discovering and extracting data from multiple web pages for research purposes.
  2. Automating the collection of content for data analysis and reporting.
  3. Monitoring web content changes over time for competitive analysis.

FAQ from mcp-server-Bloom?

  • Is mcp-server-Bloom easy to set up?

Yes! Follow the installation instructions provided in the repository to get started quickly.

  • Can mcp-server-Bloom handle large volumes of data?

Yes! It supports efficient batch processing and has built-in rate limiting to manage requests effectively.

  • What types of content can be extracted?

The tool can extract text, images, and metadata from web pages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Robinson777-prog
Star
0
Language
JavaScript
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