TiresVote MCP
OfficialRelated Servers
Alternatives to TiresVote MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes 11 agent-native QA tools over stdio so coding agents can discover a project, analyze risk, select the smallest relevant test set, generate and dry-run tests, triage failures, propose tiered heals, analyze flakes, generate quality reports, and evaluate release readiness. Planning and healing tools stay read-only or propose-only, while execution defaults to dry-run, keeping agent actions safe and evidence-backed.MIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to interact with Ethereum, Base and configurable EVM chains over stdio using the shared command catalog, covering contract reads, prepared and policy-guarded execution, wallet management, Socket swaps and bridging, simulation, monitoring and saved contracts.-
- AlicenseAqualityCmaintenanceProvides vehicle wheel and tyre fitment data for 10,000+ makes, models, and trim levels through 32 read-only tools, enabling searches by vehicle, rim, or tire specifications.3248 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides AI agents read-only analytical access to a SQLite database over stdio, with tools for listing tables, describing schemas, and running paginated SQL queries.-
- FlicenseNot gradedqualityBmaintenance24 free personal-finance and macro tools (mortgage, paycheck, tax, FRED, BLS) for LLM agents. Zero API keys, stdio transport, source-cited from IRS, Federal Reserve, BLS, Treasury, and Freddie Mac.-
- AlicenseAqualityBmaintenanceEnables AI agents to explore PostgreSQL schemas, run read-only queries, inspect execution plans, and receive evidence-backed SQL diagnostics with reproducible optimization benchmarks over local stdio.51MIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource and action: reference lists (brands, regions, performance categories), catalog browsing (brand tires, sizes), two clearly differentiated searches (name vs filters), detail retrieval (tire card, test), and ancillary content (pros/cons, materials, tests). The descriptions explicitly contrast similar tools (e.g., tires_search vs tires_search_advanced, tires_list_brand_tires vs advanced brand filter), so misselection is unlikely.
All tools use a consistent `tires_` prefix and snake_case verb_noun pattern (`list_*`, `get_*`, `search`, `search_advanced`). The convention is predictable throughout with no mixed styles or ambiguous abbreviations.
12 tools is well within the 3–15 sweet spot and each tool covers a distinct facet of the tire catalog domain (reference data, search, detail, reviews, materials, tests). No tool appears redundant or padding the count.
The read-only catalog surface covers brands, models, sizes, regions, performance categories, name/filter search, and supplementary content like pros/cons, materials, and tests. Minor gaps exist (e.g., no reference list for automobile types or seasons, and no per-region detail tool), but these are documented limitations rather than dead ends for core workflows.