goofish-price-mcp
Related Servers
Alternatives to goofish-price-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that lets local AI agents query bank transactions stored in a local SQLite database, with tools for accounts, transaction search, spending summaries, recurring charges, trends, themes, subscriptions, and store health.2MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for SQLite databases, enabling AI assistants to safely query and inspect database schemas without write access.MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server that lets AI agents query SageRead data: books, reading progress, stats, notes, AI chats, papers, and semantic vector search, with API keys staying inside the app. Supports both Better SageRead and upstream SageRead data directories.223 npm1MIT
- AlicenseAqualityCmaintenanceRead-only MCP server that lets AI agents safely query SQLite, PostgreSQL, and MySQL/MariaDB. Enforces read-only transactions with column masking, row caps, query timeouts, EXPLAIN-based cost rejection, and rate limiting.734 npm2MIT
- FlicenseAqualityDmaintenanceA local MCP server that enables querying Amazon Selling Partner API for profitability analysis (revenue, fees, COGS, net margin) and inventory alerts (FBA stock levels and low-stock warnings) using read-only operations.9-
- AlicenseAqualityBmaintenanceRead-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.4268 npm1ISC
TDQS
Scored across 4 tools
Each tool has a reasonably distinct target: per-keyword deep stats, per-item listing, cross-keyword snapshot, and task listing. The only soft overlap is between get_price_stats and market_overview, which both return aggregate prices (one deep per keyword, one shallow across all); descriptions clarify the split but an agent could still pick the wrong one for a quick check.
All names are snake_case, but the conventions are mixed: get_price_stats and list_watch_tasks use verb_noun while latest_items and market_overview are bare noun phrases. It remains readable, but the set does not follow a single predictable pattern.
Four tools is on the lean side but each covers a distinct query surface (stats, items, overview, tasks) with no filler. It is appropriately scoped for a read/query-oriented price monitoring server.
The read side is covered (stats, item lists, overview, task listing), but the monitoring lifecycle is incomplete: list_watch_tasks exists with no create_watch_task, update, or delete counterpart, so an agent cannot start or stop monitoring a keyword. No tool exposes per-item history or cross-keyword comparison either.