Skip to main content
Glama
yevhen-kalyna

autoria-mcp

Related Servers

Alternatives to autoria-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI assistants real-time access to Polish used car market data via the CarDossier Market API, enabling queries on valuations, price history, liquidity, and regional prices.
      5
      25 PyPI
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Smartcar's vehicle API as tools, enabling AI agents to query vehicle telemetry and send commands using natural language.
      -
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that integrates with the Carvana marketplace to enable vehicle searching, financing estimation, and trade-in value assessments. It allows AI assistants to retrieve detailed vehicle information, history reports, and market insights directly from Carvana's inventory.
      10
      6 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      A lightweight MCP server that exposes Crawl4AI web scraping and crawling capabilities as tools for AI agents, enabling single-page scraping and multi-page crawling with adaptive stopping.
      114
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Universal MCP server for the Avito API (Russia's largest classifieds marketplace), built for autonomous AI agents to operate an account hands-free — 145 tools across 18 domains (listings, messenger, orders, delivery, promotion, autoload, reviews, analytics). Safe-by-default: dry-run, idempotency, structured errors, confirmation flow.
      144
      159 npm
      17
      MIT

    TDQS

    A3.9/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap among the many list_ tools (e.g., list_body_styles vs list_all_body_styles) and between list_options variants. Descriptions help clarify the differences, so an agent can generally select the correct tool.

    Naming Consistency4/5

    The naming pattern is mostly consistent with underscore-separated verbs (list_, lookup_, get_, search_). Minor exceptions like 'raw_search' (prefix instead of verb) and 'list_bodies_by_generation' (plural vs singular) are deviations, but they do not cause confusion.

    Tool Count3/5

    30 tools is on the high side, but the domain (used car search and reference data) is broad. Some consolidation of the many list_ tools could be considered, but each tool serves a specific API endpoint and the count is justified for full coverage.

    Completeness5/5

    The tool surface covers all major workflows: browsing reference data (brands, models, regions, etc.), searching listings, getting details, batch operations, average price analysis, and VIN decoding. There are no obvious gaps for a read-only car search assistant.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues