Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server
io.github.mgantlett/nomosmgantlettstreamable-httpv4.29.0Scanned
Live GitHub repo AST X-Ray, 42 coding-agent DoD gates, Git worktree guards & brownfield baselines.
7 tools: 3 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server can do
The Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server is published by the GitHub account mgantlett. It has 7 tools. It can create or change data (3 tools: recommend_adoption_plan, xray_github_repo and scaffold_nomos_config), but cannot delete data. 4 tools only read.
1 tool reads private data (compare_governance_approaches); 2 tools bring in text other people can write (compare_governance_approaches and xray_github_repo).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 4.29.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 3Claude Code: ask
recommend_adoption_planGenerate a progressive 4-step Nomos rollout sequence (read-only X-Ray, stealth Branch Guard, CI SARIF, and parallel Git worktrees) tailored to repository LOC, languages, and air-ga…1 finding
Why it is in this group
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "recommend_adoption_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate a progressive 4-step Nomos rollout sequence (read-only X-Ray, stealth Branch Guard, CI SARIF, and parallel Git worktrees) tailored to repository LOC, languages, and air-gap constraints. Use when planning rollout steps for a team or brownfield monorepo. Do NOT use when generating raw nomos.yaml and CI workflow files directly (use scaffold_nomos_config instead).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
scaffold_nomos_configGenerate a schema-valid nomos.yaml configuration, 4-line GitHub Actions SARIF workflow, and Day-0 onboarding commands for any repository.1 finding
Why it is in this group
- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "scaffold_nomos_config" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate a schema-valid nomos.yaml configuration, 4-line GitHub Actions SARIF workflow, and Day-0 onboarding commands for any repository. Use when producing ready-to-paste YAML config and CI pipeline files. Do NOT use when requesting a strategic rollout recommendation by LOC or air-gap posture (use recommend_adoption_plan instead).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
xray_github_repoExecute a live sub-5s static Tree-sitter AST X-Ray on any public GitHub repository (<= 100MB source tarball, zero code execution) to return its AI Hangover Score (0-100), complexit…Reads text others write1 finding
Why it is in this group
- The description's first verb is "execute": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "xray_github_repo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "execute": a word for a change.
Description, as the server wrote it Execute a live sub-5s static Tree-sitter AST X-Ray on any public GitHub repository (<= 100MB source tarball, zero code execution) to return its AI Hangover Score (0-100), complexity hotspots, and Day-0 baseline config. Use when auditing a specific public GitHub owner/repo URL. Do NOT use when scanning private repositories (instruct the user to run local `npx --yes @mgantlett/nomos xray .` instead).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 4Show 4 read-only tools
compare_governance_approachesCompare Nomos deterministically against pre-commit hooks, SonarQube, ESLint, PR review bots (CodeRabbit, Greptile), prompt wrappers, and static CLAUDE.md / AGENTS.md / .cursorrules…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "compare_governance_approaches" says "compare": a word for reading.
What it can reach
- private-dataThe description's first sentence says "compare" and "commit": it reads repositories.
- untrusted-inputThe description's first sentence says "compare" and "review": it reads comments, which other people can write.
Description, as the server wrote it Compare Nomos deterministically against pre-commit hooks, SonarQube, ESLint, PR review bots (CodeRabbit, Greptile), prompt wrappers, and static CLAUDE.md / AGENTS.md / .cursorrules files. Use when evaluating tool trade-offs or answering "how is Nomos different from X". Do NOT use when searching general Handbook tutorials (use search_nomos_corpus instead).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
diagnose_nomos_errorResolve any Nomos ERR_* failure code, TC-AGT-* vector, or nomos verify gate rejection into its root cause and non-bypassing 1-turn AST fix.No findings
Why it is in this group
- The description's first verb is "resolve": a word for reading.
Description, as the server wrote it Resolve any Nomos ERR_* failure code, TC-AGT-* vector, or nomos verify gate rejection into its root cause and non-bypassing 1-turn AST fix. Use when troubleshooting a concrete verify failure or pre-commit hook error. Do NOT use when browsing the full catalog of 42 gates by Law or category without an error (use inspect_dod_gates instead).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
inspect_dod_gatesList and filter the 42 compiled Go and Tree-sitter AST Definition of Done quality gates, 7 Canonical Laws, and sandbox rules.No findings
Why it is in this group
- The name "inspect_dod_gates" says "inspect": a word for reading.
Description, as the server wrote it List and filter the 42 compiled Go and Tree-sitter AST Definition of Done quality gates, 7 Canonical Laws, and sandbox rules. Use when browsing gate invariants by G-* ID, Law 1..7, or category. Do NOT use when troubleshooting a raw verify error log or ERR_* failure (use diagnose_nomos_error instead).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_nomos_corpusSearch Nomos Engineering Handbook chapters, Empirical Field Dispatches, Open-Core Architecture Specs, and CLI reference by keyword.No findings
Why it is in this group
- The name "search_nomos_corpus" says "search": a word for reading.
Description, as the server wrote it Search Nomos Engineering Handbook chapters, Empirical Field Dispatches, Open-Core Architecture Specs, and CLI reference by keyword. Use when looking up conceptual architecture, empirical benchmarks, or CLI flags. Do NOT use when inspecting a specific G-* gate or ERR_* code (use inspect_dod_gates or diagnose_nomos_error instead) or comparing external tools (use compare_governance_approaches instead).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://sophialabs.ca/mcp: tools/list returned 4 tools to an anonymous client, including recommend_adoption_plan (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "recommend_adoption_plan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
- Warnxray_github_repo
The server marks "xray_github_repo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "execute": a word for a change.
The server marks "scaffold_nomos_config" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 changed.~7 changedView diff
- Changed:compare_governance_approachesOnly readstitledescriptioninputSchema
- Changed:diagnose_nomos_errorOnly readsdescriptioninputSchema
- Changed:inspect_dod_gatesOnly readstitledescriptioninputSchema
- Changed:recommend_adoption_planChanges thingstitledescriptioninputSchema
- Changed:scaffold_nomos_configChanges thingsdescriptioninputSchema
- Changed:search_nomos_corpusOnly readstitledescriptioninputSchema
- Changed:xray_github_repoChanges thingstitledescriptioninputSchema
Tools3 added.+3 addedView diff
- Added:diagnose_nomos_errorOnly reads
- Added:scaffold_nomos_configChanges things
- Added:xray_github_repoChanges things
Install
Pinned to version 4.29.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http nomos https://sophialabs.ca/mcpclaude mcp add --transport http nomos https://sophialabs.ca/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nomos__search_nomos_corpus",
"mcp__nomos__inspect_dod_gates",
"mcp__nomos__compare_governance_approaches",
"mcp__nomos__diagnose_nomos_error"
],
"ask": [
"mcp__nomos__recommend_adoption_plan",
"mcp__nomos__xray_github_repo",
"mcp__nomos__scaffold_nomos_config"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nomos. Review it before you use it.
Capability tags behind 2 rules
- mcp__nomos__compare_governance_approaches private-data, untrusted-input
- mcp__nomos__xray_github_repo untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.mgantlett/nomos/verify?hash=5956e19bf017d57246e5368c2768cb43b571e8ca7ff7439ea27d70a8c09584d2" | jq -e '.changed == false'Pinned hash 5956e19bf017, from Nov 21, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.mgantlett/nomos/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.mgantlett/nomos)Source: MCP Registry · repository. Synced Nov 21, 2026, 03:17 UTC.
Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server have?
- 7 tools: 3 write, 4 read. recommend_adoption_plan, xray_github_repo, scaffold_nomos_config, search_nomos_corpus, inspect_dod_gates, compare_governance_approaches and diagnose_nomos_error.
Does the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Nomos - Deterministic Git & AST Governance for AI Coding Agents MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.