Skip to content

Zoeb Nomi MCP server

io.github.zoeb-nomi/zoebnomizoeb-nomistreamable-httpv0.1.0Scanned

Checks RAG citations against their sources (CrossSource method), plus claim checks. Read-only, free.

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No 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.
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 Zoeb Nomi MCP server can do

The Zoeb Nomi MCP server is published by the GitHub account zoeb-nomi. It has 3 tools. It can create or change data (3 tools: check_citations, verify_claim and fit_to_role), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.1.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.

3 tools

Changes things 3Claude Code: ask
  • check_citationsCheck whether each inline citation in an answer is supported by the source it points to, using CrossSource's method and failure taxonomy (supported, right_doc_wrong_passage, wrong_…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 each inline citation in an answer is supported by the source it points to, using CrossSource's method and failure taxonomy (supported, right_doc_wrong_passage, wrong_document, unsupported_claim). Cites to ids not in `sources` and citations where another passage clearly covers the claim are decided deterministically. Everything else returns needs_judgment with the CrossSource judge prompt to apply. Set use_client_model to have your client model judge those, where the client supports MCP sampling.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • fit_to_roleMap a job description to Zoeb Nomi's public work (zoebnomi.com) with quoted evidence, and list requirements with no public evidence as gaps.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
    Map a job description to Zoeb Nomi's public work (zoebnomi.com) with quoted evidence, and list requirements with no public evidence as gaps. Never answers compensation, availability, location or work authorization.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_claimCheck a claim or number about Zoeb Nomi against what zoebnomi.com states.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 a claim or number about Zoeb Nomi against what zoebnomi.com states. Returns found, number_mismatch or not_found, with the site quote, source URL, evidence link, n and date where the site gives them. Use the returned quote, not your own paraphrase. A word lookup: it cannot see negation, so read the quote.

    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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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 21, 2026, 19:20 UTC, unchanged since Nov 21, 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
3
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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zoebnomi.com/mcp: tools/list returned 3 tools to an anonymous client, including check_citations (write), verify_claim (write), fit_to_role (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http zoebnomi https://mcp.zoebnomi.com/mcp
claude mcp add --transport http zoebnomi https://mcp.zoebnomi.com/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": [],
    "ask": [
      "mcp__zoebnomi__check_citations",
      "mcp__zoebnomi__verify_claim",
      "mcp__zoebnomi__fit_to_role"
    ],
    "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 zoebnomi. Review it before you use it.

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.zoeb-nomi/zoebnomi/verify?hash=9c15820eec5448507b8061b8f97a2b983c799b957f60530ac50ff6caf0502200" | jq -e '.changed == false'

Pinned hash 9c15820eec54, from Nov 20, 2026, 18: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.zoeb-nomi/zoebnomi/changes.xml

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

Badge

Anlyon Radar badge for io.github.zoeb-nomi/zoebnomi
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.zoeb-nomi/zoebnomi.svg)](https://radar.anlyon.com/servers/io.github.zoeb-nomi/zoebnomi)

Source: MCP Registry · repository. Synced Nov 20, 2026, 19:17 UTC.

Zoeb Nomi MCP server: questions and answers

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

Is the Zoeb Nomi MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 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 Zoeb Nomi MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Zoeb Nomi 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 Zoeb Nomi MCP server have?

3 tools: 3 write. check_citations, verify_claim and fit_to_role.

Does the Zoeb Nomi MCP server need sign-in or OAuth?

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

Does the Zoeb Nomi MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Zoeb Nomi MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.