ASD-STE100 Simplified Technical English

Official

by dfch · Python

An MCP server for the ASD-STE100 (Simplified Technical English) Issue 9 standard.

An MCP server that provides support related to the ASD-STE100 Issue 9 standard (“Simplified Technical English”). It is intended for use in environments that interact with MCP servers to access standard-specific functionality and content tied to ASD-STE100.

🛠️ Key Features

Implements/targets the ASD-STE100 standard, Issue 9
Focuses on Simplified Technical English

🚀 Use Cases

Working with or validating content according to ASD-STE100 Issue 9
Integrating Simplified Technical English standard references into MCP-based tooling

⚡ Developer Benefits

Provides an MCP server interface for ASD-STE100 (Issue 9) support

⚠️ Limitations

Available source data includes only the server name and short description; no additional capabilities, tools, or constraints are specified

Topics

asd-ste100mcpmcp-serverpythonste100

README.md13 KBView on GitHub

biz.dfch.AsdSte100Mcp

Python

An MCP server for the ASD-STE100 (Simplified Technical English) Issue 9 standard.

ASD-STE100: Copyright by (c) ASD.

I am in no way affiliated with ASD. ASD does not endorse my work.

Tools
Resources
Installation
Usage
Authentication
Add to OpenCode
Development
Related Projects
Make a Release
License

Authentication

This server exposes only read-only lookup tools and resources over vocabulary and rules data that is bundled with the package; there is nothing to authenticate against. No API keys, tokens, or credentials are required or supported in either stdio or sse transport mode. If you expose the sse transport beyond localhost, secure it at the network layer (e.g. a reverse proxy) rather than expecting the server to authenticate requests itself.

Tools

Vocabulary

Tool	Description
`word_find`	Search for a term by exact name (case-insensitive) in the ASD-STE100 Issue 9 vocabulary. Return approved/rejected status, part of speech, STE examples, and approved alternatives. Use this first when you know the exact word. Use `word_match` with a wildcard if this tool returns no items.
`word_find_many`	Search for multiple terms by exact name (case-insensitive) in a single call. Returns one `WordFindEntry` per input term (`term` + `results`), in the same order as the input, each holding 0, 1, or more matching vocabulary entries.
`word_match`	Search the vocabulary using a regular expression pattern. Return all entries whose term matches. Use it to find all words with a common prefix or pattern (e.g. ^de or .*tion$). Paginated (`max_results`/`offset`); returns a `WordResult`.
`word_fuzzy`	Search for a term with sequence-matching (Python difflib.get_close_matches). Results may not be obvious — use when `word_find` returns nothing and you want fuzzy suggestions.
`word_list`	Return all vocabulary entries. Only use when you need to process the full vocabulary. Use `word_count` instead if you only need the total. Paginated (`max_results`/`offset`); returns a `WordResult`.
`word_count`	Return the total number of entries in the vocabulary. Use instead of `word_list` when you only need the count.
`word_synonym`	Search for vocabulary entries that are WordNet synonyms of a word, via the `biz-dfch-asdste100nlp` library's `Nlp` class. Use this to find approved alternatives for a non-STE word.

Rules

Tool	Description
`rules_find`	Search for rules in the ruleset by exact id (case-insensitive), e.g. `R1.1` or `GR-8`. Use this first when you know the exact id.
`rules_match`	Search rules using a regular expression matched against the rule `name` and `summary`.
`rules_search`	Full-text search across every text a rule carries (section, category, name, summary, and all content blocks: text, notes, examples, technical noun/verb lists). Optionally restrict to specific content types. Paginated (`max_results`/`offset`); returns a `SearchResult`.
`rules_by_section`	Search for rules by exact section name (case-insensitive), e.g. `Words`.
`rules_by_category`	Search for rules by exact category name (case-insensitive), e.g. `Technical nouns`.
`rules_examples`	Return content items across rules, optionally scoped by id/section/category and filtered by content type. Paginated (`max_results`/`offset`); returns a `RulesExamplesResult`.
`rules_overview`	Return a lightweight, per-rule overview (id, type, section, category, name, optional summary, and content counts/flags) without shipping every content item.
`rules_toc`	Return the distinct (section, category) pairs as a table-of-contents outline, optionally scoped to one section.

Resources

Read-only resources let a client browse or attach ruleset data directly (e.g. via an "@mention" or resource picker), without going through a tool call.

Resource URI	Description
`asdste100://rules/toc`	Table-of-contents outline of the ruleset: the distinct (section, category) pairs, each with the ids they contain. Mirrors the `rules_toc` tool with no `section` filter.
`asdste100://rules/rule/{id_}`	A single rule/recommendation/information item by exact id (case-insensitive), e.g. `asdste100://rules/rule/R1.1`. Mirrors the `rules_find` tool; an unknown id resolves to an empty list rather than an error.
`asdste100://version`	Installed version numbers of the MCP server itself and its three data-backing libraries: `biz-dfch-asdste100vocab`, `biz-dfch-asdste100rules`, and `biz-dfch-asdste100nlp`.

