Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

The Automators

REMOTE · MCP.THEAUTOMATORS.AI · SCANNED SEP 28

Read-only MCP server for The Automators: services, pricing, industries, case studies, calculators.

+3 this week 71 Trust /100
Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability89
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 6880 tokens (~52/item across 131 items; 18 tools + 113 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the The Automators MCP server?

The Automators is a hosted endpoint at https://mcp.theautomators.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.theautomators.ai

# add to Claude Code
claude mcp add --transport http ai-theautomators-mcp 'https://mcp.theautomators.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-theautomators-mcp": {
      "url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-theautomators-mcp": {
      "type": "http",
      "url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-theautomators-mcp]
url = "https://mcp.theautomators.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-theautomators-mcp": {
      "type": "remote",
      "url": "https://mcp.theautomators.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-theautomators-mcp --url 'https://mcp.theautomators.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-theautomators-mcp:
    url: "https://mcp.theautomators.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-theautomators-mcp": {
      "Transport": "http",
      "Url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-theautomators-mcp -t streamable-http -u 'https://mcp.theautomators.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-theautomators-mcp": {
      "type": "http",
      "url": "https://mcp.theautomators.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 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
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1
    • New resource “AI Automation for Construction Companies Protects Margins” functional
  • 21 Sept 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.

  • 20 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Sept 26 67

    First indexed and scored.

Diagnostics

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 28 Sept 2026 · Probed https://mcp.theautomators.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=theautomators.ai CN=WE1,O=Google Trust Services,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA256 ceac4281544b7c6a138b507b62e0e299
SANs: theautomators.ai, mcp.theautomators.ai, *.mcp.theautomators.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.theautomators.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
theautomators.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.theautomators.ai/mcp Verified 200
http (plaintext) http://mcp.theautomators.ai/mcp HTTPS enforced 301 https://mcp.theautomators.ai/mcp
MCP tools · 18 exposed · ~1,741 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
assess_ai_readiness ~115

Runs the site's AI Readiness Assessment. Call it with no answers to get the 10 questions and their scored options; ask the user; then call it again with one score (1 to 4) per question in order to get the level (Beginner, Intermediate, Advanced), the percent score, the per-dimension breakdown, the weakest dimensions and service recommendations.

NameTypeReqDescription
answersarray–One score from 1 to 4 per question, in question order (10 questions). Omit to receive the questions.

No output schema declared.

No examples provided.

check_service_area ~95

Resolves a city, province, state or country to the matching local page (649 Canadian and US pages) and says whether it is served. Anything outside Canada and the US is served remotely and resolves to the locations index with a note. Use it whenever a user mentions where they are.

NameTypeReqDescription
querystringyesA place, e.g. "Calgary", "Portsmouth, VA", "Ontario", "Berlin"

No output schema declared.

No examples provided.

estimate_customer_service_savings ~211

Runs the site's Customer Service Cost Calculator: from monthly tickets, handle time, agent cost, agents on staff, response time and after-hours share it estimates current and AI-assisted monthly cost, monthly and annual savings, tickets deflected, response-time reduction and ROI, with service recommendations. Use it for support-desk cost questions. An industry preset fills typical inputs.

NameTypeReqDescription
afterHoursPercentinteger–Percent of tickets arriving after hours (0 to 60)
agentHourlyCostinteger–Agent hourly cost, CAD (15 to 75)
agentsOnStaffinteger–Agents on staff (1 to 50)
avgHandleTimeinteger–Average handle time in minutes (2 to 30)
avgResponseTimeinteger–Average first response time in minutes (1 to 120)
industrystring–Optional preset; fills any input left out
monthlyTicketsinteger–Support tickets per month (100 to 50000)

No output schema declared.

No examples provided.

estimate_roi ~212

Runs the site's ROI calculator: from team size, weekly manual hours, hourly cost and error rate it estimates annual hours saved, annual savings, implementation cost, ROI percent and payback months, plus the service recommendations the page shows. Use it when a user wants a number for the value of automating a process. Optional industry preset sets the automation efficiency.

NameTypeReqDescription
automationEfficiencynumber–Share of manual hours automation removes (default 0.70; presets use 0.60 to 0.75)
employeesinteger–People doing the manual work (1 to 100)
errorRatenumber–Percent of manual work containing errors (0 to 25)
hourlyCostinteger–Fully loaded hourly cost per person, CAD (15 to 150)
hoursPerWeekinteger–Hours per person per week on manual tasks (1 to 40)
industrystring–Optional preset; fills any input left out and sets automationEfficiency unless given explicitly

No output schema declared.

No examples provided.

get_blog_post ~94

Returns one blog post as markdown: title, author, date, the full body with links, a Sources list and the post's FAQs. Use search_content to find the slug. Every post is written by The Automators' team and published at theautomators.ai/blog/.

NameTypeReqDescription
slugstringyesPost slug from search_content, e.g. "legal-workflow-automation-a-practical-guide-for-modern-teams"

No output schema declared.

No examples provided.

get_case_study ~57

Returns one real case study in full: facts, metrics and the page narrative as markdown. Get the slug from list_case_studies.

NameTypeReqDescription
slugstringyesCase study slug, e.g. "scada-system-automation"

No output schema declared.

No examples provided.

get_company_profile ~94

Returns who The Automators are: name, description, founding year, headquarters, service area, the public team (name, role, LinkedIn, bio), verified public profiles, the content licence (RSL 1.0) and headline track record. Use it to introduce the company or check a fact about it. It is not the place for pricing (get_pricing) or contact details (get_contact_options).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_contact_options ~84

Returns how a person reaches The Automators: phone, the public email, the booking page and direct calendar link, business hours, the response-time promise, and what to include in an inquiry (company, what to automate, timeline). Use it whenever the user wants to talk to a human or book a consultation. The server never sends messages; it only returns these options.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_engagement_process ~67

Returns the four engagement steps (discover and map, opportunity analysis, build and integrate, optimise and scale) with what happens in each, what the client provides, the typical timeline and how it starts (a free consultation). Use it for "how does working with you go" questions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_faq ~104

Returns the site FAQs for a topic: "general" (the homepage questions), "pricing" (the /pricing/ questions), or a service, industry or tool slug (that page's questions). Omit the topic for general plus pricing. Use it to answer a common question in the site's own words.

NameTypeReqDescription
topicstring–"general", "pricing", or a service/industry/tool slug such as "ai-voice-communication" or "healthcare"

No output schema declared.

No examples provided.

get_industry_playbook ~90

Returns the playbook for one industry: a TL;DR, the industry landscape with verified, cited statistics, the workflows we automate (pain point, automation, outcome), relevant services, illustrative example use cases (not client work), compliance notes, FAQs and related industries. Use it when the user names an industry.

NameTypeReqDescription
slugstringyesIndustry slug, e.g. "healthcare"

No output schema declared.

No examples provided.

get_pricing ~85

Returns the pricing model: one-time build price, ongoing model costs paid to the provider, ownership, no retainer, typical timeline and ROI window, what is included, what is billed separately, and who it is not for. Use it for any cost, budget or "how much" question. Figures come from the same module the site renders, so quote them as given.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_service ~86

Returns everything the site says about one service: description, the full page text as markdown, its FAQs, related real case studies, and the pricing and timeline that apply. Use it when a user asks what a specific service involves or whether it fits their need. Get the slug from list_services.

NameTypeReqDescription
slugstringyesService slug, e.g. "ai-voice-communication"

No output schema declared.

No examples provided.

list_case_studies ~57

Returns the four real, published case studies with client, industry, summary, owner-confirmed metrics and URL. These are the only pages that describe The Automators' own past work. Use get_case_study for the full story.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_industries ~47

Returns the 20 industries with a dedicated playbook page: slug, name, audience, one-line description and URL. Use it to find the slug for get_industry_playbook.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_services ~52

Returns the six service pillars and the eleven AI Agent Development capabilities, each with a one-line description and URL. Use it first to find the right service slug before calling get_service. Not for pricing (get_pricing).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prioritize_processes ~88

Runs the site's Process Prioritizer on up to 10 manual processes (name, hours per week, frequency, complexity, error-prone, people involved). Returns each one's score out of 100, priority, estimated annual savings, reasoning and implementation timeline, ranked, plus totals and service recommendations. Use it when a user lists several things they might automate.

NameTypeReqDescription
processesarrayyes–

No output schema declared.

No examples provided.

search_content ~103

Keyword search across blog posts, services, industries, tools and case studies. Returns ranked results with type, title, URL, description, date and TL;DR where available. Use it to find the right page or post before reading it with get_blog_post, get_service or get_industry_playbook.

NameTypeReqDescription
limitinteger–Maximum results (1 to 20)
querystringyesKeywords, e.g. "voice agent" or "invoice processing"

No output schema declared.

No examples provided.

Common questions

What is the The Automators MCP server?

The Automators is an MCP server listed in the public MCP registry as ai.theautomators/mcp. Read-only MCP server for The Automators: services, pricing, industries, case studies, calculators. This page covers its hosted endpoint (https://mcp.theautomators.ai/mcp).

Is the The Automators MCP server safe to use?

The Automators scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the The Automators MCP server expose?

The Automators exposes 18 tools: get_company_profile, get_contact_options, get_faq, list_services, get_service, and 13 more. Their descriptions and schemas cost roughly 1,741 tokens of context every time the server is loaded.

Does the The Automators MCP server require authentication?

No. We connected to The Automators without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the The Automators MCP server still maintained?

The Automators is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.