Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

nz.coffeeaddict/coffee-addict

REMOTE · COFFEEADDICT.NZ · SCANNED SEP 27

Every bag of specialty coffee on sale in New Zealand, re-read nightly from each roaster's shop.

Available components

+3 this week 72 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 369 tokens (~123/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the nz.coffeeaddict/coffee-addict MCP server?

nz.coffeeaddict/coffee-addict is a hosted endpoint at https://coffeeaddict.nz/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 · coffeeaddict.nz

# add to Claude Code
claude mcp add --transport http nz-coffeeaddict-coffee-addict 'https://coffeeaddict.nz/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "nz-coffeeaddict-coffee-addict": {
      "url": "https://coffeeaddict.nz/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nz-coffeeaddict-coffee-addict": {
      "type": "http",
      "url": "https://coffeeaddict.nz/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nz-coffeeaddict-coffee-addict]
url = "https://coffeeaddict.nz/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nz-coffeeaddict-coffee-addict": {
      "type": "remote",
      "url": "https://coffeeaddict.nz/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nz-coffeeaddict-coffee-addict --url 'https://coffeeaddict.nz/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nz-coffeeaddict-coffee-addict:
    url: "https://coffeeaddict.nz/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nz-coffeeaddict-coffee-addict": {
      "Transport": "http",
      "Url": "https://coffeeaddict.nz/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nz-coffeeaddict-coffee-addict -t streamable-http -u 'https://coffeeaddict.nz/mcp'
// mcp.json
{
  "mcpServers": {
    "nz-coffeeaddict-coffee-addict": {
      "type": "http",
      "url": "https://coffeeaddict.nz/mcp"
    }
  }
}

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

Changelog

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.

  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 27 Sept 2026 · Probed https://coffeeaddict.nz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=coffeeaddict.nz CN=WE1,O=Google Trust Services,C=US 20 Aug 2026 18 Nov 2026 ECDSA 256 ECDSA-SHA256 bd0d3f6662173227136b8991aa7897b2
SANs: coffeeaddict.nz
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 coffeeaddict.nz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
nz. present 38240, 62081 8, 8 Verified
coffeeaddict.nz. absent 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://coffeeaddict.nz/mcp Verified 200
http (plaintext) http://coffeeaddict.nz/mcp HTTPS enforced 301 https://coffeeaddict.nz/mcp
MCP tools · 3 exposed · ~306 tokens

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 →

Tool Tokens
best_deals ~64

Today's price cuts, new arrivals and cheapest bags per 100g across New Zealand specialty coffee. Every row carries the reason it is on the list, and an empty list carries the reason it is empty.

NameTypeReqDescription
kindstring––
limitinteger––

No output schema declared.

No examples provided.

roaster_info ~89

The New Zealand specialty roasters we track: how many bags each has, their cheapest per 100g, their published shipping terms and where they roast. Omit `roaster` for all of them.

NameTypeReqDescription
include_beansboolean–Also return that roaster's shelf, up to 200 bags.
roasterstring–Name or slug. Omit for all.

No output schema declared.

No examples provided.

search_beans ~153

Search every bag of specialty coffee on sale in New Zealand. Filter by free text (name, roaster, origin, tasting notes), origin, roast style, roaster, price and stock. Results are cheapest per 100g first.

NameTypeReqDescription
in_stock_onlyboolean––
limitinteger––
max_price_nzdnumber––
max_price_per_100gnumber––
originstring–Country or region, e.g. 'Ethiopia'.
querystring–Free text: name, roaster, origin or tasting note.
roast_stylestring––
roasterstring–Roaster name or slug.

No output schema declared.

No examples provided.

Common questions

What is the nz.coffeeaddict/coffee-addict MCP server?

nz.coffeeaddict/coffee-addict is an MCP server listed in the public MCP registry as nz.coffeeaddict/coffee-addict. Every bag of specialty coffee on sale in New Zealand, re-read nightly from each roaster's shop. This page covers its hosted endpoint (https://coffeeaddict.nz/mcp).

Is the nz.coffeeaddict/coffee-addict MCP server safe to use?

nz.coffeeaddict/coffee-addict scores 72 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 nz.coffeeaddict/coffee-addict MCP server expose?

nz.coffeeaddict/coffee-addict exposes 3 tools: search_beans, best_deals, roaster_info. Their descriptions and schemas cost roughly 306 tokens of context every time the server is loaded.

Does the nz.coffeeaddict/coffee-addict MCP server require authentication?

No. We connected to nz.coffeeaddict/coffee-addict without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the nz.coffeeaddict/coffee-addict MCP server still maintained?

nz.coffeeaddict/coffee-addict is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.