
Colregs Mcp
io.github.mark-brannanPublished by GitHub account mark-brannanv0.0.7Updated Nov 5, 2026
Not for navigation. Pre-release preview: COLREGS Part C night lights, international text only.
Overview
Local MCP server that answers COLREGS (Part C night lights) questions with cited, verbatim rule text, so an assistant can evaluate vessel lighting and…
- What you can do
- Evaluate a vessel's circumstances (own facts, other vessels, conditions) and get signals, appraisal, indicated identities and compliance readings
- Look up the verbatim text of a COLREGS paragraph, rule or paragraph range
- Retrieve a light's Rule 21 definition: colour, character, arc and placement
- Every answer carries paragraph cites and the verbatim text of each cited paragraph
- When to use it
- Useful when you want an assistant to reason about international collision regulations, night-light displays or encounter roles with exact rule citations rather than paraphrase. It is a pre-release preview, so treat it as a study and drafting aid, not an operational tool.
- Requirements
- Runs as a local stdio process, typically via npx with the colregs-mcp package (Node.js required), or from a built clone. No environment variables, headers, accounts or API keys. No network access at runtime; only the npm install itself uses the network.
Installation
In SourceWeft
- Open Colregs Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
colregs-mcp
[!WARNING] Not for navigation. This is a preview (0.0.x) built on pre-release rule data. Do not use its output to decide what to do on the water. The tool surface will change without notice.
An MCP server that answers questions under the COLREGS. Every answer carries its paragraph cites and the verbatim rule text those cites resolve to, so a language model cannot quietly simplify it. The rules are evaluated by colregs-engine; this package only decides how the answer is written down.
Try it
Claude Code:
Claude connector directory: in Claude, open Settings → Connectors,
search for COLREGS and click Connect. No configuration is needed.
Any other MCP client: command npx, arguments -y colregs-mcp, no
environment.
From a clone:
then command node, argument /absolute/path/to/colregs-mcp/dist/cli.js.
Tools
evaluate
circumstances is the whole picture one vessel is in: self (her own
facts), others (each other vessel, with what is known or observed of
her) and conditions (visibility, environment). One call evaluates the
picture; the response carries four readings of it.
signals: every complete, lawful set of lightsselfmay show. Each light carries its modality (shall,may,shall-if-practicable) and the paragraph that prescribes it.appraisal: what the Rules require ofselfon her own, and then against each other vessel: the kind of encounter, whether risk of collision is asserted, and each vessel's role (stand-on, give-way, shall-not-impede).indicated: for each other vessel, what her observed lights, shapes and sounds indicate she could be.compliance: over a track of circumstances sampled through time, one verdict per vessel per obligation that attached: kept, breached or pending.
Every id travels with its paragraph cite, and cited_paragraphs holds the
verbatim text of every paragraph the response cites. The input vocabulary
is generated from the colregs data package at startup. A key or value
outside it is an error, never an empty answer.
rule_text
Takes a paragraph path such as 25(b) or 26(c)(i), a bare rule number
such as 25 for every paragraph of that rule, or a range such as
24(a)(ii)-(iv). Returns the International text as transcribed from the
USCG amalgamated Navigation Rules, with its source and retrieval date.
light
Takes a light id as it appears in a response, such as light:sidelights
or light:all_round. Returns the Rule 21 definition: colour, character,
arc in degrees and placement.
Example
A 12 m sloop under way, alone.
Trimmed response:
The sloop has three lawful displays, because the Rules give her the choice and nothing in the input settles it.
docs/demo.md puts the same question to the same model with and without this server and shows both answers as captured.
Response shape
Three properties hold for every response:
- Cited, verbatim. Every entry id travels with its paragraph cite, and
cited_paragraphsholds the text of every paragraph cited. The only sentences in a response are the Rules' own. - Modality per light.
shall,mayandshall-if-practicableare kept on each light, not summarised per display.modality_keyis a one-line glossary of the modalities the response uses. - Plural by construction.
lawful_displaysopens withcountandrelationbefore any lights appear, and each option numbers itselfn of count. There is no top-levellightsfield to mistake for the answer.
A vessel that lawfully shows nothing gets one empty display, not an error. An error is reserved for input outside the vocabulary.
Every response carries colregs.version. The server refuses to start if its
own copy of colregs and the engine's are different releases.
Dependencies
colregs-engine and colregs are installed from GitHub main, not from
npm releases; the lockfile pins the commit. Both must resolve the same
release.
Privacy Policy
The server collects nothing. It runs as a local stdio process, answers from
the colregs data package installed beside it, and makes no network request
of its own. There is no telemetry, no logging of what it is asked, and no
account. The only network transaction is the install itself, which is npm's.
Releasing
Automatic from the release tag: npm and the MCP registry. The by-hand steps (Smithery, the Claude directory plugin bundle) are in docs/releasing.md.
Licence
AGPL-3.0-only. The fitness-for-navigation disclaimer in colregs carries over.
Source: README.md at commit 49fcf48
Tools
0Version history
4- v0.0.7LatestNov 5, 2026
- v0.0.6Oct 31, 2026
- v0.0.5Oct 21, 2026
- v0.0.4Oct 20, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts