BuyAPI
REMOTE · BUYAPI.AI · 2 COMPONENTS · SCANNED AUG 3
Vendor intelligence for AI coding agents choosing developer tools and stacks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 988 tokens (~141/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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · buyapi.ai
claude mcp add --transport http thesnakefang-buyapi-mcp https://buyapi.ai/api/mcp
[mcp_servers.thesnakefang-buyapi-mcp] url = "https://buyapi.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thesnakefang-buyapi-mcp": {
"type": "remote",
"url": "https://buyapi.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add thesnakefang-buyapi-mcp --url https://buyapi.ai/api/mcp --transport streamable-http
mcp_servers:
thesnakefang-buyapi-mcp:
url: "https://buyapi.ai/api/mcp" {
"mcpServers": {
"thesnakefang-buyapi-mcp": {
"type": "http",
"url": "https://buyapi.ai/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 +40
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 27
First indexed and scored.
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 3 Aug 2026 · Probed https://buyapi.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=buyapi.ai | CN=YR1,O=Let's Encrypt,C=US | 10 Jun 2026 | 8 Sept 2026 | RSA 2048 | SHA256-RSA | 5302a9c89e0548c9870cf852b3a22f2a7d1 |
| SANs: buyapi.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC secure
Validation of buyapi.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| buyapi.ai. | present | 40992 | 13 | Verified |
| buyapi.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://buyapi.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://buyapi.ai/api/mcp | HTTPS enforced | 308 | https://buyapi.ai/api/mcp |
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.
stacks.findSimilar ~92
Finds 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.
| 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 ~217
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 multi-layer 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. Agents should 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 directional cost estimates. Missing fields become assumptions, not fabricated precision. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternativesConsidered | array | — | — |
| claims | array | — | — |
| costEstimate | object | — | — |
| coverage | object | — | — |
| decisionMatrix | array | — | — |
| sources | array | — | — |
| stack | object | — | — |
| unknowns | array | — | — |
No examples provided.
vendors.compare ~136
Compares 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 vendors.resolve first.
| 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 directional cost estimates. Missing fields become assumptions, not fabricated precision. |
| Name | Type | Req | Description |
|---|---|---|---|
| availableCategories | array | — | — |
| claims | array | — | — |
| coverage | object | — | — |
| decisionMatrix | array | — | — |
| kind | string | — | — |
| message | string | — | — |
| query | string | — | — |
| suggestedNextSteps | array | — | — |
No examples provided.
vendors.details ~113
Follow-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-level pricing, limit, gotcha, or provenance details.
| 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 |
|---|---|---|---|
| claims | array | — | — |
| coverage | object | — | — |
| sources | array | — | — |
No examples provided.
vendors.estimateCost ~142
Produces 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 BuyAPI claim-based estimate math; verify exact billing in first-party docs, vendor CLIs, or vendor MCPs before purchase or production decisions.
| 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 directional cost estimates. Missing fields become assumptions, not fabricated precision. |
| Name | Type | Req | Description |
|---|---|---|---|
| availableCategories | array | — | — |
| claims | array | — | — |
| coverage | object | — | — |
| estimates | array | — | — |
| kind | string | — | — |
| message | string | — | — |
| query | string | — | — |
| suggestedNextSteps | array | — | — |
No examples provided.
vendors.evidence ~114
Returns 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 first recommendation tool.
| 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 ~174
First 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 plus a top-3 decision matrix with fit labels, confidence, tradeoffs, cost notes, freshness, and sources. 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, analytics, feature-flags |
| query | string | yes | The user's question or task context for relevance ranking |
| Name | Type | Req | Description |
|---|---|---|---|
| availableCategories | array | — | — |
| claims | array | — | — |
| coverage | object | — | — |
| decisionMatrix | array | — | — |
| kind | string | — | — |
| message | string | — | — |
| query | string | — | — |
| results | array | — | — |
| suggestedNextSteps | array | — | — |
No examples provided.