mcp-pricescout
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key. | |
| FIRECRAWL_API_KEY | Yes | Your Firecrawl API key. | |
| ANTHROPIC_BASE_URL | No | The base URL for the Anthropic API. Leave unset to use the standard API. Set to https://claude.vocareum.com when using a Vocareum-proxied Anthropic key (voc-...). | https://api.anthropic.com |
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 |
|---|---|
| scrape_websitesC | Scrape multiple websites using Firecrawl and store their content. Args: websites: Dictionary of provider_name -> URL mappings formats: List of formats to scrape ['markdown', 'html'] (default: both) api_key: Firecrawl API key (if None, expects environment variable) Returns: List of provider names for successfully scraped websites |
| extract_scraped_infoB | Extract information about a scraped website. Args: identifier: The provider name, full URL, or domain to look for Returns: Formatted JSON string with the scraped information |
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 2 tools
The two tools have clearly distinct roles: one initiates the scraping workflow and the other retrieves previously scraped data. There is minor potential for confusion about what 'extract' means in the naming, but the descriptions resolve the boundary.
Both tools follow a consistent verb_object pattern with snake_case: scrape_websites and extract_scraped_info. The naming style is uniform and predictable.
Two tools is on the low end for a price-scouting server, but the pair covers a minimal scrape-then-retrieve workflow. It feels thin rather than bloated, so it is borderline acceptable.
The server appears aimed at price monitoring, but there is no tool for searching, comparing, updating, or deleting scraped data. The surface only supports scraping and retrieving stored content, leaving significant gaps for a typical price-scout use case.