mcp-registry/com.nimcoffee/nimcoffee · v4.0.3
As of 2026-10-18 02:00 UTC, the Nimcoffee MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 minutes.
Order freshly self-roasted specialty coffee from NiMCoffee, a coffee roaster in Fuzhou, China.
Claude Code
claude mcp add --transport http nimcoffee-mcp-server https://mcp.nimcoffee.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"nimcoffee-mcp-server": {
"type": "http",
"url": "https://mcp.nimcoffee.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
16 of 16 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
Handshake + tools/list takes ~3,309 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.nimcoffee%2Fnimcoffee/fixes
{
"name": "cancel_order",
"description": "Cancel a pending order.",
"inputSchema": {
"type": "object",
"required": [
"order_id"
],
"properties": {
"token": {
"type": "string",
"default": "",
"description": "User auth token (required)"
},
"order_id": {
"type": "integer",
"description": "Order ID to cancel"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
},
"title": "Cancel Order"
}{
"name": "check_payment_status",
"description": "Check if an order has been paid.",
"inputSchema": {
"type": "object",
"required": [
"order_id"
],
"properties": {
"token": {
"type": "string",
"default": "",
"description": "User auth token"
},
"order_id": {
"type": "integer",
"description": "Order ID to check"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Check Payment Status"
}{
"name": "create_order",
"description": "Create an order for a NiMCoffee product.",
"inputSchema": {
"type": "object",
"required": [
"product_id"
],
"properties": {
"token": {
"type": "string",
"default": "",
"description": "User auth token (required)"
},
"quantity": {
"type": "integer",
"default": 1,
"description": "Number of units (default 1)"
},
"product_id": {
"type": "integer",
"description": "Product ID to order"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create Order"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.nimcoffee/nimcoffee"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.nimcoffee/nimcoffee"}) over MCP.
search_products ~158 tokenscreate_order ~117 tokenslist_orders ~114 tokensget_payment_qrcode ~106 tokensverify_and_bind ~101 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.nimcoffee%2Fnimcoffee?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.nimcoffee%2Fnimcoffee?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nimcoffee%2Fnimcoffee.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nimcoffee%2Fnimcoffee.svg :target: https://glimind.com/server/mcp-registry%2Fcom.nimcoffee%2Fnimcoffee?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7aa8873f0d950ccc…, first seen 2026-10-17, included at leaf 9723 of 19,652. Version history · verify what your client received.
Compare: most reliable ecommerce servers · most reliable payments servers · most reliable finance servers · most reliable account servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 02:00 UTC, the Nimcoffee MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 minutes.
Nimcoffee MCP server advertises 16 tools, including cancel_order, check_payment_status, create_order, get_my_coupons, get_my_membership.
Point your MCP client at this streamable-http endpoint: https://mcp.nimcoffee.com/mcp
Glimind scanned all 16 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.