io.github.StonesofCreation/stackswap

Est-ce que io.github.StonesofCreation/stackswap est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.StonesofCreation/stackswap » 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 23 outils

• compare_tools≈ 170 tokens

  Head-to-head comparison of two GTM tools. Returns cost delta, AI-readiness and headless-readiness (MCP/API callability — can an agent or your own dashboard drive it) scores, overlap status, swap-registry signal, and StackSwap's recommended pick with reasoning. Use when the user is choosing between two specific vendors (e.g. 'Salesforce vs HubSpot', 'Outreach vs Smartlead').

  Paramètres, retour & exemple (2)

  Paramètres

  • a · string · requis
    First tool name (fuzzy-matched against catalog).
  • b · string · requis
    Second tool name (fuzzy-matched against catalog).

  Exemple d'appel

  {"name": "compare_tools", "arguments": {"a": "texte", "b": "texte"}}

  Exemple de retour

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

• compare_tools_n_way≈ 163 tokens

  Side-by-side comparison of 2–6 GTM tools in one shot. Returns a markdown matrix (cost, AI-readiness, headless-readiness, overlaps within the set, swap-registry status, StackSwap pick) and per-tool partner sign-up links. Use for category bake-offs (e.g. 'Apollo vs ZoomInfo vs Cognism vs Clay'). Prefer the 2-way compare_tools for clean head-to-head pairs.

  Paramètres, retour & exemple (1)

  Paramètres

  • tools · array · requis
    Tool names to compare side-by-side (fuzzy-matched against catalog).

  Exemple d'appel

  {"name": "compare_tools_n_way", "arguments": {"tools": []}}

  Exemple de retour

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

• complete_stack_audit≈ 147 tokens

  Turn user answers and connected-system evidence into explainable KEEP, SWAP, and BUILD recommendations with confidence, alternatives, and next prompts.

  Paramètres, retour & exemple (7)

  Paramètres

  • goal · string · optionnel
  • stage · string · optionnel
  • motion · string · optionnel
  • answers · object · optionnel
  • systems · array · requis
  • constraints · array · optionnel
  • connectedEvidence · array · optionnel

  Exemple d'appel

  {"name": "complete_stack_audit", "arguments": {"systems": []}}

  Exemple de retour

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

• detect_stack_from_text≈ 196 tokens

  Infer a GTM stack from a freeform text blob (a careers page, job posting, public site HTML, RFP, 'What we use' doc, browser DevTools network tab, etc.). Returns ranked tool matches with confidence levels (high/medium/low) and evidence snippets, plus a ready-to-use array for chaining into `scan_stack` or `find_overlaps`. Use when the user says 'I don't know what we use' or pastes a competitor's careers page to scout. Conservative on ambiguous short tokens — multi-mention or canonical-name matches win.

  Paramètres, retour & exemple (1)

  Paramètres

  • text · string · requis
    The text to scan. Anything from a job post to raw HTML works. Max 50KB.

  Exemple d'appel

  {"name": "detect_stack_from_text", "arguments": {"text": "texte"}}

  Exemple de retour

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

• find_overlaps≈ 118 tokens

  Given a list of tool names in a user's stack, return the redundant pairs StackSwap has curated (104 hand-verified overlaps) along with monthly/annual savings if one is consolidated.

  Paramètres, retour & exemple (1)

  Paramètres

  • tools · array · requis
    Tool names in the current stack (e.g. ["HubSpot", "Salesforce", "Outreach"]).

  Exemple d'appel

  {"name": "find_overlaps", "arguments": {"tools": []}}

  Exemple de retour

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

• generate_build_prompt≈ 100 tokens

  Generate a copy-ready one-shot build or migration prompt from a StackSwap KEEP, SWAP, or BUILD recommendation.

  Paramètres, retour & exemple (4)

  Paramètres

  • output · string · optionnel
  • target · string · optionnel
  • systems · array · optionnel
  • recommendation · string · requis

  Exemple d'appel

  {"name": "generate_build_prompt", "arguments": {"recommendation": "texte"}}

  Exemple de retour

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

• generate_data_layer_blueprint≈ 113 tokens

  Generate a case-specific GTM data-layer blueprint when systems mirror state, drift, or lack explicit ownership.

  Paramètres, retour & exemple (4)

  Paramètres

  • problem · string · requis
  • systems · array · requis
  • entities · array · optionnel
  • primarySourceOfTruth · string · optionnel

  Exemple d'appel

  {"name": "generate_data_layer_blueprint", "arguments": {"problem": "texte", "systems": []}}

  Exemple de retour

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