Installation

bash

pip install biz-dfch-asdste100mcp

Or with uv:

bash

uv add biz-dfch-asdste100mcp

Usage

MCP Inspector

If you want to test the MCP server without a tool like OpenCode, you can do this with MCP Inspector.

MCP Inspector is part of the mcp[cli] package. When you install this project with --extra dev you can use MCP Inspector.

NOTE: The examples below use bunx instead of npx to launch MCP Inspector; npx has not been tested.

stdio (Claude Desktop, OpenCode, and other MCP hosts)

bash

asdste100-mcp

Run MCP Inspector against the server over stdio:

bash

bunx @modelcontextprotocol/inspector uv run --frozen --directory . asdste100-mcp

MCP Inspector with stdio

NOTE: Sometimes, the MCP Inspector cannot connect to the MCP server via stdio. Use the sse option (see below) instead.

SSE / network

bash

asdste100-mcp --transport sse --host localhost --port 8000

NOTE: You do not have to supply the option --port to the MCP server. The default value of port is 8000.

Start the server, then connect MCP Inspector to it — these are two separate commands, run in two separate terminals:

bash

# terminal 1: start the server
uvx --from . asdste100-mcp -t sse

bash

# terminal 2: launch the inspector and connect it to the running server
bunx @modelcontextprotocol/inspector

Start the MCP server with uvx and then start the MCP Inspector with bunx

MCP Inspector with sse

Options

Option	Env var	Default	Description
`--transport`	`ASDSTE100_MCP_TRANSPORT`	`stdio`	Transport mode: `stdio` or `sse`
`--host`	`ASDSTE100_MCP_HOST`	`localhost`	Bind address (SSE only)
`--port`	`ASDSTE100_MCP_PORT`	`8000`	TCP port (SSE only)
`--env`	—	auto-discovered	Path to a `.env` file
`--file` / `-f`	`ASDSTE100_MCP_FILES`	(empty)	Path to a vocabulary file (`*.jsonl`); repeatable
`--rules-file` / `-r`	`ASDSTE100_MCP_RULES_FILES`	(empty)	Path to a rules file (a single JSON array); repeatable

Vocabulary configuration

Env var	Default	Description
`ASDSTE100_MCP_FILES`	(empty)	Colon-separated paths to additional vocabulary files
`ASDSTE100_MCP_USE_STE100`	`true`	Load the built-in ASD-STE100 Issue 9 vocabulary
`ASDSTE100_MCP_USE_STE100_TECHNICAL_WORDS`	`false`	Also load the technical words vocabulary

Rules configuration

Env var	Default	Description
`ASDSTE100_MCP_RULES_FILES`	(empty)	Colon-separated paths to additional rules files (each a single JSON array)
`ASDSTE100_MCP_USE_STE100_RULES`	`true`	Load the built-in ASD-STE100 Issue 9 ruleset

Add to OpenCode

To add the ASD-STE100 (Simplified Technical English) MCP server to your OpenCode configuration:

Open your OpenCode config file (typically ~/.config/opencode/opencode.json or ~/.config/opencode/opencode.jsonc)
Add the following configuration to the mcp section (and use it via stdio):

json

"asdste100": {
  "type": "local",
  "enabled": true,
  "command": ["uvx", "--from", "biz-dfch-asdste100mcp", "asdste100-mcp"]
}

Save the file and restart OpenCode

This enables OpenCode to access ASD-STE100 vocabulary and rules lookups for technical writing and documentation compliance.

Development

Install dev dependencies

bash

uv sync --all-extras

Run linters

bash

uv run --frozen ruff format --check
uv run --frozen ruff check
uv run --frozen pylint $(git ls-files '*.py')

Run tests

bash

uv run --frozen python -m unittest discover -v -s tests -t . -p "test_*.py"

This server is part of the ASD-STE100 tooling family:

biz.dfch.AsdSte100Vocab — the ASD-STE100 Issue 9 vocabulary library
biz.dfch.AsdSte100Rules — the ASD-STE100 Issue 9 ruleset library
biz.dfch.AsdSte100Nlp — WordNet-based synonym lookup for ASD-STE100 words
biz.dfch.AsdSte100Lookup — an interactive CLI to look up words and rules
biz.dfch.AsdSte100Mcp — this repo: an MCP server exposing vocabulary and rules lookup tools

Make a Release

1. Make sure all tests pass

Before releasing, make sure the CI pipeline is green on the dev branch:

bash

uv run --frozen ruff format --check
uv run --frozen ruff check
uv run --frozen pylint $(git ls-files '*.py')
uv run --frozen python -m unittest discover -v -s tests -t . -p "test_*.py"

2. Increase the version

Update the version in pyproject.toml:

toml

version = "x.y.z"

3. Commit and push to `dev`

bash

git add pyproject.toml CHANGELOG.md
git commit -m "chore: bump version to vx.y.z"
git push origin dev

4. Merge `dev` into `main`

bash

git checkout main
git merge dev
git push origin main

5. Create and push a version tag

bash

export VERSION=x.y.z
git tag v${VERSION}
git push origin v${VERSION}

Pushing the tag triggers the publish.yml workflow, which will:

Build the sdist and wheel.
Publish to TestPyPI (environment testpypi).
Publish to PyPI (environment pypi), only if TestPyPI succeeded.
Publish to the MCP Registry (publish-to-mcp-registry job) — requires the new version to be live on PyPI first.
Create a GitHub Release with auto-generated notes and the distribution artifacts attached.

Then switch back to dev to continue work:

bash

git checkout dev

Configure Trusted Publishing

The workflow uses OIDC Trusted Publishing — no API tokens or secrets are needed.

GitHub: create environments

Go to your repo → Settings → Environments and create two environments:

Environment	Recommended protection
`testpypi`	None required
`pypi`	Add a required reviewer to prevent accidental production releases

TestPyPI

Field	Value
PyPI project name	`biz-dfch-asdste100mcp`
Owner	`dfch`
Repository	`biz.dfch.AsdSte100Mcp`
Workflow name	`publish.yml`
Environment	`testpypi`

PyPI

Field	Value
PyPI project name	`biz-dfch-asdste100mcp`
Owner	`dfch`
Repository	`biz.dfch.AsdSte100Mcp`
Workflow name	`publish.yml`
Environment	`pypi`

MCP Registry Publishing

The publish-to-mcp-registry job uses GitHub OIDC authentication and does not require additional setup — it will automatically publish to the official MCP Registry once the package is live on PyPI.

Verify your server is registered:

bash

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.dfch/biz-dfch-asdste100mcp"

License

AGPL-3.0-or-later

Install

Configuration

Environment variables

ASDSTE100_MCP_TRANSPORT

Transport mode: stdio or sse

ASDSTE100_MCP_HOST

Bind address (SSE transport only)

ASDSTE100_MCP_PORT

TCP port (SSE transport only)

ASDSTE100_MCP_FILES

Colon-separated paths to additional vocabulary .jsonl files

ASDSTE100_MCP_USE_STE100

Load the built-in ASD-STE100 Issue 9 vocabulary

ASDSTE100_MCP_USE_STE100_TECHNICAL_WORDS

Also load the technical words vocabulary

ASDSTE100_MCP_RULES_FILES

Colon-separated paths to additional rules files (JSON array each)

ASDSTE100_MCP_USE_STE100_RULES

Load the built-in ASD-STE100 Issue 9 ruleset

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "biz-dfch-asdste100mcp": {
      "command": "uvx",
      "args": [
        "biz-dfch-asdste100mcp"
      ],
      "env": {
        "ASDSTE100_MCP_TRANSPORT": "<YOUR_ASDSTE100_MCP_TRANSPORT>",
        "ASDSTE100_MCP_HOST": "<YOUR_ASDSTE100_MCP_HOST>",
        "ASDSTE100_MCP_PORT": "<YOUR_ASDSTE100_MCP_PORT>",
        "ASDSTE100_MCP_FILES": "<YOUR_ASDSTE100_MCP_FILES>",
        "ASDSTE100_MCP_USE_STE100": "<YOUR_ASDSTE100_MCP_USE_STE100>",
        "ASDSTE100_MCP_USE_STE100_TECHNICAL_WORDS": "<YOUR_ASDSTE100_MCP_USE_STE100_TECHNICAL_WORDS>",
        "ASDSTE100_MCP_RULES_FILES": "<YOUR_ASDSTE100_MCP_RULES_FILES>",
        "ASDSTE100_MCP_USE_STE100_RULES": "<YOUR_ASDSTE100_MCP_USE_STE100_RULES>"
      }
    }
  }
}

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

biz.dfch.AsdSte100Mcp

Table of Contents

Authentication

Tools

Vocabulary

Rules

Resources

Installation

Usage

MCP Inspector

stdio (Claude Desktop, OpenCode, and other MCP hosts)

SSE / network

Options

Vocabulary configuration

Rules configuration

Add to OpenCode

Development

Install dev dependencies

Run linters

Run tests

Related Projects

Make a Release

1. Make sure all tests pass

2. Increase the version

3. Commit and push to dev

4. Merge dev into main

5. Create and push a version tag

Configure Trusted Publishing

GitHub: create environments

TestPyPI

PyPI

MCP Registry Publishing

License

Install

Configuration

3. Commit and push to `dev`

4. Merge `dev` into `main`