io.github.ljcl/gaggiuino-mcp

MCPcommunity
v5.0.1io.github.ljclUnknownUpdated 6d agoGitHub

Remote MCP server for your Gaggiuino espresso machine's shots and profiles

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
6d agoLast update
Reads these credentials
  • MCP_OAUTH_SECRETOAuth appoptional

    Signing key for self-issued OAuth access and refresh tokens, at least 32 characters (openssl rand -hex 32). Keep it stable across restarts so clients stay signed in

  • MCP_OAUTH_PASSPHRASE_HASHOAuth appoptional

    scrypt hash of the passphrase you type on the OAuth consent page, in the form scrypt$N$r$p$salt$hash. Required whenever OAuth is enabled. Generate with `bun run hash-passphrase` — never store the…

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.ljcl
LicenseUnknown
Version5.0.1
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface8 tools · 1 privileged
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · 1 privileged
Statically extracted from the published packagevHEAD · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_shot_raw_dataNo description published

This tool published no description. Forge does not invent one.

get_machine_settingsNo description published

This tool published no description. Forge does not invent one.

select_profileNo description published

This tool published no description. Forge does not invent one.

delete_profileprivilegedNo description published

This tool published no description. Forge does not invent one.

get_dial_in_guidanceNo description published

This tool published no description. Forge does not invent one.

view_shot_graphNo description published

This tool published no description. Forge does not invent one.

get_shot_raw_jsonNo description published

This tool published no description. Forge does not invent one.

get_previous_shot_jsonNo description published

This tool published no description. Forge does not invent one.

0 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Remote MCP server for your Gaggiuino espresso machine's shots and profiles

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.