mcp-pricescout
Related Servers
Alternatives to mcp-pricescout
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables scraping and comparing LLM inference pricing from multiple providers using Firecrawl, storing results in SQLite for analysis.2-
- FlicenseBqualityBmaintenanceEnables scraping and comparing pricing information for LLM inference services across multiple providers (CloudRift, DeepInfra, Fireworks, Groq) using Firecrawl API and SQLite storage.2-
- FlicenseNot gradedqualityCmaintenanceEnables scraping LLM inference pricing from websites like Cloudrift, DeepInfra, Fireworks, and Groq, storing results in SQLite for cost comparison.-
- FlicenseAqualityDmaintenanceEnables scraping and comparison of LLM inference pricing from multiple providers like Cloudrift, DeepInfra, Fireworks, and Groq, storing results in a SQLite database.2-
- FlicenseBqualityCmaintenanceAn AI-powered chatbot that researches and tracks LLM inference pricing across providers, stores structured pricing data locally, and answers pricing questions via natural language.2-
- AlicenseNot gradedqualityBmaintenanceMCP server for monitoring competitor pricing pages, scraping pricing data into SQLite, and answering plain-language questions about pricing plans via Claude.MIT
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.