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.

NiMCoffee 新印象咖啡

REMOTE · MCP.NIMCOFFEE.COM · 2 COMPONENTS

Order freshly self-roasted specialty coffee from NiMCoffee, a coffee roaster in Fuzhou, China.

0 this week 71 Trust /100

Last scanned (17 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 & Reachability40
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 950 tokens (~59/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (94% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_verification_code" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • 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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 0
    • Stability: pass → 0.97 functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
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 21 Nov 2026 · Probed https://mcp.nimcoffee.com/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.nimcoffee.com CN=YE1,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 638f6ea09b37c7379c3fda8f2047cd3cefd
SANs: mcp.nimcoffee.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.nimcoffee.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
nimcoffee.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

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

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.nimcoffee.com/sse Verified 200
http (plaintext) http://mcp.nimcoffee.com/sse HTTPS enforced 301 https://mcp.nimcoffee.com/sse
MCP tools · 16 exposed · ~740 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
cancel_order ~37

Cancel a pending order.

NameTypeReqDescription
order_idintegeryesOrder ID to cancel
tokenstring–User auth token (required)
NameTypeReqDescription
resultstringyes–

No examples provided.

check_payment_status ~39

Check if an order has been paid.

NameTypeReqDescription
order_idintegeryesOrder ID to check
tokenstring–User auth token
NameTypeReqDescription
resultstringyes–

No examples provided.

create_order ~56

Create an order for a NiMCoffee product.

NameTypeReqDescription
product_idintegeryesProduct ID to order
quantityinteger–Number of units (default 1)
tokenstring–User auth token (required)
NameTypeReqDescription
resultstringyes–

No examples provided.

get_my_coupons ~26

List user's available coupons.

NameTypeReqDescription
tokenstring–User auth token
NameTypeReqDescription
resultstringyes–

No examples provided.

get_my_membership ~37

Get user's membership info: tier, points, balance, and available coupons.

NameTypeReqDescription
tokenstring–User auth token (required)
NameTypeReqDescription
resultstringyes–

No examples provided.

get_order_status ~48

Get the current status of an order (preparation, ready for pickup, etc).

NameTypeReqDescription
order_idintegeryesOrder ID to check
tokenstring–User auth token
NameTypeReqDescription
resultstringyes–

No examples provided.

get_payment_qrcode ~55

Get WeChat Pay QR code for an order. Returns a QR code image for user to scan.

NameTypeReqDescription
order_idintegeryesOrder ID from create_order
tokenstring–User auth token (required)

No output schema declared.

No examples provided.

get_product_detail ~38

Get detailed information about a specific product.

NameTypeReqDescription
product_idintegeryesProduct ID number
tokenstring–User auth token
NameTypeReqDescription
resultstringyes–

No examples provided.

get_recommendations ~33

Get personalized coffee recommendations based on user preferences.

NameTypeReqDescription
tokenstring–User auth token (used for personalization)
NameTypeReqDescription
resultstringyes–

No examples provided.

get_stores ~32

List NiMCoffee store locations with addresses and hours.

NameTypeReqDescription
tokenstring–User auth token (optional)
NameTypeReqDescription
resultstringyes–

No examples provided.

list_orders ~57

List user's recent orders.

NameTypeReqDescription
limitinteger–Max results (default 5)
statusstring–Filter by status (completed/pending/cancelled). Empty for all.
tokenstring–User auth token
NameTypeReqDescription
resultstringyes–

No examples provided.

pay_with_balance ~46

Pay for an order using member balance (no WeChat needed).

NameTypeReqDescription
order_idintegeryesOrder ID to pay
tokenstring–User auth token (required)
NameTypeReqDescription
resultstringyes–

No examples provided.

reorder ~39

Reorder a previous order (same items).

NameTypeReqDescription
order_idintegeryesPrevious order ID to reorder
tokenstring–User auth token
NameTypeReqDescription
resultstringyes–

No examples provided.

search_products ~110

Search NiMCoffee products by keyword, category, origin, or flavor.

NameTypeReqDescription
categorystring–Filter by category (e.g., "精品咖啡豆", "挂耳咖啡", "咖啡浓缩液")
keywordstring–Search keyword (e.g., "耶加雪菲", "拿铁", "果酸")
limitinteger–Max results to return (default 10)
tokenstring–User auth token
NameTypeReqDescription
resultstringyes–

No examples provided.

send_verification_code ~40

Send SMS verification code to the user's phone number.

NameTypeReqDescription
phonestringyesUser's phone number (e.g., 13800138000)
NameTypeReqDescription
resultstringyes–

No examples provided.

verify_and_bind ~47

Verify SMS code and bind the user. Returns a user token for subsequent operations.

NameTypeReqDescription
codestringyesSMS verification code received
phonestringyesUser's phone number
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the NiMCoffee 新印象咖啡 MCP server?

NiMCoffee 新印象咖啡 is a hosted endpoint at https://mcp.nimcoffee.com/sse, 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.nimcoffee.com

# add to Claude Code
claude mcp add --transport http com-nimcoffee-nimcoffee 'https://mcp.nimcoffee.com/sse'
Common questions

What is the NiMCoffee 新印象咖啡 MCP server?

NiMCoffee 新印象咖啡 is an MCP server listed in the public MCP registry as com.nimcoffee/nimcoffee. Order freshly self-roasted specialty coffee from NiMCoffee, a coffee roaster in Fuzhou, China. This page covers its hosted endpoint (https://mcp.nimcoffee.com/sse).

Is the NiMCoffee 新印象咖啡 MCP server safe to use?

NiMCoffee 新印象咖啡 scores 71 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 NiMCoffee 新印象咖啡 MCP server expose?

NiMCoffee 新印象咖啡 exposes 16 tools: send_verification_code, verify_and_bind, search_products, get_product_detail, get_recommendations, and 11 more. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.

Does the NiMCoffee 新印象咖啡 MCP server require authentication?

No. We connected to NiMCoffee 新印象咖啡 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the NiMCoffee 新印象咖啡 MCP server still maintained?

NiMCoffee 新印象咖啡 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 NiMCoffee 新印象咖啡 MCP server?

VerifyMCP ran 12 checks on NiMCoffee 新印象咖啡, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about NiMCoffee 新印象咖啡: Authorization. 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.