# Zoeb Nomi (remote · mcp.zoebnomi.com)

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

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.zoebnomi.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/zoeb-nomi-zoebnomi/mcp.md), [page](https://verifymcp.io/servers/zoeb-nomi-zoebnomi/mcp)

## Channel facts

- Endpoint: `https://mcp.zoebnomi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 671 tokens (~95/item across 7 items; 3 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Zoeb Nomi MCP server?

Zoeb Nomi is a hosted endpoint at https://mcp.zoebnomi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http zoeb-nomi-zoebnomi 'https://mcp.zoebnomi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "zoeb-nomi-zoebnomi": {
      "url": "https://mcp.zoebnomi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "zoeb-nomi-zoebnomi": {
      "type": "http",
      "url": "https://mcp.zoebnomi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.zoeb-nomi-zoebnomi]
url = "https://mcp.zoebnomi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zoeb-nomi-zoebnomi": {
      "type": "remote",
      "url": "https://mcp.zoebnomi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add zoeb-nomi-zoebnomi --url 'https://mcp.zoebnomi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  zoeb-nomi-zoebnomi:
    url: "https://mcp.zoebnomi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "zoeb-nomi-zoebnomi": {
      "Transport": "http",
      "Url": "https://mcp.zoebnomi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add zoeb-nomi-zoebnomi -t streamable-http -u 'https://mcp.zoebnomi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "zoeb-nomi-zoebnomi": {
      "type": "http",
      "url": "https://mcp.zoebnomi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-20 (score 68)

First indexed and scored.

## MCP tools (3)

### `check_citations` (~203 tokens)

Check citations (CrossSource)

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.

Input parameters:

- `answer` (string, required): The answer text with inline citations like [doc_id:chunk_id] or [source_id].
- `include_judge_prompts` (boolean): Return the judge prompt with each needs_judgment item. Default true.
- `sources` (array, required): Every passage the answering system had available (30 at most).
- `use_client_model` (boolean): Ask the client model (MCP sampling) to judge needs_judgment items. Default false.

### `verify_claim` (~109 tokens)

Verify a claim about Zoeb Nomi

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.

Input parameters:

- `claim` (string, required): The claim to check, e.g. "CrossSource lifted citation precision to 0.994".

### `fit_to_role` (~65 tokens)

Map a job description to public work

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.

Input parameters:

- `job_description` (string, required): The job description text.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/zoeb-nomi-zoebnomi/mcp#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 68

## Common questions

### What is the Zoeb Nomi MCP server?

Zoeb Nomi is an MCP server listed in the public MCP registry as io.github.zoeb-nomi/zoebnomi. Checks RAG citations against their sources (CrossSource method), plus claim checks. Read-only, free. This page covers its hosted endpoint (https://mcp.zoebnomi.com/mcp).

### Is the Zoeb Nomi MCP server safe to use?

Zoeb Nomi scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Zoeb Nomi MCP server expose?

Zoeb Nomi exposes 3 tools: check_citations, verify_claim, fit_to_role. Their descriptions and schemas cost roughly 377 tokens of context every time the server is loaded.

### Does the Zoeb Nomi MCP server require authentication?

No. We connected to Zoeb Nomi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zoeb Nomi MCP server still maintained?

Zoeb Nomi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zoeb Nomi MCP server?

VerifyMCP ran 12 checks on Zoeb Nomi, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Zoeb Nomi: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.zoebnomi.com/mcp
- Repository: https://github.com/zoeb-nomi/zoebnomi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/zoeb-nomi-zoebnomi/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zoeb-nomi-zoebnomi/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/zoeb-nomi-zoebnomi/mcp.json
- HTML version of this page: https://verifymcp.io/servers/zoeb-nomi-zoebnomi/mcp
