BuyAPI
NPM · BUYAPI · 2 COMPONENTS
Vendor intelligence for AI coding agents choosing developer tools and stacks.
Available components
Last scanned (1 hour ago)
Scores higher than 87% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 184 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 825 tokens (~117/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/buyapi@0.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
stacks.findSimilar ~80
Finds public stack profiles 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum stacks to return |
| vendorId | string | – | Optional BuyAPI vendor ID, e.g. /database/convex |
| Name | Type | Req | Description |
|---|---|---|---|
| stacks | array | yes | – |
No examples provided.
stacks.recommend ~213
Recommends 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 stack choice. Do not use this for local coding/debugging/docs questions that do not involve software or vendor selection. Do not call vendors.resolve first; this tool handles retrieval and ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | string | – | Budget, scale, existing tools, team size, compliance needs |
| projectDescription | string | yes | What the user is building |
| stackContext | array | – | Optional existing stack context from a repo scan or saved private stack. Pass derived tool metadata only, not source code. |
| stackFacts | object | – | Optional derived stack facts such as languages, frameworks, runtimes, package managers, test tools, and dev workflow. Do not pass source code or secrets. |
| workload | object | – | Explicit workload assumptions for deterministic cost estimates. Missing fields become assumptions, not fabricated precision. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternativesConsidered | array | – | – |
| costEstimate | object | – | – |
| decisionMatrix | array | – | – |
| sources | array | – | – |
| stack | object | – | – |
| unknowns | array | – | – |
No examples provided.
vendors.compare ~114
Compares two or more BuyAPI vendors for a specific workload or decision. Use this for head-to-head questions like "Convex vs Supabase vs Neon for a realtime SaaS" or "Stripe vs Paddle for a marketplace".
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The user's decision context |
| vendorIds | array | yes | BuyAPI vendor IDs, e.g. ['/database/convex', '/database/neon'] |
| workload | object | – | Explicit workload assumptions for deterministic cost estimates. Missing fields become assumptions, not fabricated precision. |
| Name | Type | Req | Description |
|---|---|---|---|
| availableCategories | array | – | – |
| decisionMatrix | array | – | – |
| kind | string | – | – |
| message | string | – | – |
| query | string | – | – |
| suggestedNextSteps | array | – | – |
No examples provided.
vendors.details ~84
Retrieves detailed vendor information including pricing, features, limits, gotchas, comparisons, and source provenance. Call vendors.resolve first unless the user already provided a BuyAPI vendor ID like /database/supabase.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Specific question to focus the response on |
| vendorId | string | yes | BuyAPI vendor ID, e.g. /database/supabase |
| Name | Type | Req | Description |
|---|---|---|---|
| sources | array | – | – |
No examples provided.
vendors.estimateCost ~104
Produces deterministic monthly cost estimates from BuyAPI pricing data and explicit workload inputs. Use this when the user asks for cost math. Missing workload fields are returned as assumptions or unknowns instead of being hallucinated.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category to estimate across the current corpus |
| vendorIds | array | – | Optional vendor IDs to estimate directly |
| workload | object | yes | Explicit workload assumptions for deterministic cost estimates. Missing fields become assumptions, not fabricated precision. |
| Name | Type | Req | Description |
|---|---|---|---|
| availableCategories | array | – | – |
| estimates | array | – | – |
| kind | string | – | – |
| message | string | – | – |
| query | string | – | – |
| suggestedNextSteps | array | – | – |
No examples provided.
vendors.evidence ~96
Returns recent BuyAPI evidence rows for a vendor, category, stack, or comparison. Use this when the user asks why BuyAPI believes something, what sources support a vendor page, or what recent human/source signals exist.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum rows to return |
| subjectId | string | yes | Subject ID, e.g. /database/supabase or database |
| subjectType | string | yes | Evidence subject type |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | yes | – |
No examples provided.
vendors.resolve ~134
Finds BuyAPI vendor IDs for a user question. Category is optional; provide it when known. Use this for vendor discovery before vendors.details, or when the user asks which provider in a category fits their constraints. Do not use this for local coding/debugging/docs questions unless they involve choosing a software vendor or tool. If the category is outside BuyAPI's corpus, the tool returns an explicit "not in corpus yet" result instead of inventing vendors.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category: database, auth, hosting, payments, email |
| query | string | yes | The user's question or task context for relevance ranking |
| Name | Type | Req | Description |
|---|---|---|---|
| availableCategories | array | – | – |
| kind | string | – | – |
| message | string | – | – |
| query | string | – | – |
| results | array | – | – |
| suggestedNextSteps | array | – | – |
No examples provided.
How do I install the BuyAPI MCP server?
BuyAPI runs locally as an npm package, launched with npx -y buyapi. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · buyapi
claude mcp add thesnakefang-buyapi-mcp -- npx -y buyapi
What is the BuyAPI MCP server?
BuyAPI is an MCP server listed in the public MCP registry as io.github.TheSnakeFang/buyapi-mcp. Vendor intelligence for AI coding agents choosing developer tools and stacks. This page covers its npm package (buyapi).
Is the BuyAPI MCP server safe to use?
BuyAPI scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BuyAPI MCP server expose?
BuyAPI exposes 7 tools: vendors.resolve, vendors.details, vendors.evidence, stacks.findSimilar, vendors.compare, and 2 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.
Is the BuyAPI MCP server still maintained?
BuyAPI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the BuyAPI MCP server under?
BuyAPI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.