NOMOS
com.nomosprotocol/nomosVersion 1.6.0Ask a sealed authority whether an action may proceed. Answers are deterministic and citable.
Status
Responds217 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:08 UTC
- Latency
- 217 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://www.nomosprotocol.com/api/mcpResponds217 msNo sign-in
Claude Code
claude mcp add --transport http nomos https://www.nomosprotocol.com/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: nomos
Remote MCP server URL: https://www.nomosprotocol.com/api/mcpCursor
{
"mcpServers": {
"nomos": {
"url": "https://www.nomosprotocol.com/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"nomos","type":"http","url":"https://www.nomosprotocol.com/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
ask_authorityQuery 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. | Not declared | No | No | No |
ask_by_contextAsk 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. | Not declared | No | No | Yes |
detect_contradictionsAnalyze 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. | Not declared | Yes | Yes | No |
find_authorityFind 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. | Not declared | Yes | Yes | No |
generate_governanceConvert 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. | Not declared | No | No | No |
request_authorityAsk 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. | Not declared | No | Yes | No |
verify_decisionCheck 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). | Not declared | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 14, 2026
- Updated
- Nov 14, 2026
- Repository
- Not given
- Categories
- Uncategorized
- GDPR
- Not declared