vindex-mcp
Related Servers
Alternatives to vindex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceTrust layer for AI agents: 22 pay-per-call x402 tools for scam and fraud checks, payment pre-flight, wallet screening, policy approvals, contact extraction and company research. Free preview with no wallet; paid calls settle in USDC on Base.22104 npmMIT
- AlicenseCqualityAmaintenanceKeyword Metrics for Google Ads search volume, CPC, advertising competition and monthly history. Optional AI Search Volume provides modeled question-demand signals, not actual ChatGPT or Perplexity query counts. Free discovery and quotes; paid calls require an approved budget and use USDC on Base via x402. Also includes SERP, domain and local-market research.78398 npmMIT
- AlicenseAqualityCmaintenancePay-per-call data and tools for AI agents over x402, by UnyKorn. 360 endpoints: DeFi and market data, multi-chain wallet reads, wallet and token risk signals, SEC filings, web and domain intel, and AI text tools. Settled per call in USDC on Base ($0.001-$0.25). No API keys or subscriptions; unpaid calls return the exact quote first.21MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run honeypot and owner-power safety checks on Base tokens and to read wallet ETH and USDC balances, with every answer sourced from real chain data and paid per call in USDC via x402.MIT

AgentBIT MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to call 50+ pay-per-request tools covering onchain and crypto data, web research, security, compliance screening, business intelligence, and infrastructure checks. Payments settle per call in USDC on Base through the x402 protocol with no accounts, API keys, or subscriptions, and the first call is free for new wallets.MIT- AlicenseAqualityDmaintenanceEnables AI agents to access crypto/web3 data across 5 chains with pay-per-call billing in USDC via x402, no API key required, and built-in spend caps.3649 npmMIT
TDQS
Scored across 7 tools
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.
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.
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.
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.