# Opafex (remote · opafex.com)

Helps UK small business owners decide where AI fits: what to automate first, data checks, payback.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `opafex.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-opafex-business-automation/api-mcp.md), [page](https://verifymcp.io/servers/com-opafex-business-automation/api-mcp)

## Channel facts

- Endpoint: `https://opafex.com/api/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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1581 tokens (~316/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Opafex MCP server?

Opafex is a hosted endpoint at https://opafex.com/api/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 com-opafex-business-automation 'https://opafex.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-opafex-business-automation": {
      "url": "https://opafex.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-opafex-business-automation": {
      "type": "http",
      "url": "https://opafex.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-opafex-business-automation]
url = "https://opafex.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-opafex-business-automation": {
      "type": "remote",
      "url": "https://opafex.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-opafex-business-automation --url 'https://opafex.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-opafex-business-automation:
    url: "https://opafex.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-opafex-business-automation": {
      "Transport": "http",
      "Url": "https://opafex.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-opafex-business-automation -t streamable-http -u 'https://opafex.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-opafex-business-automation": {
      "type": "http",
      "url": "https://opafex.com/api/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-11-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +1)

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

### 2026-10-30 (score 80, +1)

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

### 2026-10-28 (score 79, +1)

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

### 2026-10-25 (score 78, +1)

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

### 2026-10-23 (score 77, +1)

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

### 2026-10-21 (score 76, +1)

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

## MCP tools (5)

### `assess_automation_opportunities` (~527 tokens)

Find what to automate first

Works out what a small business should automate first, from how it runs today, instead of a generic list of AI tools. Use when an owner asks how AI can help their business, where to start, what is worth it versus hype, or how to get good people off admin. Map what the owner has said onto the options and leave out anything they have not said. Returns the best-fitting approaches with the reasons, what to check first, a small first step, and the questions still worth asking.

Input parameters:

- `outputs` (string): What goes out to your clients? Options: documents = "Reports, proposals and quotes"; answers = "Answers by email, chat and phone"; jobs = "Job sheets and site records"; internal = "Not much leaves th…
- `producers` (string): Who produces the work that goes out? Options: founder = "Me, mostly"; professionals = "Fee-earners, each doing their own"; admin = "An admin or operations team"; field = "Whoever is on site".
- `prompting` (string): What made you start looking? Options: answering = "We answer the same questions daily"; admin = "Good people are doing admin"; field = "Site work comes back on paper"; unsure = "Nobody here knows whe…
- `retyping` (string): Where does information get retyped? Options: systems = "Between two systems"; paper = "Off paper and photos"; inbox = "Out of the inbox"; none = "Nowhere obvious".
- `sector` (string): The firm's sector. plumbing-electrical-and-other-trades = plumbers, electricians, heating engineers, window fitters and other trades working on customers' jobs; construction = contractors and constru…
- `software` (string): Which systems do you run the business on? Options: mainstream = "Microsoft or Google, plus a CRM"; industry = "An industry system and spreadsheets"; spreadsheets = "Spreadsheets and email"; bespoke =…
- `teamSize` (string): Number of people in the firm.
- `wand` (string): Which task would you never do again? Options: chasing = "Chasing people for information"; writing = "Writing the same document again"; answering = "Answering the same question again"; writeup = "Writ…

### `get_sector_playbook` (~171 tokens)

What AI does in your sector

Describes how a specific type of UK firm uses AI: what gets drafted, chased or checked, what to look for in a tool, and the questions firms in that sector ask. Use when an owner or partner in accountancy, recruitment, a law firm, financial planning, insurance broking, an estate or letting agency, construction or a trade such as plumbing or electrical work asks how firms like theirs use AI. Use other for any other small business.

Input parameters:

- `sector` (string, required): The firm's sector. plumbing-electrical-and-other-trades = plumbers, electricians, heating engineers, window fitters and other trades working on customers' jobs; construction = contractors and constru…

### `check_ai_data_protection` (~224 tokens)

Check before client data goes into AI

Lists what a UK firm should check before client or staff information goes into an AI tool, under UK GDPR, ordered by what matters most for that tool and that data. Use when an owner asks if they can put client information into ChatGPT, whether ChatGPT or Copilot is GDPR compliant for their business, what to do about staff pasting customer details into AI, or what to ask an AI supplier. Returns questions to ask with the reason for each, not legal advice.

Input parameters:

- `data` (array, required): What would go in. special_category = health, ethnicity, religion, sexual orientation and similar; criminal_records = criminal offence data such as background checks.
- `regulated` (boolean): True if the firm is regulated by a professional or financial regulator.
- `tool` (string, required): personal_account = a personal or free login to a general AI chat tool; business_plan = a business or team plan of one; built_into_software = AI features inside software the firm already uses; special…

### `draft_ai_policy` (~203 tokens)

Draft an AI policy for a small firm

Drafts a one-page AI use policy for a small UK firm: approved tools, what must never be pasted in, human checking, telling clients, and who is responsible. Use when an owner asks whether they need an AI policy, what to put in one, or how to stop staff pasting client details into AI tools. Returns the clauses and the steps to take before adopting it. A starting draft, not legal advice.

Input parameters:

- `data` (array, required): What information staff might put into AI tools. Use no_personal_data if none.
- `regulated` (boolean): True if the firm is regulated by a professional or financial regulator.
- `teamSize` (string): Number of people in the firm.
- `uses` (array, required): What staff use or will use AI for. drafting_and_research; client_communication = drafting emails or letters to clients; meeting_notes = recording or transcribing meetings; decisions_about_people = sc…

### `estimate_automation_payback` (~229 tokens)

Will automating it pay for itself?

Works out whether automating a task pays for itself, from the owner's own hours, headcount, hourly cost and supplier quote, with every assumption stated and time for checking the output deducted. Use when an owner asks if an AI tool or automation is worth the money, how long it takes to pay back, or how to estimate the return before committing. Ask the owner for the numbers rather than guessing them.

Input parameters:

- `automatableShare` (string, required): How much of the task could a tool do? small = a quarter; about_half; most = around 70%. If unsure, use small.
- `hourlyCost` (number, required): What an hour of those people's time costs the firm, in pounds.
- `hoursPerWeekPerPerson` (number, required): Hours a week one person spends on the task.
- `monthlyToolCost` (number): The supplier's monthly price in pounds, from the owner's own quote.
- `people` (integer, required): How many people do the task.
- `setupCost` (number): One-off setup cost in pounds, including the team's time to learn it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-opafex-business-automation/api-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72

## Common questions

### What is the Opafex MCP server?

Opafex is an MCP server listed in the public MCP registry as com.opafex/business-automation. Helps UK small business owners decide where AI fits: what to automate first, data checks, payback. This page covers its hosted endpoint (https://opafex.com/api/mcp).

### Is the Opafex MCP server safe to use?

Opafex scores 83 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 Opafex MCP server expose?

Opafex exposes 5 tools: assess_automation_opportunities, get_sector_playbook, check_ai_data_protection, draft_ai_policy, estimate_automation_payback. Their descriptions and schemas cost roughly 1,354 tokens of context every time the server is loaded.

### Does the Opafex MCP server require authentication?

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

### Is the Opafex MCP server still maintained?

Opafex is still listed as active in the MCP registry. We last reached this channel on 5 November 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://opafex.com/api/mcp
- Website: https://opafex.com/assistant-tools
- Changelog RSS feed: https://verifymcp.io/servers/com-opafex-business-automation/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-opafex-business-automation/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-opafex-business-automation/api-mcp