# The Automators (remote · mcp.theautomators.ai)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `mcp.theautomators.ai`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ai-theautomators-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-theautomators-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.theautomators.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 89/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 6880 tokens (~52/item across 131 items; 18 tools + 113 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http ai-theautomators-mcp 'https://mcp.theautomators.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-theautomators-mcp": {
      "url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-theautomators-mcp": {
      "type": "http",
      "url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-theautomators-mcp --url 'https://mcp.theautomators.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-theautomators-mcp:
    url: "https://mcp.theautomators.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-theautomators-mcp": {
      "Transport": "http",
      "Url": "https://mcp.theautomators.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-theautomators-mcp -t streamable-http -u 'https://mcp.theautomators.ai/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71, +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.

### 2026-09-25 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 69, +1)

- [functional] New resource “AI Automation for Construction Companies Protects Margins”

### 2026-09-21 (score 68, +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.

### 2026-09-20 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-19 (score 67)

First indexed and scored.

## MCP tools (18)

### `get_company_profile` (~94 tokens)

Company profile

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

### `get_contact_options` (~84 tokens)

Contact options

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.

### `get_faq` (~104 tokens)

Frequently asked questions

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.

Input parameters:

- `topic` (string): "general", "pricing", or a service/industry/tool slug such as "ai-voice-communication" or "healthcare"

### `list_services` (~52 tokens)

List services

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

### `get_service` (~86 tokens)

Service detail

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.

Input parameters:

- `slug` (string, required): Service slug, e.g. "ai-voice-communication"

### `get_pricing` (~85 tokens)

Pricing model

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.

### `get_engagement_process` (~67 tokens)

Engagement process

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.

### `list_industries` (~47 tokens)

List industries

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.

### `get_industry_playbook` (~90 tokens)

Industry playbook

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.

Input parameters:

- `slug` (string, required): Industry slug, e.g. "healthcare"

### `list_case_studies` (~57 tokens)

List case studies

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.

### `get_case_study` (~57 tokens)

Case study detail

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

Input parameters:

- `slug` (string, required): Case study slug, e.g. "scada-system-automation"

### `get_blog_post` (~94 tokens)

Blog post

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

Input parameters:

- `slug` (string, required): Post slug from search_content, e.g. "legal-workflow-automation-a-practical-guide-for-modern-teams"

### `check_service_area` (~95 tokens)

Check service area

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.

Input parameters:

- `query` (string, required): A place, e.g. "Calgary", "Portsmouth, VA", "Ontario", "Berlin"

### `search_content` (~103 tokens)

Search site content

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.

Input parameters:

- `limit` (integer): Maximum results (1 to 20)
- `query` (string, required): Keywords, e.g. "voice agent" or "invoice processing"

### `estimate_roi` (~212 tokens)

Estimate automation ROI

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.

Input parameters:

- `automationEfficiency` (number): Share of manual hours automation removes (default 0.70; presets use 0.60 to 0.75)
- `employees` (integer): People doing the manual work (1 to 100)
- `errorRate` (number): Percent of manual work containing errors (0 to 25)
- `hourlyCost` (integer): Fully loaded hourly cost per person, CAD (15 to 150)
- `hoursPerWeek` (integer): Hours per person per week on manual tasks (1 to 40)
- `industry` (string): Optional preset; fills any input left out and sets automationEfficiency unless given explicitly

### `assess_ai_readiness` (~115 tokens)

Assess AI readiness

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.

Input parameters:

- `answers` (array): One score from 1 to 4 per question, in question order (10 questions). Omit to receive the questions.

### `prioritize_processes` (~88 tokens)

Prioritize processes to automate

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.

Input parameters:

- `processes` (array, required)

### `estimate_customer_service_savings` (~211 tokens)

Estimate customer service savings

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.

Input parameters:

- `afterHoursPercent` (integer): Percent of tickets arriving after hours (0 to 60)
- `agentHourlyCost` (integer): Agent hourly cost, CAD (15 to 75)
- `agentsOnStaff` (integer): Agents on staff (1 to 50)
- `avgHandleTime` (integer): Average handle time in minutes (2 to 30)
- `avgResponseTime` (integer): Average first response time in minutes (1 to 120)
- `industry` (string): Optional preset; fills any input left out
- `monthlyTickets` (integer): Support tickets per month (100 to 50000)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-theautomators-mcp/mcp#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 71
- 2026-09-26: 70
- 2026-09-25: 70
- 2026-09-24: 69
- 2026-09-23: 69
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67

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

## Links

- Remote endpoint: https://mcp.theautomators.ai/mcp
- Website: https://theautomators.ai/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/ai-theautomators-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-theautomators-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-theautomators-mcp/mcp