Skip to main content
Glama
jcislo

vindex-mcp

by jcislo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to vindex-mcp

No user-submitted related servers found.

    Related Servers

    • @connskill/mcp-growth-services by CONN-SKILL

      @connskill/mcp-growth-servicesofficial

      CONN-SKILL
      A
      license
      Not graded
      quality
      B
      maintenance
      Pay-per-call access to SEO and SERP data, keyword research, backlink and site audits, local business search, SMS verification, social marketing, EU-hosted LLM inference, and read-only on-chain calls. No signup and no API key: agents pay per request in USDC on Base via x402.
      54 npm
      MIT

    • Nexus Intelligence MCP Server

      ROGT7
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to call 93 pay-per-call machine-to-machine services spanning web scraping, crypto sentiment, market data, on-chain analytics, social and threat intelligence, vulnerability scanning, and micro-SaaS utilities. Payments are settled in USDC on Arbitrum via the x402 protocol using a wallet header, so no API keys, signups, or billing setup are required.
      MIT

    • agentpay

      ronaldanton
      A
      license
      Not graded
      quality
      C
      maintenance
      Pay-per-call AI microservices settled in USDC on Base via the x402 (HTTP 402) protocol. 28 tools including web search, summarization, extraction, code review, deep research, crypto safety, sanctions screening and on-chain data — no accounts or API keys.
      6 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: health, pricing, sample, decode, recalls, costs, and known issues. There is no overlap in primary functionality, and even the bundled data in get_known_issues does not conflict with the dedicated tools.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun snake_case pattern. Most use the get_ prefix, and decode_vin uses a different verb but still follows the same grammatical structure, making the set predictable and easy to navigate.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a VIN data API: 3 free discovery tools and 4 paid data endpoints. Each tool earns its place and the count is within the ideal 3-15 range.

    Completeness5/5

    The tool surface covers the full lifecycle of the VIN data domain: discovery (pricing, sample, health), core decoding, recalls, purchase costs, and known issues. No obvious gaps exist, as the sample tool explicitly enumerates the four paid endpoint shapes, all of which are implemented.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources