io.github.hadriangateway/platter

MCPcommunity
v2.0.3io.github.hadriangatewayUnknownUpdated 3mo agoGitHub

MCP server exposing Read, Write, Edit, Bash, Glob, Grep, and JS tools over stdio.

Your computer, served on a platter. MCP server that exposes Read, Write, Edit, Bash, Glob, Grep, and JS tools over Stdio and StreamableHTTP transports. Built with Bun, compiles to standalone executables. Designed to be used by browser-based (or any MCP-compatible) agents, like Hadrian, to control a computer. ------|-------------| read | Read file contents with pagination (offset/limit). Detects…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1Forks
3mo agoLast update
Package
Authorio.github.hadriangateway
LicenseUnknown
Version2.0.3
Sourcemcp-registry
GitHubhadriangateway/platter
SBOMCycloneDX 1.6 ↓
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 surface7 tools · 1 privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
CODE…/src/tray/icon-data.tsVery large base64-looking blob in source
EvalsNone
IndexedJun 13, 2026

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

Tools

7 tools · 1 privileged
Statically extracted from the published packagevHEAD · 3mo 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.

readNo description published

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

writeprivilegedNo description published

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

editNo description published

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

bashNo description published

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

globNo description published

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

grepNo description published

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

jsNo description published

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

0 of 7 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

Your computer, served on a platter. MCP server that exposes Read, Write, Edit, Bash, Glob, Grep, and JS tools over Stdio and StreamableHTTP transports. Built with Bun, compiles to standalone executables. Designed to be used by browser-based (or any MCP-compatible) agents, like Hadrian, to control a computer. ------|-------------| read | Read file contents with pagination (offset/limit). Detects image files (JPEG, PNG, GIF, WebP) and returns metadata. Truncates text to 2000 lines or 50KB. |…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

7 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

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.