Buy Me a Coffee (read-only)
NPM · BUYMEACOFFEE-MCP · SCANNED SEP 25
Read your own Buy Me a Coffee supporters, Extras purchases, memberships and totals.
Available components
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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 265 tokens (~66/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Buy Me a Coffee (read-only) MCP server?
Buy Me a Coffee (read-only) runs locally as an npm package, launched with npx -y buymeacoffee-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 · buymeacoffee-mcp
claude mcp add mayeu20-buymeacoffee-mcp -- npx -y buymeacoffee-mcp
{
"mcpServers": {
"mayeu20-buymeacoffee-mcp": {
"command": "npx",
"args": [
"-y",
"buymeacoffee-mcp"
]
}
}
} {
"servers": {
"mayeu20-buymeacoffee-mcp": {
"command": "npx",
"args": [
"-y",
"buymeacoffee-mcp"
]
}
}
} codex mcp add mayeu20-buymeacoffee-mcp -- npx -y buymeacoffee-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mayeu20-buymeacoffee-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"buymeacoffee-mcp"
],
"enabled": true
}
}
} openclaw mcp add mayeu20-buymeacoffee-mcp --command npx --arg -y --arg buymeacoffee-mcp
mcp_servers:
mayeu20-buymeacoffee-mcp:
command: "npx"
args: ["-y", "buymeacoffee-mcp"] {
"McpServers": {
"mayeu20-buymeacoffee-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"buymeacoffee-mcp"
]
}
}
} assistant mcp add mayeu20-buymeacoffee-mcp -t stdio -c npx -a -y buymeacoffee-mcp
{
"mcpServers": {
"mayeu20-buymeacoffee-mcp": {
"command": "npx",
"args": [
"-y",
"buymeacoffee-mcp"
]
}
}
} 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.
- 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 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.
- 21 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +43
- Malware scan: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 14 Sept 26 −40
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.2 functional
- 10 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
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 25 Sept 2026 · Analysed npm/buymeacoffee-mcp@0.1.2
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 →
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 →
list_extra_purchases ~69
List recent Extras purchases with emails redacted by default. Full emails belong to the account owner and should be handled accordingly when include_emails is true.
| Name | Type | Req | Description |
|---|---|---|---|
| include_emails | boolean | – | – |
| limit | integer | – | – |
| max_pages | integer | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
list_subscriptions ~60
Read memberships as supplied by the API, with emails redacted by default. Full emails belong to the account owner and should be handled accordingly when include_emails is true.
| Name | Type | Req | Description |
|---|---|---|---|
| include_emails | boolean | – | – |
| max_pages | integer | – | – |
No output schema declared.
No examples provided.
list_supporters ~73
List recent one-off supporters, newest first, with emails redacted by default. Full emails belong to the account owner and should be handled accordingly when include_emails is true.
| Name | Type | Req | Description |
|---|---|---|---|
| include_emails | boolean | – | – |
| limit | integer | – | – |
| max_pages | integer | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
summary ~63
Total supports and Extras by currency, counting free supports separately and excluding refunds and revoked purchases. Stops after an older page when observed ordering is newest-first, or returns an error if the page cap prevents completion.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| max_pages | integer | – | – |
No output schema declared.
No examples provided.
What is the Buy Me a Coffee (read-only) MCP server?
Buy Me a Coffee (read-only) is an MCP server listed in the public MCP registry as io.github.mayeu20/buymeacoffee-mcp. Read your own Buy Me a Coffee supporters, Extras purchases, memberships and totals. This page covers its npm package (buymeacoffee-mcp).
Is the Buy Me a Coffee (read-only) MCP server safe to use?
Buy Me a Coffee (read-only) scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 Buy Me a Coffee (read-only) MCP server expose?
Buy Me a Coffee (read-only) exposes 4 tools: list_supporters, list_extra_purchases, list_subscriptions, summary. Their descriptions and schemas cost roughly 265 tokens of context every time the server is loaded.
Is the Buy Me a Coffee (read-only) MCP server still maintained?
Buy Me a Coffee (read-only) is still listed as active in the MCP registry. We last reached this channel on 25 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 Buy Me a Coffee (read-only) MCP server under?
Buy Me a Coffee (read-only) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.