Squish
Server Details
Manage your Squish domains, DNS, hosting, backups and site files from your AI assistant.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 58 tools
Most tools target a distinct resource+action, and descriptions actively cross-reference near-neighbors (check_uptime vs get_my_site_health, lookup_dns vs get_dns_records, detect_web_host vs lookup_ip_hosting vs detect_technology). A few pairs still require careful reading — check_ai_visibility vs run_my_ai_visibility_report and check_ai_visibility vs plan_ai_visibility_fixes — but each has an explicit routing rule that resolves the overlap.
Names are overwhelmingly snake_case verb_noun with a meaningful prefix convention (get_my_/list_my_ for the customer's own resources vs lookup_/check_/detect_ for public lookups). Minor deviations exist: get_migration_status vs advance_email_migration vs list_my_migrations mix 'migration' and 'email_migration', and setup_domain_forwarding vs set_my_cdn differ in verb style.
58 tools is very heavy for a single connection, well past the 25-tool threshold for 'too many'. The platform is genuinely broad (hosting, domains, DNS, email, AI Visibility, diagnostics, support, account), so each tool is defensible, but the granular read-only diagnostics cluster could be consolidated and the surface is burdensome to navigate.
Coverage is strong across every advertised area: full DNS CRUD plus forwarding and autorenew, domain search/purchase/transfer, site files and backups, CDN control, email migration lifecycle, AI Visibility plan/apply/track, support case lifecycle, and account updates. Gaps are mostly intentional handoffs to the dashboard (starting purchases, confirming migrations, creating new tickets), which are workable but leave a couple of dead ends.
Available Tools
58 toolsadd_ai_visibility_coverageAdd ai visibility coverageAInspect
Adds one more domain to a customer's AI Visibility plan (up to 3 extra). The domain must be provably theirs: on this account's registrar portfolio, or pointing at their own server. Two-step: (1) confirm:false previews (slot free? already covered?) and names the domain; read it to the customer and get an explicit yes. (2) ONLY after an explicit yes, call with confirm:true: the proof is checked, the slot is taken and a first scan is run. Refused with UNVERIFIED and a reason when the domain cannot be confirmed as theirs; relay that reason, it says what to do.
Inputs: domain (required), coveredDomain (required), confirm.
add_case_noteAdd case noteAInspect
Add a note / reply from the customer to one of their OWN support tickets (Salesforce Cases) — the note lands on the case as a public comment the support team can see. Use when the user wants to add information, reply, or follow up on an existing ticket ("add a note to my ticket", "tell them I also tried X", "update my case"). Two-step usage REQUIRED: (1) call with confirm:false to look up the ticket and read the exact note text back to the user for review; (2) ONLY after the user confirms, call with confirm:true to post it. Notes cannot be edited or removed once posted, so always confirm the wording first. Pass the ticket number exactly as shown by list_my_cases (e.g. "00001040").
Inputs: note (required), ticketNumber (required), confirm.
advance_email_migrationAdvance email migrationAInspect
Drive a migration to its next stage. Use after the customer has done their part on a polled stage — e.g. they just clicked the Microsoft consent URL and we need to re-check whether admin access has been granted, or a stage previously failed and they want to retry. Idempotent — safe to call multiple times. Returns the new state (or NOT_READY if the upstream signal hasn't arrived yet — that's normal, tell the user to wait a bit). Confirm-first is NOT required here because this tool doesn't cross a "money moves" boundary on its own — order placement happens at Confirm email migration (in the Squish dashboard), not here.
Inputs: migrationId (required).
apply_ai_visibility_fixesApply ai visibility fixesADestructiveInspect
Applies AI Visibility fixes to one of the customer's OWN hosted WordPress sites — adds business structured data (schema), a meta description, and an FAQ page. Two-step usage: (1) call with confirm:false to PREVIEW — returns exactly which fixes would be applied and anything still needing the customer's business details; describe that and ask them to confirm. (2) ONLY after the user clearly says yes, call again with confirm:true to apply. Never pass confirm:true without an explicit yes in the user's most recent message. The domain must be one of the user's own Squish-hosted WordPress sites. Every change is made behind a pre-edit restore point and a bad apply is rolled back automatically — nothing is left half-applied. HONESTY: this makes the site readable and understood by AI; it never promises an engine will recommend or cite the business.
Inputs: domain (required), confirm.
check_ai_visibilityCheck ai visibilityARead-onlyIdempotentInspect
Check how legible and citable a business website is to AI answer engines (ChatGPT, Perplexity, Google AI answers) and get an A-F grade with plain-English findings. Checks whether an AI crawler can read the site at all (the JS/SPA-render problem), whether it has business structured data (schema), whether it has Q&A-style content, and whether answer-engine crawlers are allowed. Returns { domain, grade, score, headline, summary, readability, structure, legibility, posture, findings, remediation }. Call this when someone asks whether AI/ChatGPT can find or read their business, about "AI SEO" / answer-engine optimization, or wants their AI visibility graded. HONESTY: this measures whether AI can SEE and UNDERSTAND the business — never promise an engine will recommend or cite them; that is influence, not a guarantee. Works on any public website — no login required.
Inputs: domain (required).
check_blacklistCheck blacklistARead-onlyIdempotentInspect
Check whether a domain or its IP address appears on major spam and malware blacklists (Spamhaus ZEN, SORBS, SpamCop, Barracuda, Spamhaus DBL, URIBL, SURBL). Returns { domain, ip, blacklisted, listedOn[], cleanOn[], checkedLists, note? }. When the domain has no A record, ip is null and only the domain-based lists are checked (note explains the partial result). Call this when someone asks about email deliverability problems, whether their domain is blacklisted, why their emails land in spam, or if their IP has a bad reputation. No login required.
Inputs: domain (required).
check_email_authCheck email authARead-onlyIdempotentInspect
Check a domain's email authentication posture — SPF, DKIM, and DMARC — and get an A-F grade with plain-English findings. Returns { domain, grade, provider, spf, dkim, dmarc, findings, migration }. Call this when a customer asks about email deliverability, DMARC policy, SPF records, DKIM setup, or why their email is landing in spam. Works on any public domain — no login required.
Inputs: domain (required).
check_security_headersCheck security headersARead-onlyIdempotentInspect
Check a website's HTTP security headers and get an A-F grade. Tests for HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. Returns { domain, grade, score, checks[], server }. Call this when someone asks about website security, why their site got a bad security score, how to improve their security headers, or what headers they're missing. No login required.
Inputs: domain (required).
check_sslCheck sslARead-onlyIdempotentInspect
Check the SSL/TLS certificate for a domain. Returns validity, issuer, subject, expiry date, days remaining, SANs, and TLS protocol version. Call this when a customer asks about HTTPS, SSL errors, certificate warnings, or when a certificate is expiring. Works on any public domain — no login required. For a site hosted on Squish, call the certificate "free SSL that renews automatically" and do not volunteer the name of the issuer; if the customer asks who issued it, answer truthfully from issuer.
Inputs: domain (required).
check_uptimeCheck uptimeARead-onlyIdempotentInspect
Check whether a website is up and reachable right now. Tests both HTTPS and HTTP, reports HTTP status code, response time in milliseconds, and whether the server redirects. Returns { domain, online, primaryStatus, https, http }. Call this when someone asks "is my site down?", "why is my website not loading?", or any question about site availability. No login required.
Inputs: domain (required).
close_my_caseClose my caseAInspect
Close one of the customer's OWN support tickets (Salesforce Cases) when they say the issue is resolved. Two-step usage REQUIRED: (1) call with confirm:false to look up the ticket and preview which one will be closed — read the ticket number and subject back to the user; (2) ONLY after the user explicitly says yes, call with confirm:true to close it. Pass the ticket number exactly as shown by list_my_cases (e.g. "00001040"). Staff can reopen a closed ticket if needed, but never close a ticket the user hasn't clearly said is resolved.
Inputs: ticketNumber (required), confirm.
create_dns_recordCreate dns recordAInspect
Create a new DNS record on a domain the customer owns. Two-step usage: (1) call with confirm:false to preview the new record and describe it to the user, then (2) ONLY after the user explicitly says yes, call again with confirm:true. NEVER call confirm:true without explicit user confirmation.
Inputs: type (required), value (required), domain (required), ttl, +2 more.
delete_dns_recordDelete dns recordADestructiveInspect
Delete a DNS record on a domain the customer owns. Two-step usage REQUIRED: (1) call with confirm:false to fetch the record being deleted and describe EXACTLY what will be removed (record type, host, value) — deletion is irreversible and the user must understand what they're losing. (2) ONLY after the user explicitly says yes, call again with confirm:true.
Inputs: domain (required), recordId (required), confirm.
detect_email_providerDetect email providerARead-onlyIdempotentInspect
Inspect a customer's email domain via Microsoft's public getuserrealm.srf endpoint to figure out whether their Microsoft 365 is bought direct from Microsoft or resold through GoDaddy. Use this IMMEDIATELY after the customer gives you their email domain in a migration conversation, BEFORE asking "is it Microsoft Direct or GoDaddy?" — the answer should come from this tool, not from the customer.
Returns { likelyProvider: "microsoft-direct" | "godaddy", confidence: "high" | "medium" | "low", ... }. Pass likelyProvider straight to Start email migration (in the Squish dashboard) as the source argument. You do NOT need to mention the detection step to the customer — just proceed.
The source field only affects post-migration UX (which URL we point the customer to for cancelling their old subscription), so a wrong guess is easily corrected mid-flow. NEVER respond to a "you tell me?" question with "I can't tell" — call this tool instead.
Idempotent + side-effect-free (just an outbound HTTP GET to login.microsoftonline.com); safe to call multiple times.
Inputs: domain (required).
detect_technologyDetect technologyARead-onlyIdempotentInspect
Detect the technologies powering a website — CMS (WordPress, Shopify, Drupal, etc.), CDN (Cloudflare, Fastly, CloudFront, etc.), web server, frontend framework (Next.js, Gatsby, Nuxt, etc.), and analytics platforms. Returns { domain, cms, cdn, server, framework, metaGenerator, analytics[] }. Call this when someone asks what platform a site runs on, what CMS a competitor uses, what CDN a site is behind, or what stack powers a website. No login required.
Inputs: domain (required).
detect_web_hostDetect web hostARead-onlyIdempotentInspect
Find out WHO HOSTS a website — the hosting company behind a domain, plus the CDN in front of it, the DNS provider, and the email provider. Returns { domain, host: { name, kind, confidence, evidence[] }, originHidden, proxy, ip, dns, email, platform, migration }. host.kind is one of platform | managed-wordpress | shared | cloud | edge | squish. IMPORTANT: when originHidden is true the site sits behind a CDN (usually Cloudflare) and the real host could NOT be identified — say so plainly instead of naming the CDN as the host. Call this when someone asks who hosts a site, who a competitor hosts with, where a site they inherited is running, or what they would be migrating away from. For the CMS/stack running on top, use detect_technology instead. No login required.
Inputs: domain (required).
diagnose_my_serverDiagnose my serverARead-onlyIdempotentInspect
Diagnoses performance on the customer's own VPS from the server's telemetry — CPU load relative to their plan's vCPU count, memory pressure, and disk fullness — and explains in plain language what is wrong. Use for "why is my site slow?", "is my server struggling?", "do I need a bigger plan?", "is my disk full?".
This is server-side and VPS-only. For shared hosting it returns not_applicable — say so rather than guessing. For whether a site is REACHABLE use check_uptime; for uptime HISTORY use get_my_site_health.
IMPORTANT: lead with summary, then the individual findings detail lines. If agentReporting is false, the server is NOT confirmed healthy — we simply cannot see it; say that plainly. Only raise upgrading when upgradeSuggested is true; when it is false and the box is healthy, say the bottleneck is above the server (application, plugins, queries) rather than selling a bigger plan.
Inputs: domain.
get_account_infoGet account infoARead-onlyIdempotentInspect
Returns the customer's profile on file — name, email, phone, billing address, company, and account number. Use when the user asks "what's my address on file?", "what's my account number?", or wants to verify what we have. Read-only.
Inputs: no named parameters.
get_dns_recordsGet dns recordsARead-onlyIdempotentInspect
Returns the DNS records currently set on a domain the customer owns (A, AAAA, CNAME, MX, TXT, NS, etc.) — same data as the registrar's DNS panel. Use when the user asks "what's my A record on x.com?", "show me my MX records", "what does my DNS look like?". Pre-checks that the domain is on the customer's account; returns a clear error if not. Read-only.
Inputs: domain (required).
get_hosting_upgrade_optionsGet hosting upgrade optionsARead-onlyIdempotentInspect
Which higher plan tiers one of the customer's hosting sites can move up to, with each tier's monthly sticker and whether it is eligible (and why not). The exact amount due today (prorated against what they already paid) is shown in the dashboard before they confirm; the upgrade charges the card on file, so it is confirmed THERE, never by a tool. Use when they ask "can I get a bigger server?", "what would it cost to upgrade?". Read-only.
Inputs: domain (required).
get_migration_statusGet migration statusARead-onlyIdempotentInspect
Get the full state of a single email migration: current stage, the tenant ID we discovered, the SKU mapping the orchestrator proposed (sourceSkus / targetSkus), the scheduled cutoverAt if any, the consent URL the customer needs to click (when in CONSENT_PENDING), and any failure info. Use when the user asks "how is my migration going?", "what stage am I in?", "give me the consent link", or before driving the next stage. Read-only.
Inputs: migrationId (required).
get_my_ai_visibility_coverageGet my ai visibility coverageARead-onlyIdempotentInspect
Which domains a customer's AI Visibility plan watches: the plan's own site plus the extra domains they have added, each with how it was verified and its latest grade (null grade = not scanned yet, say "pending", never "passing"). Also how many of the slots are used. Refused when AI Visibility is not on the plan. Read-only.
Inputs: domain (required).
get_my_cdn_statsGet my cdn statsARead-onlyIdempotentInspect
Returns whether the CDN (edge cache) is on for one of the customer's hosting sites and, for a Managed Cloud server, the last 30 days of edge traffic across the sites on that server: requests, bandwidth, cache hit rate. On shared hosting the edge zone is shared with other customers, so per-site traffic figures do not exist: the answer is on/off only (stats: null, perSite: false). Use for "is my CDN on?", "how much traffic is my site getting?", "is the cache working?". Read-only.
Inputs: domain (required).
get_my_domain_transfersGet my domain transfersARead-onlyIdempotentInspect
Where the customer's inbound domain transfers stand, one row per domain, with counts: awaiting_code (paid, the customer still has to enter the transfer code in their dashboard — or, for a .uk domain (method ips_tag), confirm there that the current registrar changed the IPS tag to NAMESILO), queued (code in, being submitted), refused (the registrar rejected it — the reason says what to fix before entering the code again), needs_attention (we are checking it with the registrar), pending_registry (submitted, usually done in about 5 days), completed, cancelled. Pass cartId to see one checkout's batch. Use after prepare_domain_transfers, or when they ask "did my transfers go through?". Codes are entered in the dashboard, never here. Read-only.
Inputs: cartId.
get_my_site_healthGet my site healthARead-onlyIdempotentInspect
Returns MEASURED uptime history for the customer's own hosted sites — how the site has BEEN over a trailing window, from our SLA monitoring record. Use for "how has my site been?", "has my site gone down?", "what's my uptime?", "did you have an outage last week?". This is different from check_uptime, which probes a URL live right now — use that for "is my site up?" and this for anything historical. Optionally scope to one domain (which also returns the recent outage list for it). Read-only.
IMPORTANT: each site carries a disclosure sentence — lead with it rather than quoting a bare percentage. When measurementHealthy is false, relay measurementNote: our monitoring was behind, so the numbers are provisional and you must say so. When coverage is "none", do NOT invent or estimate a figure — say it is not measured yet.
Inputs: days, domain.
get_my_site_runtimeGet my site runtimeARead-onlyIdempotentInspect
Returns what one of the customer's SHARED hosting sites actually runs, read from the server: the PHP version the site uses down to the patch level (e.g. 8.4.27), its handler (FPM / FastCGI), when that PHP build was last updated on the server, every PHP build installed, and the control panel and OS. CALL THIS for "what PHP version am I on", "am I patched for ", "is my server up to date": compare the exact version with the fixed release and say so; the updatedAt date is when Squish applied the build. Squish patches shared servers; the customer does not install PHP updates themselves. A Managed Cloud server is not covered here. Read-only.
Inputs: domain (required).
get_public_pricingGet public pricingARead-onlyIdempotentInspect
Fetch the live public Squish pricing catalogs. Sections: hosting (all hosting tiers + self-serve flags), email (Microsoft 365 tiers, monthly vs annual), domains (first-year floor AND renewal prices for the headline endings only), billing_terms (multi-year term rates + the self-serve checkout ceiling), addons (email add-ons), hosting_addons (hosting add-ons). CALL THIS whenever you are about to state an exact price, renewal, spec, or term rate that you cannot see in the Squish Services block — never quote catalog numbers from memory. For any OTHER domain ending (.house, .xyz, .shop, .co.uk and hundreds more), pass tld and the result carries that ending's live first-year, renewal AND transfer-in price. No login required.
Inputs: tld, section.
get_site_import_statusGet site import statusARead-onlyIdempotentInspect
Where a "Move a site here" import stands for one of the customer's hosting sites: whether an import can start, the current run (kind, phase, progress) or the preview waiting to go live, and whether a WordPress connection exists. Use when they ask "is my site move done?", "what is happening with my import?". Starting, going live with or discarding an import is done in the dashboard (Hosting → the site → Move a site here). Read-only.
Inputs: domain (required).
list_capabilitiesList capabilitiesARead-onlyIdempotentInspect
Lists everything a Squish connection or the Squish assistant can do, grouped by area (account, domains, DNS, purchases, hosting, AI Visibility, email, diagnostics, catalogs), with each tool's name, a one-line summary, whether it reads or writes, the key scope it needs, and whether it is available to THIS session. CALL THIS when the user asks what you can do, what the connection can do, what a read-write key adds, or whether something is possible over MCP. Relay the areas in plain words; name the tool only when they ask. No login required.
Inputs: no named parameters.
list_my_backupsList my backupsARead-onlyIdempotentInspect
Lists the restore points held for one of the customer's SHARED hosting sites, newest first: the nightly backups of the whole site (source "nightly") and the edit points (source "edit") — the previous version of each file an assistant replaced with write_site_files, listed with the files it holds. Restoring a nightly point merges the whole site back; restoring an edit point puts back ONLY those files. For "undo that last change" pick the newest edit point; for "my site was fine yesterday" pick a nightly one. Use for "what backups do I have?", "can I roll my site back?", and ALWAYS before restore_my_site_backup so the backupId is a real one. A VPS is not covered here (its snapshots live in its own panel). Read-only.
Inputs: domain (required).
list_my_casesList my casesARead-onlyIdempotentInspect
Returns the customer's support tickets (Salesforce Cases) — ticket number, subject, status, priority, and when it was opened. Use whenever the user asks about a support ticket or case: "check on my open support ticket", "what's the status of my ticket?", "did my case get resolved?", "do I have any open tickets?". Cases are ordered newest-first; set openOnly:true to return only tickets that are still open (not Closed). Read-only.
Inputs: limit, openOnly.
list_my_domainsList my domainsARead-onlyIdempotentInspect
Returns the list of domains the customer owns through Squish, with status, expiry, auto-renew, order number, and purchase date. Use when the user asks "what domains do I have?", "which domains am I paying for?", or similar. Read-only.
Inputs: no named parameters.
list_my_hostingList my hostingARead-onlyIdempotentInspect
Returns the list of hosting sites the customer has provisioned, with the control panel (Plesk or CyberPanel) and its URL, setup type (general / WordPress / AI Quick Start), and Plesk login. panelUrl is null when the server has no panel. Use when the user asks "what sites do I have?", "where do I log in to my hosting?", "what's my hosting panel URL?". Read-only.
Inputs: no named parameters.
list_my_migrationsList my migrationsARead-onlyIdempotentInspect
List the customer's email migrations across all states (in-progress, scheduled, complete, cancelled). Use when the user asks "what migrations do I have?", "is my migration done?", "what's the status of my email move?", or to find the migrationId to pass to get_migration_status. Read-only; starting, confirming or cancelling a migration happens in the Squish dashboard.
Inputs: limit.
list_my_recent_ordersList my recent ordersARead-onlyIdempotentInspect
Returns recent orders on the customer's account, with order number, total, status, effective date, and what has been refunded. Use when the user asks "what did I buy recently?", "show me my last order", "what was my last invoice for?", "was I refunded?". Each order carries total (what was charged), refunded (what has since gone back to the customer, 0 when nothing has), and net (total minus refunded). An order's status stays "Activated" after a refund, so read refunded, not status, to answer whether money went back. Read-only.
Inputs: limit.
list_site_filesList site filesARead-onlyIdempotentInspect
Lists one folder of a customer's SHARED hosting site's web root (the files the site serves): name, type (file / dir / symlink), size. Start at the root (no path) and go down one folder at a time. Use before read_site_file / write_site_files so paths are real. Hidden files and anything outside the web root are never shown. Read-only.
Inputs: domain (required), path.
lookup_dnsLookup dnsARead-onlyIdempotentInspect
Look up DNS records for any domain — A, AAAA, MX, TXT, NS, and CNAME. Returns { domain, records: { A, AAAA, MX, TXT, NS, CNAME } }. Call this when a customer asks about DNS configuration, nameservers, mail routing, or wants to verify a specific record on any domain (not just domains they own). No login required.
Inputs: domain (required).
lookup_ip_hostingLookup ip hostingARead-onlyIdempotentInspect
Look up the IP address(es) for a domain and identify which network announces them — ASN, AS name, BGP prefix, registry, and the registry country for the allocation. Returns { domain, ipv4[], ipv6[], primaryIp, hosting: { asn, asName, prefix, countryCode, registry } }. Call this when someone asks what IP a domain resolves to or which network owns that IP. asName is a registry handle with the operator appended ("CLOUDFLARENET - Cloudflare, Inc., US"), and countryCode is where the block was allocated, NOT where the server is — this is BGP data, not geolocation, and there is no city. IMPORTANT: the network announcing an IP is not the web host — for a site behind a CDN it IS the CDN (godaddy.com announces from Cloudflare). For "who hosts this site?" use detect_web_host instead. No login required.
Inputs: domain (required).
lookup_whoisLookup whoisARead-onlyIdempotentInspect
Look up WHOIS / RDAP registration info for any domain. Returns registrar, registration date, expiry date, nameservers, and status codes. Note: registrant contact details are privacy-redacted by registries (post-GDPR). Call this when a customer asks who owns a domain, when it expires, what registrar it's on, or whether it's available. No login required.
Inputs: domain (required).
plan_ai_visibility_fixesPlan ai visibility fixesARead-onlyIdempotentInspect
For a website, scan it AND return a reviewable PLAN of proposed fixes to make it more legible to AI answer engines — generated business structured data (schema), a meta description, FAQ/Q&A drafts, and flags for the render and crawler-posture fixes. Returns { domain, grade, reviewRequired, proposals: [{ id, type, title, rationale, autoApplicable, needsInput, artifact }], summary }. Call this after check_ai_visibility when someone asks "how do I fix it?" or "what would you change?". IMPORTANT: this only PROPOSES — nothing is applied to any live site here. Every change is reviewed and approved first. HONESTY: the render/JS fix is a hosting change, not something the AI writes; and never promise an engine will recommend or cite the business. Works on any public website — no login required. When mentionByEngine is present, report each engine separately, say the numbers come from each engine's API, and never present mentionRate as one combined figure when enginesUnmeasured is not empty.
Inputs: domain (required).
prepare_domain_purchasePrepare domain purchaseAInspect
Prepares the purchase of an AVAILABLE domain for this customer and returns a checkout link: the domain is priced and placed in a cart on their Squish account, and the link opens the normal checkout where the customer (or whoever they send the link to) pays with their card. No money moves when this tool runs. Two-step: (1) call with confirm:false — the preview is the quote: whether the name is available, the first-year price, the renewal price, the term. Relay it and ask for an explicit yes. (2) ONLY after an explicit yes in their most recent message, call with confirm:true to create the cart and get the link; the link is valid for 30 days and the cart also appears in their dashboard. Use when the customer asks to buy or register a domain through an outside assistant, or wants a payment link for a domain. For a name that is taken, use search_domains to find alternatives instead.
Inputs: domain (required), years, confirm.
prepare_domain_transfersPrepare domain transfersAInspect
Prepares moving one or more domains the customer already owns at ANOTHER registrar to Squish, and returns ONE checkout link for all of them: each eligible domain is priced and placed in a single cart on their account; the link opens the normal checkout. No money moves when this tool runs and no auth codes are needed here: after paying, the customer enters each transfer (EPP/auth) code from the Domains card in their dashboard, so NEVER ask for a code in the conversation. A .uk domain (.co.uk, .org.uk, .uk …) has NO code at all: the current registrar changes its IPS tag to NAMESILO and the customer confirms that from the same Domains card. conversation and never pass one to this tool. Two-step: (1) confirm:false previews, PER DOMAIN, whether it can move (and if not, why: already at Squish, not registered anywhere — use prepare_domain_purchase —, locked, too recently registered, restricted or premium ending) and the transfer price, plus the total and the three things they do at the current registrar; relay the ineligible list and ask for an explicit yes. (2) ONLY after an explicit yes in their most recent message, call with confirm:true for the link; the cart holds the eligible domains only. Up to 50 domains per call; split a longer list. Use get_my_domain_transfers afterwards to report where each transfer stands.
Inputs: domains (required), confirm.
purge_my_cdn_cachePurge my cdn cacheAInspect
Clears the CDN edge cache for one of the customer's hosting sites so visitors get the latest files right away. Use after they changed their site and still see the old version. Two-step: (1) call with confirm:false for the preview, ask for a yes; (2) ONLY after an explicit yes in their most recent message, call with confirm:true. Harmless to the site (the next visit refills the cache), scoped to this domain only.
Inputs: domain (required), confirm.
read_site_fileRead site fileARead-onlyIdempotentInspect
Returns the text of one file in a customer's SHARED hosting site's web root (HTML, CSS, JS, JSON, text…), up to 512 KB. ALWAYS read a file before changing it with write_site_files, and change only what the customer asked for. Binary files (images, fonts) are described, not returned. Read-only.
Inputs: path (required), domain (required).
remove_ai_visibility_coverageRemove ai visibility coverageADestructiveInspect
Removes a domain from a customer's AI Visibility coverage, freeing its slot. The plan's own site can never be removed. Its scan history for that domain is dropped. Two-step: confirm:false previews, confirm:true removes ONLY after an explicit yes.
Inputs: domain (required), coveredDomain (required), confirm.
reopen_my_caseReopen my caseAInspect
Reopen one of the customer's OWN support tickets (Salesforce Cases) that was closed — use when a previously-resolved issue has come back or was never actually fixed. Two-step usage REQUIRED: (1) call with confirm:false to look up the ticket and preview which one will be reopened — read the ticket number and subject back; (2) ONLY after the user confirms, call with confirm:true to reopen it. Puts the ticket back in the support queue (Status → New). If the ticket is already open, this is a no-op. Pass the ticket number exactly as shown by list_my_cases.
Inputs: ticketNumber (required), confirm.
restore_my_site_backupRestore my site backupADestructiveInspect
Restores one of the customer's SHARED hosting sites from a restore point. DESTRUCTIVE. A nightly point is merged over the whole live site, so changes made since it was taken are lost (files added since may survive). An edit point (backupId "edit_…") puts back ONLY the files that write replaced, after setting their current versions aside as a new edit point, so it can itself be undone. Two-step: (1) call with confirm:false — the preview names the restore point and says exactly what will change; read it to the customer and ask for an explicit yes. (2) ONLY after an explicit yes in their most recent message, call with confirm:true. Get backupId from list_my_backups; never guess one.
Inputs: domain (required), backupId (required), confirm.
run_my_ai_visibility_reportRun my ai visibility reportAInspect
Runs an AI Visibility report on one of the customer's OWN Squish-hosted sites and SAVES it to their history, so the grade can be tracked over time (the CRM shows it move). Use this — not check_ai_visibility — when a signed-in customer asks to check or re-check THEIR OWN site, or after applying fixes to record the new grade. The domain must be one of the customer's own hosted sites. Returns the same graded result as check_ai_visibility ({ grade, score, findings, ... }), and the result is recorded against their account. Read-only to the site (it just scans).
Inputs: domain (required).
scan_portsScan portsARead-onlyIdempotentInspect
Scan common TCP ports on a domain to see which services are publicly accessible. Checks 16 ports: FTP(21), SSH(22), SMTP(25), HTTP(80), POP3(110), IMAP(143), HTTPS(443), SMTPS(465), SMTP-submission(587), IMAPS(993), POP3S(995), MySQL(3306), RDP(3389), PostgreSQL(5432), HTTP-alt(8080), HTTPS-alt(8443). Returns { domain, ip, openPorts[], closedPorts[] }. Call this when someone asks what services are running on a server, whether a specific port is open, or to check firewall exposure. Requires the customer to be signed in.
Inputs: domain (required).
search_domainsSearch domainsARead-onlyIdempotentInspect
Search domain-name availability and pricing. Checks the requested name across common endings (.com/.net/.org/.io/.co/.ai/.app/.dev plus .xyz/.shop/.store/.tech/.online/.site) and a few brandable variations, then returns which are available, their yearly price, and which are taken. CALL THIS whenever the user wants to find, check, buy, or register a domain, or asks if a domain is available. IMPORTANT routing rules: (1) If the user names a specific extension (e.g. "is acme.xyz free?", "I want testsquish1.xyz"), pass the FULL domain including that extension as query — never strip or substitute the TLD they asked for. (2) If the user corrects or refines a previous search to a different extension ("no, I meant .xyz", "what about .io?"), call again with the SAME base name and the NEW extension (e.g. query:"acme.io"). (3) Do NOT call this tool when the user is merely reacting to results without naming a new name or extension ("any other ideas?", "hmm, none of those") — answer from the results you already have instead of re-searching. No login required.
Inputs: query (required).
set_my_cdnSet my cdnAInspect
Turns the CDN (edge cache in front of the site) on or off for one of the customer's hosting sites. This rewrites the domain's DNS on Squish nameservers, so it takes a few minutes to settle and is refused for a domain whose DNS is managed at another registrar. Two-step: (1) confirm:false previews the change; (2) ONLY after an explicit yes in their most recent message, call with confirm:true. The result says what HAPPENED (cdnEnabled), which can differ from what was asked — relay the note when there is one.
Inputs: domain (required), enabled (required), confirm.
setup_domain_forwardingSetup domain forwardingADestructiveInspect
Configure URL forwarding so visits to the domain (and its www) redirect to a target URL. Useful for "point foo.com at my main site" requests. Redirects are served from our edge network, which means the domain has to be delegated to Squish nameservers. Two-step usage REQUIRED: (1) call with confirm:false to preview, describe to user; (2) ONLY after explicit yes, call with confirm:true. If the preview comes back with nameserverChangeRequired:true you MUST relay that the domain's nameservers would move to us and that DNS records at its current DNS host — email/MX included — stop working until they are recreated here — and that this particular change cannot be made from chat: direct the customer to the dashboard's DNS settings for that domain, where they review and confirm the nameserver move themselves. A domain that receives email should be moved with a DNS migration instead. All forwarding is a standard (302) redirect — cloaked/framed forwarding is not offered; if asked, say so rather than promising it.
Inputs: domain (required), target (required), confirm, acknowledgeNameserverChange.
toggle_autorenewToggle autorenewAInspect
Turn auto-renew on or off for a domain the customer owns. Two-step usage: (1) call with confirm:false to fetch the current state and preview the change. If turning OFF, make sure the user understands the domain will expire if they don't renew manually. (2) ONLY after explicit user yes, call with confirm:true.
Inputs: domain (required), enabled (required), confirm.
trace_redirectsTrace redirectsARead-onlyIdempotentInspect
Trace the full HTTP redirect chain for a domain — follows every hop (up to 15) and reports each URL and status code. Returns { domain, hops, chain[], finalUrl, finalStatusCode, httpChain[], httpUpgrade, hasRedirectLoop }. chain starts at https:// (what a modern browser does); httpChain starts at http:// and is what httpUpgrade describes: "upgrades" (plaintext reaches HTTPS), "serves-plaintext" (answers on http and stays there), or "unmeasured" (port 80 never answered — NOT the same as no upgrade, and must not be reported as one). Call this when someone asks about redirect chains, why their site redirects, SEO redirect issues, mixed-content redirects, whether their site forces HTTPS, or what URL a domain ultimately lands on. No login required.
Inputs: domain (required).
update_account_addressUpdate account addressADestructiveInspect
Update the customer's billing address on file (Stripe + Salesforce). Two-step usage REQUIRED: (1) call with confirm:false to fetch the current address and preview the new one — describe both to the user in plain English; (2) ONLY after the user explicitly says yes, call with confirm:true to apply. NEVER call confirm:true without an explicit affirmative in the user's most recent message. If only some address fields are provided, the unspecified ones will be replaced with empty/null — make sure the user understands they're replacing the whole address, not patching it.
Inputs: city (required), line1 (required), line2, state, +3 more.
update_account_phoneUpdate account phoneADestructiveInspect
Update the phone number on the customer's account (Stripe + Salesforce). Two-step usage: (1) call with confirm:false to fetch the current phone and preview the change; (2) ONLY after the user says yes, call with confirm:true. NEVER call confirm:true without an explicit affirmative in the user's most recent message.
Inputs: phone (required), confirm.
update_dns_recordUpdate dns recordADestructiveInspect
Update an existing DNS record on a domain the customer owns. Two-step usage: (1) call with confirm:false to fetch the current record + preview the change and describe both to the user in plain English, then (2) ONLY after the user explicitly says yes, call again with confirm:true to apply. NEVER call confirm:true without an explicit affirmative in the user's most recent message. You typically need to call get_dns_records first to find the recordId.
Inputs: value (required), domain (required), recordId (required), ttl, +2 more.
write_site_filesWrite site filesADestructiveInspect
Writes (creates or replaces) up to 25 web files in a customer's SHARED hosting site's web root and publishes them immediately — this is how an assistant puts an edit on the live site. Full file contents only (no patches): read_site_file first, apply the customer's change, send the whole file back. Web file types only (HTML, CSS, JS, JSON, text, SVG, images, fonts); never PHP, .htaccess or hidden files. The previous version of every replaced file is kept in a restore point outside the served tree. Two-step: (1) confirm:false previews the paths and sizes and says which site; read it to the customer and get an explicit yes. (2) ONLY after an explicit yes in their most recent message, call with confirm:true. 2 MB per call, 1 MB per file; a whole site goes through "Move a site here" in the dashboard, not this.
Inputs: files (required), domain (required), confirm.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Manage Rivervo websites, domains, mail, cloud servers and app deployments from your AI assistant.
Register, transfer and manage domain names and DNS from your AI agent.
Host websites, apps, databases, domains and mail at Cubli (EU) from your AI tool.
Deploy and manage static websites on FluxHost directly from your AI assistant.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to manage Combell hosting resources such as domains, DNS, mailboxes, databases, and SSL certificates through natural language.74MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage O2Switch hosting accounts, including deploying sites, managing subdomains, SSL certificates, WordPress, email, cron jobs, and more, with human confirmation for sensitive actions.2MIT
- FlicenseBqualityCmaintenanceEnables deploying sites, managing databases, and troubleshooting deployments on Hostwares from AI assistants.14-
- AlicenseNot gradedqualityCmaintenanceEnables searching for and purchasing domain names, checking trademark registers, and deploying, listing, and editing static websites at those domains directly from an AI assistant. Publishing and checkout are confirmed by the user in the browser.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.