free-web-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BSC_RPC_URL | No | Chain RPC (Anvil `http://127.0.0.1:8545` or BSC Testnet) | |
| MCP_SERVER_URL | No | Where the dashboard finds the MCP server (`http://127.0.0.1:8765`) | |
| WALLET_PRIVATE_KEY | No | Server-side signer for anchoring (never in frontend/logs) | |
| EVIDENCE_REGISTRY_ADDRESS | No | Deployed contract address (after `forge script`) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchB | Search the web and return a list of results (title/url/snippet). |
| web_fetchB | Fetch a webpage and extract its main readable content. Set rendered=True to drive a headless browser (requires RENDER_ENABLED=true). |
| web_search_and_fetchA | Search the web, then fetch and extract text from each result URL. Set rendered=True to drive a headless browser (requires RENDER_ENABLED=true). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: web_search returns results, web_fetch retrieves a single page, and web_search_and_fetch explicitly combines both. There is no meaningful overlap between the three.
All tool names follow the consistent web_<action> pattern using lowercase snake_case. The names clearly indicate their operation, including the compound web_search_and_fetch.
Three tools is a reasonable, well-scoped size for a simple web retrieval server. Each tool earns its place, and the combined search-and-fetch adds convenience without bloating the surface.
The core search-and-fetch workflow is fully covered, with an optional rendered mode for JavaScript-heavy pages. A minor gap is lack of a tool for raw HTML or structured page extraction, but most basic browsing needs are addressed.