"Elastic Stack" matching MCP tools:

• delete_stackA

  Cycle MCPA

  PERMANENTLY delete a stack on Cycle together with ALL of its builds. This is IRREVERSIBLE. Cycle refuses to delete a stack while any container deployed from it exists, so the preview reports such containers as a blocker. Teardown order: delete the containers first (delete_environment removes every container in an environment; delete_container removes one), then the stack. Linked DNS records do not block anything and can be deleted at any point, in parallel. This tool is two-step by design and NOTHING is deleted on the first call: 1. Call without confirm. The stack is resolved and the response inventories what would be destroyed — the stack's name, ID, identifier, and creation date, its builds — and lists any containers deployed from it that block the deletion. Present ALL of those details to the user verbatim. 2. Only after the user explicitly approves deleting that specific stack, call again with confirm:true and stack set to the exact 24-char hex ID from step 1 (names are not accepted with confirm — the ID binds the deletion to what the user approved). Never set confirm:true unless the user has just approved this exact deletion; a general instruction like "clean things up" is not sufficient.

  Connector

  Destructive

  API key

• ip_selfA

  IP.LS — IP Lookup ServiceA

  Get geolocation and network info about the caller's own public IP, plus the protocol stack (IPv4/IPv6) of the current connection. On dual-stack machines the stack is chosen by the client and may differ from `curl ip.ls`, which picks a random stack; use curl -4/-6 locally to get the other stack, or — for clients that cannot pick a stack (browser, PowerShell, most HTTP libraries) — the single-stack hostnames https://4.ip.ls / https://6.ip.ls (DNS selects the stack; an unreachable 6.ip.ls means no usable IPv6). Data comes from a server-side GeoIP lookup on the caller's real IP.

  ConnectorNo auth

• site-intelA

  SuprsonicA

  Get comprehensive domain intelligence: WHOIS, DNS, SSL, tech stack, email security, hosting. Returns, by mode, the registration (WHOIS) data, DNS records with email security, the technology stack, a security grade from A to F, or the subdomains; overview combines registration, DNS, SSL and hosting. Use for technical facts about a domain. For business facts about the company behind it use companies; to find a name you can register use domains. Cost: overview 2 credits, whois 1 credit, dns 1 credit, tech-stack 2 credits, security 2 credits, subdomains 2 credits, charged only when a call succeeds.

  ConnectorNo auth

• devops_watch_stackA

  devops-status-mcp-serverA

  Check the health of a named vendor stack — a saved list of vendors representing your infrastructure dependencies. On the first call, provide vendors to define the stack; subsequent calls can omit vendors to reuse the saved list. Stacks are saved per authenticated caller, or per local server process; a shared deployment that does not authenticate callers saves nothing, so there vendors is required on every call and the response says so. Up to 20 vendors are saved per stack and checked per call; use several stack names for a larger set. Returns a unified health snapshot with an aggregate rollup plus per-vendor detail. A vendor that cannot be resolved or reached is reported in its own row and left out of the saved stack, so one bad entry never discards the sweep. Every vendor with an active problem gets a pre-filled devops_suggest_action call in nextToolSuggestions. Ideal for morning status checks or pre-deploy sweeps. Multiple stacks can coexist (e.g., "production", "staging").

  ConnectorNo auth

• get_listingA

  remoetA

  Works without a Remoet account. Get detailed information about a specific company listing by its slug. Use this to review a company before deciding whether to star it. Returns the company's full description, perks, job count, and URLs. NOTE: the tech stack is a small preview unless the company is starred. Starring unlocks the full stack (techStackCount shows the true total, e.g. a 3-tag preview of 147). Pass checkTechStack with the user's technologies to verify overlap against the FULL stack. Matched ones come back in matchedTechStack and lead the preview, same contract as search_listings. The star budget is reported by get_account.

  ConnectorNo auth

• star_listingA

  remoetA

  Star/save a company listing. Starring subscribes you to their job postings. Starred company jobs appear in get_starred_jobs. Starring also unlocks the company's FULL tech stack (unstarred listings only show a small preview). Starring is FREE. It does not consume budget. However, there is a limit on how many active stars you can have at once. Remaining star slots are reported by get_account. CRITICAL: Only star companies where the user's tech stack genuinely overlaps with the company's tech stack. A React/Node developer should NOT star a company that only uses Go or Java. Irrelevant stars pollute the job feed with noise. Every star must be a deliberate, high-quality match. A company returned by a techStack-filtered search_listings call confirms the technologies in its matchedTechStack field (the filter checks the full stack, including the part hidden from the preview), so judge overlap by matchedTechStack, not the visible preview.

  ConnectorNo auth

• get_listingA

  remoet-mcpA

  Works without a Remoet account. Get detailed information about a specific company listing by its slug. Use this to review a company before deciding whether to star it. Returns the company's full description, perks, job count, and URLs. NOTE: the tech stack is a small preview unless the company is starred. Starring unlocks the full stack (techStackCount shows the true total, e.g. a 3-tag preview of 147). Pass checkTechStack with the user's technologies to verify overlap against the FULL stack. Matched ones come back in matchedTechStack and lead the preview, same contract as search_listings. The star budget is reported by get_account.

  ConnectorOAuth

• star_listingA

  remoet-mcpA

  Star/save a company listing. Starring subscribes you to their job postings. Starred company jobs appear in get_starred_jobs. Starring also unlocks the company's FULL tech stack (unstarred listings only show a small preview). Starring is FREE. It does not consume budget. However, there is a limit on how many active stars you can have at once. Remaining star slots are reported by get_account. CRITICAL: Only star companies where the user's tech stack genuinely overlaps with the company's tech stack. A React/Node developer should NOT star a company that only uses Go or Java. Irrelevant stars pollute the job feed with noise. Every star must be a deliberate, high-quality match. A company returned by a techStack-filtered search_listings call confirms the technologies in its matchedTechStack field (the filter checks the full stack, including the part hidden from the preview), so judge overlap by matchedTechStack, not the visible preview.

  ConnectorOAuth

