Skip to content

Opafex

by opafex.com · remote · no sign-in to list tools · v1.0.0 · published by com.opafex

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

Changes · 3
CompareRegistry entry

5 tools: 3 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http business-automation https://opafex.com/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 3Claude Code: ask
  • assess_automation_opportunitiesWorks out what a small business should automate first, from how it runs today, instead of a generic list of AI tools.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find what to automate first
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • draft_ai_policyDrafts 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Draft an AI policy for a small firm
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • estimate_automation_paybackWorks 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 o…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Will automating it pay for itself?
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 2Claude Code: allow
  • check_ai_data_protectionLists 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.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check before client data goes into AI
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • get_sector_playbookDescribes 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.No findings

    Why it is in this group

    • The name "get_sector_playbook" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What AI does in your sector
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http business-automation https://opafex.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__business-automation__get_sector_playbook",
      "mcp__business-automation__check_ai_data_protection"
    ],
    "ask": [
      "mcp__business-automation__assess_automation_opportunities",
      "mcp__business-automation__draft_ai_policy",
      "mcp__business-automation__estimate_automation_payback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as business-automation. Review it before you use it.