# Opafex

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

- name: com.opafex/business-automation
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 94/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.opafex%2Fbusiness-automation
- tools: https://api.protogrid.dev/v1/servers/com.opafex%2Fbusiness-automation/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-6d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 94/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,341 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 6 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 2,341 tokens to load them all
- tool set hash: 1ffb110376984d0e3126ac50ac9b690b
- tools last changed: 2026-10-18T01:53:03.031Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.opafex/business-automation.svg)](https://protogrid.dev/servers/com.opafex/business-automation)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-18 `assess_automation_opportunities` changed (inputSchema)
- 2026-10-17 `assess_automation_opportunities` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/com.opafex%2Fbusiness-automation/changes

## Remotes

- https://opafex.com/api/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `assess_automation_opportunities`: 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.
- `check_ai_data_protection`: 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.
- `draft_ai_policy`: 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.
- `estimate_automation_payback`: 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.
- `get_sector_playbook`: 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.