NiMCoffee 新印象咖啡
REMOTE · MCP.NIMCOFFEE.COM · 2 COMPONENTS · SCANNED OCT 4
Order freshly self-roasted specialty coffee from NiMCoffee, a coffee roaster in Fuzhou, China.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 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 Management97
- Stability observed for 29 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
- 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
How do I install the NiMCoffee 新印象咖啡 MCP server?
NiMCoffee 新印象咖啡 is a hosted endpoint at https://mcp.nimcoffee.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.nimcoffee.com
claude mcp add --transport http com-nimcoffee-nimcoffee 'https://mcp.nimcoffee.com/mcp'
{
"mcpServers": {
"com-nimcoffee-nimcoffee": {
"url": "https://mcp.nimcoffee.com/mcp"
}
}
} {
"servers": {
"com-nimcoffee-nimcoffee": {
"type": "http",
"url": "https://mcp.nimcoffee.com/mcp"
}
}
} [mcp_servers.com-nimcoffee-nimcoffee] url = "https://mcp.nimcoffee.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-nimcoffee-nimcoffee": {
"type": "remote",
"url": "https://mcp.nimcoffee.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-nimcoffee-nimcoffee --url 'https://mcp.nimcoffee.com/mcp' --transport streamable-http
mcp_servers:
com-nimcoffee-nimcoffee:
url: "https://mcp.nimcoffee.com/mcp" {
"McpServers": {
"com-nimcoffee-nimcoffee": {
"Transport": "http",
"Url": "https://mcp.nimcoffee.com/mcp"
}
}
} assistant mcp add com-nimcoffee-nimcoffee -t streamable-http -u 'https://mcp.nimcoffee.com/mcp'
{
"mcpServers": {
"com-nimcoffee-nimcoffee": {
"type": "http",
"url": "https://mcp.nimcoffee.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 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
- 27 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.
- 25 Sept 26 +1
- 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 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.
- 21 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.
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 5 Oct 2026 · Probed https://mcp.nimcoffee.com/mcp
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=YE2,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6a64d41610abb6b0716de5d8256e424d092 |
| SANs: mcp.nimcoffee.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | present | 19718 | 13 | Verified |
| nimcoffee.com. | 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://mcp.nimcoffee.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.nimcoffee.com/mcp | HTTPS enforced | 301 | https://mcp.nimcoffee.com/mcp |
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 →
cancel_order Cancel Order ~37
Cancel a pending order.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Order ID to cancel |
| token | string | – | User auth token (required) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_payment_status Check Payment Status ~39
Check if an order has been paid.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Order ID to check |
| token | string | – | User auth token |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_order Create Order ~56
Create an order for a NiMCoffee product.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | Product ID to order |
| quantity | integer | – | Number of units (default 1) |
| token | string | – | User auth token (required) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_my_coupons Get My Coupons ~26
List user's available coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | User auth token |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_my_membership Get My Membership ~37
Get user's membership info: tier, points, balance, and available coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | User auth token (required) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_order_status Get Order Status ~48
Get the current status of an order (preparation, ready for pickup, etc).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Order ID to check |
| token | string | – | User auth token |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_payment_qrcode Get Payment Qrcode ~55
Get WeChat Pay QR code for an order. Returns a QR code image for user to scan.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Order ID from create_order |
| token | string | – | User auth token (required) |
No output schema declared.
No examples provided.
get_product_detail Get Product Detail ~38
Get detailed information about a specific product.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | Product ID number |
| token | string | – | User auth token |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_recommendations Get Recommendations ~33
Get personalized coffee recommendations based on user preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | User auth token (used for personalization) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_stores Get Stores ~32
List NiMCoffee store locations with addresses and hours.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | User auth token (optional) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_orders List Orders ~57
List user's recent orders.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 5) |
| status | string | – | Filter by status (completed/pending/cancelled). Empty for all. |
| token | string | – | User auth token |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pay_with_balance Pay With Balance ~46
Pay for an order using member balance (no WeChat needed).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Order ID to pay |
| token | string | – | User auth token (required) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reorder Reorder ~39
Reorder a previous order (same items).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Previous order ID to reorder |
| token | string | – | User auth token |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_products Search Products ~110
Search NiMCoffee products by keyword, category, origin, or flavor.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g., "精品咖啡豆", "挂耳咖啡", "咖啡浓缩液") |
| keyword | string | – | Search keyword (e.g., "耶加雪菲", "拿铁", "果酸") |
| limit | integer | – | Max results to return (default 10) |
| token | string | – | User auth token |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_verification_code Send Verification Code ~40
Send SMS verification code to the user's phone number.
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | User's phone number (e.g., 13800138000) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_and_bind Verify And Bind ~47
Verify SMS code and bind the user. Returns a user token for subsequent operations.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | SMS verification code received |
| phone | string | yes | User's phone number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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/mcp).
Is the NiMCoffee 新印象咖啡 MCP server safe to use?
NiMCoffee 新印象咖啡 scores 77 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 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.