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.

Espresso MCP

NPM · ESPRESSO-MCP · SCANNED SEP 22

Find great espresso cafes worldwide with curated data and transparent quality scoring.

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 859 tokens (~143/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the Espresso MCP server?

Espresso MCP runs locally as an npm package, launched with npx -y espresso-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · espresso-mcp

# add to Claude Code
claude mcp add mattgierhart-espresso-mcp -- npx -y espresso-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mattgierhart-espresso-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "espresso-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mattgierhart-espresso-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "espresso-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mattgierhart-espresso-mcp -- npx -y espresso-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mattgierhart-espresso-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "espresso-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mattgierhart-espresso-mcp --command npx --arg -y --arg espresso-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mattgierhart-espresso-mcp:
    command: "npx"
    args: ["-y", "espresso-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mattgierhart-espresso-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "espresso-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mattgierhart-espresso-mcp -t stdio -c npx -a -y espresso-mcp
// mcp.json
{
  "mcpServers": {
    "mattgierhart-espresso-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "espresso-mcp"
      ]
    }
  }
}
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.

  • 22 Sept 26 +1

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

  • 20 Sept 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.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 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.

  • 10 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
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 22 Sept 2026 · Analysed npm/espresso-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 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
find_espresso_near ~132

Find ranked specialty espresso cafes within a radius of given coordinates. Returns cafes from the curated database sorted by espresso-quality score, with distance and score reasoning for each.

NameTypeReqDescription
latnumberyesLatitude in decimal degrees (-90..90).
limitintegerMaximum number of cafes to return. Default 10.
lonnumberyesLongitude in decimal degrees (-180..180).
min_scorenumberFilter out cafes below this espresso quality score (0-100). Default 50.
radius_kmnumberSearch radius in kilometers. Default 2km.

No output schema declared.

No examples provided.

get_cafe_details ~74

Retrieve a full curated record for a cafe by id, including the espresso-quality score breakdown (per-signal contributions) and a few nearby/related cafes.

NameTypeReqDescription
idstringyesCafe id (slug) — e.g. 'tim-wendelboe-oslo'. Use search_cafes to find ids.

No output schema declared.

No examples provided.

list_anti_patterns ~114

List shops that exemplify what to AVOID when looking for great espresso. Includes mass-market chains (Starbucks, Dunkin', Costa) and 'flavor-led specialty' shops that display third-wave signage but lean heavily on flavored drinks. Each entry shows why it's flagged. Useful as contrast when recommending real specialty cafes, and as regression fixtures for the scoring algorithm.

NameTypeReqDescription
categorystringFilter to a specific anti-pattern category.
limitintegerMaximum number of entries to return. Default 20.

No output schema declared.

No examples provided.

list_great_roasters ~108

List curated specialty coffee roasters from the database, filtered by country and reputation tier. Useful for finding cafes that serve a given roaster's beans, or planning a roaster-focused trip.

NameTypeReqDescription
countrystringFilter by ISO-3166 alpha-2 country code.
limitintegerMaximum number of roasters to return. Default 50.
min_reputationstringMinimum reputation tier. Default: 'notable' (includes all known).

No output schema declared.

No examples provided.

score_cafe ~132

Apply the espresso-quality scoring algorithm to a set of observed signals (no database lookup required). Returns a 0-100 score, tier, per-signal contributions, and reasoning. Use this when you've gathered information about a cafe from a website, photo, or review and want a structured assessment.

NameTypeReqDescription
namestringOptional cafe name (used in reasoning and roaster lookup).
observed_signalsobjectyesSignals observed about the cafe. Omit fields you don't know — unknowns are skipped, not penalized.
source_rankingsarrayAwards / rankings the cafe appears in.

No output schema declared.

No examples provided.

search_cafes ~180

Search the curated specialty coffee cafe database by name, city, country, roaster, and minimum quality score. Returns scored results sorted by espresso-quality score descending.

NameTypeReqDescription
citystringFilter by city name (case-insensitive exact match).
countrystringFilter by ISO-3166 alpha-2 country code (e.g. 'JP', 'DK', 'US').
limitintegerMaximum number of cafes to return. Default 20.
min_scorenumberMinimum espresso-quality score (0-100). Default 0 (no filter).
querystringFree-text query matched against cafe name, city, district, and notes (case-insensitive).
roasterstringFilter to cafes that roast in-house under this name, or serve beans from this roaster.

No output schema declared.

No examples provided.

Common questions

What is the Espresso MCP server?

Espresso MCP is listed in the public MCP registry as io.github.mattgierhart/espresso-mcp. Find great espresso cafes worldwide with curated data and transparent quality scoring. This page covers its npm package (espresso-mcp).

Is the Espresso MCP server safe to use?

Espresso MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 Espresso MCP server expose?

Espresso MCP exposes 6 tools: find_espresso_near, search_cafes, get_cafe_details, score_cafe, list_great_roasters, list_anti_patterns. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.

Is the Espresso MCP server still maintained?

Espresso MCP is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Espresso MCP server under?

Espresso MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.