BuyAPI
io.github.TheSnakeFang/buyapi-mcp · v0.7.1
Vendor intelligence for AI coding agents choosing developer tools and stacks.
MCPremotelocal · npmno credentialsDatabases
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 7 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 100/100
What it does: 7 tools · 7 read, 0 write · Databases
Test call stacks.findSimilar: worked (1,081 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://buyapi.ai/api/mcpPackage
registry: npm
identifier: buyapi
version: 0.7.1
transport: stdioTools
7 tools listed at last check
vendors.resolveFirst stop for category-specific vendor recommendations and vendor ID discovery. Finds BuyAPI vendor IDs for a user question; provide category when known. Use this when the user asks which provider in a category fits their constraints. With a covered category, the response includes ranked results pvendors.detailsFollow-up tool for one known vendor. Retrieves detailed pricing, features, limits, gotchas, comparisons, and source provenance. Call vendors.resolve first unless the user already provided a BuyAPI vendor ID like /database/supabase. Use this after a candidate is selected and the user needs claim-levvendors.evidenceReturns recent reviewed BuyAPI evidence rows for a vendor, category, stack, or comparison. Use this when the user asks why BuyAPI believes something, what sources support a recommendation, or what recent human/source/opinion/history signals exist. This is a trust and provenance follow-up, not the fstacks.findSimilarFinds reviewed public stack examples related to a vendor, or recent curated stack examples. Use this when the user asks who uses a tool, what similar builders use, or wants examples of real stack combinations. Do not use it as a generic recommendation tool.vendors.compareCompares two or more already-known BuyAPI vendors for a specific workload or decision. Use this when the candidate set is known, for head-to-head questions like "Convex vs Supabase vs Neon for a realtime SaaS" or "Stripe vs Paddle for a marketplace". If the user has not named candidates, use vendorvendors.estimateCostProduces directional monthly cost estimates from BuyAPI pricing data and explicit workload inputs. Use this only when the user asks for cost math and provides explicit workload inputs. Missing workload fields are returned as assumptions or unknowns instead of being hallucinated. Treat results as Bustacks.recommendRecommends a complete stack from BuyAPI's corpus with a structured decision matrix, cost estimate, assumptions, unknowns, alternatives, and sources. Use this when the user is starting a project or asks for a complete multi-layer stack choice. Do not use this for local coding/debugging/docs question
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.TheSnakeFang/buyapi-mcp)