mcpbeat Sign in

NOMOS MCP Server

by nomosprotocol Your server? Claim it
not responding

NOMOS is listed as active in the registry but did not answer our last check. It exposes 6 tools.

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

Uptime history 16 hours of history · worst hour 0%
16 hours agonow
49.1%
Uptime 24h
28 of 57 checks
6
Tools
read from the server
452 ms
Response time
average over 24h
open, no key
Access
streamable-http

NOMOS does not always answer

Over the last week it answered 49.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add nomos --transport http https://www.nomosprotocol.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://www.nomosprotocol.com/api/mcp
~/.codex/config.toml
[mcp_servers.nomos]
url = "https://www.nomosprotocol.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "nomos": {
      "url": "https://www.nomosprotocol.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "nomos": {
      "type": "http",
      "url": "https://www.nomosprotocol.com/api/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ask
ask_authority
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.
authority
find_authority
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.
detect
detect_contradictions
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 contradiction types: threshold_conflicts (numeric rule overlaps), ghost_terms (undefined terms used in rules), role_conflicts (same action allowed by one role, denied by another), rule_collisions (direct logical conflicts), and layer_divergences (policy says X but behavioral data shows Y).
generate
generate_governance
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.
request
request_authority
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.
verify
verify_decision
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).

Endpoints

URLTransportStateLatencyChecked
https://www.nomosprotocol.com/api/mcp streamable-http answering 124 ms 4 min ago

Alternatives to NOMOS

same job, measured the same way
Vizier Guard
by vassiliylakhonin

Deterministic authorization and security guard for AI agent actions with signed receipts.

75 installs/wk local only
Opengate MCP
by nickjlamb

Check whether an AI answer is grounded in its context — deterministic, no LLM judge.

56 installs/wk local only
Syl Pulse
by sylai

Causal analytics: ask a business question, get a deterministic causal answer and charts.

1 tools answering
KATA Research Automation
by dharan1007

Deterministic research automation with live OpenAlex search and reusable workflow programs.

answering
ALEETH Authority MCP
by aleeth

The first MCP governed by ICA. Every action is gated and sealed with a verifiable receipt.

answering
Deepsleuth
by deepsleuth

Deterministic, no-LLM security scanner for MCP servers, plus an inline proxy gate.

129 installs/wk local only
RealEstate-Analytics.ai
by realestate-analytics

Prospect, grade and analyze off- or on-market real estate deals with deterministic, auditable math.

answering
Quant Research MCP
by flawlessbyte

Paper-backed quant trading methods and a deterministic, no-LLM decision helper for serious traders.

103 installs/wk local only

NOMOS — questions

Answers built from our own checks of this server.

What can NOMOS do?
It exposes 6 tools, read directly from the server on our last check. Among them: ask_authority, detect_contradictions, find_authority, generate_governance, request_authority, verify_decision. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is NOMOS working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 57 checks got a reply (49.1%), average response time 452 ms. The bar chart above shows every period we have measured.
The registry lists NOMOS as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect NOMOS?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does NOMOS need an API key?
No. NOMOS completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is NOMOS?
It answers our handshake in 452 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.