Skip to content

NOMOS MCP server

com.nomosprotocol/nomosnomosprotocol.comstreamable-httpv1.6.1Scanned

Ask a sealed authority whether an action may proceed. Answers are deterministic and citable.

7 tools: 5 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 5 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

5 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.
Govern this server →

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 MCP server can do

The NOMOS MCP server is published by nomosprotocol.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (5 tools: verify_decision, generate_governance, ask_authority, ask_by_context and 1 more), but cannot delete data. 2 tools only read.

1 tool reads private data (detect_contradictions); 1 tool brings in text other people can write (ask_by_context).

The fixed checks matched 1 finding (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 15, 2026, version 1.6.1.

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 5Claude Code: ask
  • ask_authorityQuery a published authority on the NOMOS Exchange marketplace — a different system from verify_decision's own sealed policies.1 finding

    Why it is in this group

    • The description's first verb is "query": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "ask_authority" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Query a published authority on the NOMOS Exchange marketplace — a different system from verify_decision's own sealed policies. Every public authority (e.g. eu-ai-act.nomos) is queryable with no key. Returns the authority's own verdict (AUTHORIZED/DENIED/ESCALATED), the exact rule and reason, and a permanent, cryptographically-bound transcript (query_id + url) — replayable evidence, not just a reply. Nothing is invented or paraphrased: the verdict is the authority's sealed rules evaluated against your inputs. The default response is a short, curated summary (verdict, matched rule, source citation when the artifact has one, transparency/completeness disclosures, transcript link) — not the full rule-by-rule evaluation trace. Set include_evaluation_trace: true to get that complete diagnostic record when you or the user actually need it.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ask_by_contextAsk whether an action is allowed WITHOUT choosing the law yourself (NOMOS-SPEC-014).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Ask whether an action is allowed WITHOUT choosing the law yourself (NOMOS-SPEC-014). Describe where the act happens and who it involves; NOMOS works out from its signed registrar log which laws govern it, asks every one, and combines strictly: any deny denies, a yes needs every law. Prefer this over ask_authority whenever you do not already know which law applies: naming one law leaves out the others. Each law's own answer is a permanent, signed transcript (members[].query_id). If a fact that decides which law applies is missing, the answer is INSUFFICIENT_DATA with open_facts naming it: ask the user, never guess. A place the registrar does not cover is answered INSUFFICIENT_DATA, never as permission; say so plainly. Relay `coverage`: the registrar lists only its own laws, so other law may also apply.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: true
  • generate_governanceConvert one or more policy documents into a sealed NOMOS governance artifact (.nomos).No findings

    Why it is in this group

    • The name "generate_governance" says "generate": a word for a change.
    Description, as the server wrote it
    Convert one or more policy documents into a sealed NOMOS governance artifact (.nomos). Extracts executable rules using Claude, detects contradictions between rules, computes an Autonomy Readiness Index (ARI) score (0–1), and cryptographically seals the result. Returns an artifact_id you can use with verify_decision immediately. Optionally accepts historical behavioral decision logs to add a behavioral evidence layer and reach CERTIFIED confidence tier.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: false
  • request_authorityAsk for an authority (a law, regulation, standard or policy) to be added to the NOMOS Exchange when find_authority finds nothing.No findings

    Why it is in this group

    • The name "request_authority" says "request": a word for a change.
    Description, as the server wrote it
    Ask for an authority (a law, regulation, standard or policy) to be added to the NOMOS Exchange when find_authority finds nothing. Requests are public and ranked by how many asked; they decide what is compiled next. Repeated requests from one caller count once. This never creates an authority: only its issuer, or NOMOS compiling the public text, can.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_decisionCheck whether an AI decision is allowed, denied, or needs escalation according to a sealed NOMOS governance artifact.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
    Check whether an AI decision is allowed, denied, or needs escalation according to a sealed NOMOS governance artifact. Always returns `allowed` (boolean) — that field is safe to read regardless of which artifact type answered. The rest of the shape genuinely differs by artifact type, because it proxies two different underlying endpoints: pub_ demo artifacts return a flat shape (`outcome`: auto_approved/auto_rejected/escalated, `rule_applied`, `rule_reference`, flat `confidence` and `audit_hash`); your own sealed artifacts from Studio return a nested shape (`verdict`: approved/rejected/escalated, a nested `rule` object, and nested `confidence`/`audit`/`performance` objects). See outputSchema for both exact shapes — do not assume one without checking which kind of artifact_id was passed. Use artifact IDs starting with pub_ for public demo artifacts that require no API key: pub_lending_v1 (loan approval), pub_refund_v1 (refund policy), pub_fraud_v1 (fraud detection), pub_hr_leave_v1 (HR leave approval), pub_kyc_v1 (KYC/identity).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • detect_contradictionsAnalyze policy documents (and optional behavioral decision logs) to detect contradictions, hidden rules, and gaps between declared policy and observed behavior.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "analyze": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "analyze" and "document": it reads documents.
    Description, as the server wrote it
    Analyze policy documents (and optional behavioral decision logs) to detect contradictions, hidden rules, and gaps between declared policy and observed behavior. Stateless — no artifact is created and nothing is persisted. Returns contradictions of three types: rule_collision (two rules that apply to the same case with different decisions where the policy does not settle it soundly, each with that case and what the policy would do), ghost_term (an undefined standard such as "reasonable" in a rule's own text), and layer_divergence (a policy rule and a rule of practice that one case meets with different decisions); with behavioral logs, policy_gaps measured from the decisions.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • find_authorityFind which published authorities on the NOMOS Exchange govern something you are about to do, from a plain description (e.g.No findings

    Why it is in this group

    • The name "find_authority" says "find": a word for reading.
    Description, as the server wrote it
    Find which published authorities on the NOMOS Exchange govern something you are about to do, from a plain description (e.g. "deploy a recruitment model in the EU"). No name needed. Returns the matching authorities ranked, and for each the facts it reads that match your description (what to pass to ask_authority as inputs) and its most relevant rules with where they come from in the source. Also returns authorities others have requested that are not listed yet. Matches by words and by meaning (a small multilingual model on the server, so questions in Arabic and other languages work); it only chooses what to ask, never a verdict. Call this before ask_authority when you do not know the authority's name.

    Annotations the server declares

    • readOnlyHint: true
    • 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 write1
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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 15, 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
5
Protocol version
2025-06-18
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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.nomosprotocol.com/api/mcp: tools/list returned 7 tools to an anonymous client, including verify_decision (write), generate_governance (write), ask_authority (write), ask_by_context (write), request_authority (write)

    What this check looks for

Posture changes

  1. Nov 15, 2026
    • Tools that change things, listed without credentials: 4 to 5

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "ask_authority" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "query": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
    • Tools that change things, listed without credentials: 4 to 5
  3. Tools3 added, 3 changed.+3 added~3 changedView diff

Install

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

claude mcp add --transport http nomos https://www.nomosprotocol.com/api/mcp
claude mcp add --transport http nomos https://www.nomosprotocol.com/api/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nomos__detect_contradictions",
      "mcp__nomos__find_authority"
    ],
    "ask": [
      "mcp__nomos__verify_decision",
      "mcp__nomos__generate_governance",
      "mcp__nomos__ask_authority",
      "mcp__nomos__ask_by_context",
      "mcp__nomos__request_authority"
    ],
    "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__detect_contradictions private-data
  • mcp__nomos__ask_by_context 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/com.nomosprotocol/nomos/verify?hash=a39d902081c866aaf8456a3a9f8e6c78af7268f87990f157af85d832c99624ce" | jq -e '.changed == false'

Pinned hash a39d902081c8, from Nov 15, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.nomosprotocol/nomos/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.nomosprotocol/nomos
[![Anlyon Radar](https://radar.anlyon.com/badge/com.nomosprotocol/nomos.svg)](https://radar.anlyon.com/servers/com.nomosprotocol/nomos)

Source: MCP Registry. Synced Nov 15, 2026, 18:17 UTC.

NOMOS MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NOMOS MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 1 finding 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 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 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 MCP server have?

7 tools: 5 write, 2 read. verify_decision, generate_governance, ask_authority, ask_by_context, request_authority, detect_contradictions and find_authority.

Does the NOMOS MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the NOMOS 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 MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.