Zoeb Nomi
REMOTE · MCP.ZOEBNOMI.COM
Checks RAG citations against their sources (CrossSource method), plus claim checks. Read-only, free.
Available components
Last scanned (22 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 671 tokens (~95/item across 7 items; 3 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.zoebnomi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zoebnomi.com | CN=WE1,O=Google Trust Services,C=US | 20 Nov 2026 | 18 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | fcb284dc8afe2c7e0ec80350944b04dd |
| SANs: zoebnomi.com, mcp.zoebnomi.com, *.mcp.zoebnomi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zoebnomi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| zoebnomi.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zoebnomi.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zoebnomi.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_citations Check citations (CrossSource) ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
fit_to_role Map a job description to public work ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_description | string | yes | The job description text. |
No output schema declared.
No examples provided.
verify_claim Verify a claim about Zoeb Nomi ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The claim to check, e.g. "CrossSource lifted citation precision to 0.994". |
No output schema declared.
No examples provided.
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.
remote · mcp.zoebnomi.com
claude mcp add --transport http zoeb-nomi-zoebnomi 'https://mcp.zoebnomi.com/mcp'
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.