car-listing-check-mcp
Related Servers
Alternatives to car-listing-check-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAnalyze headshot / Bewerbungsfoto framing, resolution and checklist readiness for job applications (remote Streamable HTTP; Cloudflare Worker).2MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to submit a storefront URL and receive an A–F conversion-readiness grade across 20 weighted checks, including specific failing checks. Calls are paid per use in USDC via x402, requiring no accounts or API keys.MIT
DealScore MCPDeprecated
FlicenseNot gradedqualityBmaintenanceEnables agents to evaluate car deals by returning a deal grade, numeric score, market price comparison, comps summary, risks, and confidence from a VIN or vehicle attributes without scraping listings.-- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for website SEO + GEO analysis. Scan any URL to get scores across 5 categories (SEO, GEO, Performance, Security, Accessibility) with actionable fix recommendations. Enables AI coding assistants to audit websites and implement fixes autonomously.-
- AlicenseAqualityBmaintenanceAuto-Apply That Ends on an Interview. Job matches, applications submitted on the employer's own hiring system automatically or after your approval, employer-receipt tracking, a resume rewritten for each role, cover letters and interview prep. Hosted remote server over Streamable HTTP with OAuth 2.1.412,047 npm4MIT
- FlicenseNot gradedqualityNot gradedmaintenanceURL reality check for AI agents — returns HTTP status, SHA-256 content hash, classification, readability score, title, and wayback-machine fallback when dead, cached 10 minutes at $0.001 per call.-
TDQS
Scored across 2 tools
The two tools target clearly different needs: check_car_listing evaluates a specific supplied listing and returns a score with fixes, while get_car_listing_checklist returns static market-specific guidance. Each description explicitly excludes the other's territory (no fetching, no inspecting) and states when not to use it, leaving little room for misselection.
Both names follow a clean verb_noun snake_case pattern (check_car_listing, get_car_listing_checklist) with a shared domain noun, making the action/object relationship obvious. No mixed conventions or vague verbs.
Two tools is thin even for a narrowly scoped listing checker; the checklist could plausibly be an argument of the check tool rather than a separate endpoint, and there is no batch or comparison capability. It is not egregiously over- or under-scoped, but it sits at the borderline of feeling sparse.
The core lifecycle of 'get guidance, then score a listing' is covered, including multi-market checklists and optional field/photo inputs. Minor gaps exist around batch checking of multiple listings or re-checking after edits, but agents can work around these by calling the tool repeatedly.