• suppco_add_to_stackA

  SuppCoA

  Use this when the user wants to start tracking a product in their SuppCo stack. Adds the product to the signed-in user's stack. `id` is a SuppCo product UUID or slug from a search or product result. This does not buy anything; to buy a Buying Club product, use suppco_add_to_cart.

  ConnectorNo auth

• dp_get_stackA

  Default PrivacyA

  Fetch one privacy stack by slug. Most stacks come back whole in this one call. A long stack returns its summary and its layers with the tools in each, in setup order, instead; then pass section (a layer heading) for why each tool and the tradeoffs, or full: true for the whole stack. Slugs come from dp_list_stacks or dp_search.

  ConnectorNo auth

• list_stack_profilesA

  AnkraB

  List reusable stack profiles (versioned stack templates) available to the organisation, including public profiles shared by other organisations, one compact page at a time. Returns: count, matching_count, page, next_page (null on the last page), note, and profiles [{name, category, visibility, latest_version, description abridged to ~90 characters with description_abridged: true when cut}]. Call again with page=next_page until it is null to see every profile; call get_stack_profile(profile_name) for the full description, id, tags, versions and parameters. ALWAYS check this before hand-building a stack with design_stack when the user asks for a 'standard', 'usual', or previously saved setup - instantiating an existing profile is preferred over rebuilding from charts.

  ConnectorOAuth

• update_application_demo_configA

  AnkraB

  Replace an Application's saved demo env entries and throwaway-database flag wholesale (the demo pre-setup every future launch inherits). Read the current configuration first and carry existing env entries forward - entries not in this call are dropped. The full-stack stack profile and shared base stack designations are NOT settable here and are preserved untouched: a demo whose database comes from a stack must not have the throwaway Postgres wired over it. Values may reference ${{ ankra.demo_database.* }} placeholders (requires database=true) and ${SECRET_SLOT:<uuid>} sentinels (kept secret, mounted via a Kubernetes Secret). Affects only demo deployments in TTL-reaped namespaces, never production workloads; running demos pick the change up on their next redeploy_demo.

  ConnectorOAuth

• validate_stackA

  AnkraB

  Validate a stack specification against the cluster without creating or deploying anything: replays the same validation the create lane runs (duplicate stack name, member shape, chart and dependency checks) and reports the errors. The stack object uses the same shape as create_stack, including the parents dependency edges. Returns {valid, errors}, plus a dependency_review whenever a multi-member specification declares no parents at all - those members would deploy in parallel and race each other. Use this before create_stack, and add the missing parents before deploying. Read-only.

  ConnectorOAuth

• delete_stackA

  spacesheepA

  Delete a stack. Its pages are not deleted: each page it was home to is unfiled, and the agent files it into the person's other stacks on its next pass (and won't start a stack like it again). To keep the pages together under another stack instead, use merge_stacks. Only when the person asks.

  Connector

  Destructive

  OAuth

• briq_upA

  briqA

  Bring up the stack a repo declares in its stack file, briq.yaml. Pass `file`: the file's content as you read it from the repo. Creates each service the stack does not have yet, as briq_run makes it and under the same checks: every new one, or none. Leaves the services it has as they are and never deletes, so calling it again is safe. A service is what briq_run takes: `recipe` with the fields it changes (image, env, cmd, size, volume, files; checkout and steps for a language recipe), or `image` with its settings. A secret the file names as { secret: NAME } is generated, unless its value is passed here: secrets: { STRIPE_KEY: "…" }; ask the person for one briq cannot generate, never invent it. Returns each briq and the outputs (connection strings, <briq>:URL for each published service). With `expose: true`, the outputs reach the stack from outside briq (a laptop): each database gets a TLS endpoint. The format: briq_docs "stack-file".

  ConnectorOAuth

• stacks.findSimilarA

  BuyAPIA

  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.

  ConnectorNo auth

• get_profileA

  HireMe MCPA

  Who Djaouad Frih is: full-stack AI engineer, stack, live products, availability and contact links. Call this first.

  ConnectorNo auth

• recommend_stackA

  StackSwapA

  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).

  ConnectorNo auth

• export_stack_profile_iacA

  AnkraB

  Export one published version of a stack profile as a ClusterInfrastructureAsCode YAML document (the twin of `ankra stack-profiles export-iac`), with the parameters it declares. Use this to read a profile's full definition, to copy it into another organisation with import_stack_profile, or to keep it in Git. Read-only.

  ConnectorOAuth

• create_stackA

  spacesheepA

  Make a new stack and file pages into it in the same call: as each page's one home (it leaves the stack it was in), or with also: true as an extra stack it shows in too. A name the person already has is that stack, not a second one. A stack nothing is filed in is cleared by the nightly tidy, so give it pages. Up to 40 stacks. Only when the person asks; list_stacks shows the stacks and shelves they have.

  ConnectorOAuth

• search_kevA

  Distributed RiskA

  CISA's Known Exploited Vulnerabilities catalog, newest first: CVE, vendor, product, date added, federal due date, known ransomware use, the required action, FIRST's EPSS estimate, and whether it sits in the AI and agent software stack. Look up one CVE, search vendor or product words, list what was added since a date, or only the AI stack. For one CVE in full, use get_cve.

  ConnectorNo auth