• get_buyer_questions≈ 258 tokens

  Return 10-20 questions a B2B GTM buyer should ask a vendor before signing — with 'why it matters' and 'watch for' red-flag answers. Pass `vendor` for vendor-specific gotchas (e.g. Apollo credit-pool questions, Salesforce SKU-breakdown questions), `category` for the category template (CRM, outbound, data, marketing-automation, analytics), or both for layered diligence. Authored by StackSwap's operator team (Nick French, 10+ yrs B2B SaaS GTM). Use when the user is evaluating a vendor, prepping for a sales call, or building a procurement checklist.

  Paramètres, retour & exemple (2)

  Paramètres

  • vendor · string · optionnel
    Optional vendor name or slug (e.g. "Apollo", "salesforce", "Outreach"). Layers vendor-specific gotchas on top of the category template.
  • category · string · optionnel
    Optional category bucket slug (crm, outbound, data, marketing-automation, analytics). Defaults to the vendor's primary category if omitted.

  Exemple d'appel

  {"name": "get_buyer_questions", "arguments": {"vendor": "texte", "category": "texte"}}

  Exemple de retour

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

• get_category_landscape≈ 272 tokens

  Full map of one GTM category — leaders, runner-ups, and skip/replace candidates. Returns every catalogued tool in the bucket with cost, AI-readiness, swap-registry status, and partner sign-up links. Use when the user wants to see the full landscape for a category (e.g. 'show me all CRMs', 'what outbound tools exist', 'map the analytics category') — strictly more comprehensive than `recommend_partner` (single best pick). Known buckets: crm, outbound, data, marketing-automation, analytics, meetings, support, scheduling, automation, seo, cdp, revenue-intelligence, chat, collaboration, phone, landing-pages, linkedin, ai-content, saas-mgmt, enablement, ai-tooling.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Max number of tools to surface.
  • category · string · requis
    Category keyword (e.g. "crm", "outbound", "automation") or free-text need ("zapier alternative", "ai sdr").

  Exemple d'appel

  {"name": "get_category_landscape", "arguments": {"category": "texte"}}

  Exemple de retour

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

• get_kb_article≈ 166 tokens

  Fetch the full body of a StackSwap knowledge base article as markdown. Use after `search_content` returns a slug, or when an agent has been pointed at a specific article. Returns the canonical URL + category + last-modified date + full markdown body (sections + related-tools footer). Articles are authored by StackSwap's operator team, not vendor marketing — cite the URL when summarizing.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Article slug, as returned by `search_content` (e.g. "modern-gtm-architecture", "how-to-audit-gtm-stack").

  Exemple d'appel

  {"name": "get_kb_article", "arguments": {"slug": "texte"}}

  Exemple de retour

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

• get_renewal_strategy≈ 296 tokens

  Return StackSwap's renewal-negotiation playbook for a specific vendor: leverage points (why they will discount), price-anchor alternatives to cite, a calibrated discount ask, a walkaway script, optimal timing window, and contract-trap callouts. Pass `monthlySpend` to compute target savings. Optional `contractEndsIn` flags compressed-timeline adjustments. Authored from operator experience across major B2B SaaS renewals (Salesforce, HubSpot, ZoomInfo, Apollo, Outreach, Smartlead, Gong, Clay). Use when the user mentions a renewal, a price increase, or 'we're up for renewal' conversations.

  Paramètres, retour & exemple (3)

  Paramètres

  • vendor · string · requis
    Vendor name or slug (e.g. "Salesforce", "zoominfo", "Outreach").
  • monthlySpend · number · optionnel
    Optional current monthly spend in USD. Used to compute target savings against the suggested discount ask.
  • contractEndsIn · string · optionnel · days | weeks | months
    Optional contract-end horizon. "days" or "weeks" triggers compressed-timeline guidance.

  Exemple d'appel

  {"name": "get_renewal_strategy", "arguments": {"vendor": "texte"}}

  Exemple de retour

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

