io.github.TheSnakeFang/buyapi-mcp

Est-ce que io.github.TheSnakeFang/buyapi-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.TheSnakeFang/buyapi-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• stacks.findSimilar≈ 224 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
    Maximum stacks to return
  • vendorId · string · optionnel
    Optional BuyAPI vendor ID, e.g. /database/convex

  Exemple d'appel

  {"name": "stacks.findSimilar", "arguments": {"limit": 1, "vendorId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"stacks": []}}

• stacks.recommend≈ 845 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • workload · object · optionnel
    Explicit workload assumptions for directional cost estimates. Missing fields become assumptions, not fabricated precision.
  • stackFacts · object · optionnel
    Optional derived stack facts such as languages, frameworks, runtimes, package managers, test tools, and dev workflow. Do not pass source code or secrets.
  • constraints · string · optionnel
    Budget, scale, existing tools, team size, compliance needs
  • stackContext · array · optionnel
    Optional existing stack context from a repo scan or saved private stack. Agents should pass derived tool metadata only, not source code.
  • projectDescription · string · requis
    What the user is building

  Exemple d'appel

  {"name": "stacks.recommend", "arguments": {"projectDescription": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"stack": {}, "claims": [], "sources": [], "coverage": {}, "unknowns": [], "costEstimate": {}, "decisionMatrix": [], "alternativesConsidered": []}}

• vendors.compare≈ 508 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • query · string · requis
    The user's decision context
  • workload · object · optionnel
    Explicit workload assumptions for directional cost estimates. Missing fields become assumptions, not fabricated precision.
  • vendorIds · array · requis
    BuyAPI vendor IDs, e.g. ['/database/convex', '/database/neon']

  Exemple d'appel

  {"name": "vendors.compare", "arguments": {"query": "texte", "vendorIds": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"kind": "texte", "query": "texte", "claims": [], "message": "texte", "coverage": {}, "decisionMatrix": [], "suggestedNextSteps": [], "availableCategories": []}}

• vendors.details≈ 284 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · optionnel
    Specific question to focus the response on
  • vendorId · string · requis
    BuyAPI vendor ID, e.g. /database/supabase

  Exemple d'appel

  {"name": "vendors.details", "arguments": {"vendorId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"claims": [], "sources": [], "coverage": {}}}

• vendors.estimateCost≈ 534 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • category · string · optionnel
    Optional category to estimate across the current corpus
  • workload · object · requis
    Explicit workload assumptions for directional cost estimates. Missing fields become assumptions, not fabricated precision.
  • vendorIds · array · optionnel
    Optional vendor IDs to estimate directly

  Exemple d'appel

  {"name": "vendors.estimateCost", "arguments": {"workload": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"kind": "texte", "query": "texte", "claims": [], "message": "texte", "coverage": {}, "estimates": [], "suggestedNextSteps": [], "availableCategories": []}}

• vendors.evidence≈ 284 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · number · optionnel
    Maximum rows to return
  • subjectId · string · requis
    Subject ID, e.g. /database/supabase or database
  • subjectType · string · requis · vendor | category | stack | comparison
    Evidence subject type

  Exemple d'appel

  {"name": "vendors.evidence", "arguments": {"subjectId": "texte", "subjectType": "vendor"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"evidence": []}}

• vendors.resolve≈ 444 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    The user's question or task context for relevance ranking
  • category · string · optionnel
    Optional category: database, auth, hosting, payments, email, analytics, feature-flags

  Exemple d'appel

  {"name": "vendors.resolve", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"kind": "texte", "query": "texte", "claims": [], "message": "texte", "results": [], "coverage": {}, "decisionMatrix": [], "suggestedNextSteps": [], "availableCategories": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://buyapi.ai/api/mcp