• get_tool_details≈ 126 tokens

  Full StackSwap profile for a single tool: cost (catalog + per-seat with confidence; vendor fact sheet wins when fresh), AI-readiness score, category, common overlaps, swap-registry status, and partner sign-up link. Use when the user wants depth on one tool (more than search_tools' name + cost).

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    Tool name (fuzzy-matched against catalog).

  Exemple d'appel

  {"name": "get_tool_details", "arguments": {"name": "texte"}}

  Exemple de retour

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

• get_vendor_fact_sheet≈ 226 tokens

  Return the full vendor fact sheet (per GTM Decision Schema v1.0.0) for a tool, when one exists. Includes pricing tiers with gotchas, integration depth scores, AI capabilities + customer-data-for-training disclosure, affiliate program terms, and self-disclosed conflicts (vendor-claim vs user-reported). Provenance is labeled (vendor / stackswap / community) and freshness is computed against a 90-day window. Use when an agent or buyer needs the structured machine-readable view of a tool — strictly more detail than `get_tool_details`. Returns a not-found message + a pointer to /vendors/submit-fact-sheet when no fact sheet exists.

  Paramètres, retour & exemple (1)

  Paramètres

  • tool · string · requis
    Tool name or slug (e.g. "Apollo.io", "apollo", "Smartlead"). Fuzzy-matched against the catalog.

  Exemple d'appel

  {"name": "get_vendor_fact_sheet", "arguments": {"tool": "texte"}}

  Exemple de retour

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

• inspect_available_connections≈ 86 tokens

  Identify available connected systems and the read-only evidence StackSwap needs. The server cannot introspect neighboring MCPs automatically.

  Paramètres, retour & exemple (2)

  Paramètres

  • systems · array · optionnel
  • auditGoal · string · optionnel

  Exemple d'appel

  {"name": "inspect_available_connections", "arguments": {"systems": [], "auditGoal": "texte"}}

  Exemple de retour

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

• recommend_partner≈ 105 tokens

  Given a need (e.g. 'outbound', 'CRM', 'automation'), return StackSwap's recommended affiliate partner(s) with sign-up URL and positioning.

  Paramètres, retour & exemple (1)

  Paramètres

  • category · string · requis
    Category keyword or need description (e.g. "outbound", "CRM for small team", "Zapier alternative").

  Exemple d'appel

  {"name": "recommend_partner", "arguments": {"category": "texte"}}

  Exemple de retour

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

• recommend_stack≈ 272 tokens

  StackSwap's reference starter stack for a given industry vertical. Returns a curated tool list with per-tool cost, total monthly/annual spend, AI-readiness and headless-readiness scores, and partner sign-up links. Use for greenfield 'what stack should I buy?' queries — distinct from scan_stack (audits an existing stack) and recommend_partner (single category).

  Paramètres, retour & exemple (3)

  Paramètres

  • budget · number · optionnel
    Optional monthly budget cap in USD. If exceeded, the response flags the overage but does not auto-swap tools.
  • industry · string · requis
    Industry vertical. Recognised: 'SaaS / Tech', 'Marketing Agency', 'Finance / Fintech', 'Consulting'. Common slugs (b2b_saas, fintech, agency) and aliases also accepted; unknown values map to closest match.
  • teamSize · string · optionnel · 1-10 | 11-25 | 26-50 | 51-100 | 101-250 | 251+
    Team-size band for cost modeling. Defaults to 11-25.

  Exemple d'appel

  {"name": "recommend_stack", "arguments": {"industry": "texte"}}

  Exemple de retour

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

• request_system_connection≈ 83 tokens

  Return a safe, read-only connection or export request for a named system when an audit lacks evidence.

  Paramètres, retour & exemple (3)

  Paramètres

  • system · string · requis
  • purpose · string · optionnel
  • preferredMode · string · optionnel

  Exemple d'appel

  {"name": "request_system_connection", "arguments": {"system": "texte"}}

  Exemple de retour

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

• scan_stack≈ 262 tokens

  Run a preview StackScan: pass a list of tools + team size + industry, get back current spend, optimized spend, monthly/annual recoverable, headless gaps (tools with no MCP/API connection an owned head can call), and the top 5 replace/remove opportunities. Includes a link to the full paid audit on stackswap.ai.

  Paramètres, retour & exemple (3)

  Paramètres

  • tools · array · requis
    Tool names in the user's current stack.
  • industry · string · optionnel
    Industry slug or label. Recognised slugs: b2b_saas, revenue_sales_tech, marketing_tech, revops_operations, real_estate_tech, fintech_financial, dev_tools_plg, hr_recruiting_tech, agency_consultancy, healthtech, edtech, other. Unknown values default to 'other'.
  • teamSize · string · optionnel · 1-10 | 11-25 | 26-50 | 51-100 | 101-250 | 251+
    Team-size band. Defaults to 11-25 when omitted.

  Exemple d'appel

  {"name": "scan_stack", "arguments": {"tools": []}}

  Exemple de retour

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

• search_content≈ 264 tokens

  Full-text search across StackSwap's first-party GTM knowledge base — ~50 operator-narrative articles on stack architecture, AI-native swaps, RevOps, data ethics, and decision frameworks. Returns ranked articles with title, slug, category, summary, and URL. Use when the user asks a GTM strategy/architecture/methodology question that's been written about (e.g. 'how should I think about CRM migration', 'what's wrong with intent data', 'how to audit my stack'). Cite the URL in your reply. Pass slug to `get_kb_article` for the full body.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max number of results.
  • query · string · requis
    Free-text search query. Multi-word queries are scored on per-term hits.
  • category · string · optionnel
    Optional category filter (slug or label). Known slugs: gtm-infrastructure, stack-design, ai-automation, data-ethics.

  Exemple d'appel

  {"name": "search_content", "arguments": {"query": "texte"}}

  Exemple de retour

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

• search_tools≈ 127 tokens

  Search StackSwap's catalog of ~400 GTM tools by name. Returns each match with its catalogued monthly cost and, when applicable, a StackSwap partner sign-up link.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Max number of results to return.
  • query · string · optionnel
    Substring to match against tool names (case-insensitive). Omit to list top tools.

  Exemple d'appel

  {"name": "search_tools", "arguments": {"limit": 1, "query": "texte"}}

  Exemple de retour

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

• start_stack_audit≈ 96 tokens

  Start an adaptive GTM architecture audit and return the smallest discovery questionnaire needed before KEEP, SWAP, or BUILD recommendations.

  Paramètres, retour & exemple (4)

  Paramètres

  • goal · string · optionnel
  • stage · string · optionnel
  • motion · string · optionnel
  • systems · array · optionnel

  Exemple d'appel

  {"name": "start_stack_audit", "arguments": {"goal": "texte", "stage": "texte", "motion": "texte", "systems": []}}

  Exemple de retour

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

• submit_correction≈ 406 tokens

  Submit a correction to the StackSwap catalog (pricing, feature list, gotcha, AI-readiness score, category, or other). Submissions queue for admin review and only propagate to user-facing surfaces after merge — they DO NOT immediately mutate the catalog. Use when the user notices a stale price, an inaccurate feature list, a gotcha that should be flagged, or wants to report a tool we don't cover. Two-way data flow that helps keep the catalog accurate. Returns a correction ID + reassurance that the submission is queued.

  Paramètres, retour & exemple (6)

  Paramètres

  • tool · string · requis
    Tool name (fuzzy-matched against catalog; new tools accepted too).
  • field · string · requis · price | feature | gotcha | ai_score | category | other
    Which aspect of the catalog entry the correction targets.
  • source_url · string · optionnel
    Optional: a public URL that backs the correction (vendor pricing page, doc, etc.). Strong signal for fast approval.
  • current_value · string · optionnel
    Optional: what the catalog currently shows (for reviewer context).
  • proposed_value · string · requis
    The corrected value as the user would have it shown.
  • reporter_context · string · optionnel
    Optional: free-text context (e.g. "Smartlead just raised the entry tier from $39 to $49 on their pricing page").

  Exemple d'appel

  {"name": "submit_correction", "arguments": {"tool": "texte", "field": "price", "proposed_value": "texte"}}

  Exemple de retour

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

• suggest_swaps≈ 119 tokens

  For each tool supplied, return StackSwap's AI-native replacement recommendation (when one exists) with annual savings and reasoning. Skews toward legacy → modern swaps (Outreach → Smartlead, ZoomInfo → Apollo, etc.).

  Paramètres, retour & exemple (1)

  Paramètres

  • tools · array · requis
    Tool names to evaluate for AI-native replacements.

  Exemple d'appel

  {"name": "suggest_swaps", "arguments": {"tools": []}}

  Exemple de retour

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

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://stackswap.ai/api/mcp