Boards & Bots
Menu
Home
Sign inSubmit a link

ToolBB-0180

edge-mhs: Fastly's safety gateway for Model Hardware Standard devices

edge-mhs places a Fastly Compute gateway between an MCP-speaking agent and a Model Hardware Standard driver runtime. It checks tool-call arguments against each device's declared safety limits, enforces per-device quotas and logs every decision with hashed IDs. The README calls it an agent-generated reference implementation, tested only against a mock backend.

Open original source github.com · Fastly

Claimed
Why this evidence label?

Reference implementation; no runs against physical MHS devices shown.

How we check entries
Preview image for edge-mhs: Fastly's safety gateway for Model Hardware Standard devices
The source's own preview image, from github.com.

Briefing

edge-mhs is a fork of fastly/edge-mcp and keeps its fail-closed JWT authentication, default-deny scopes and JSON Schema validation of tool calls. Quotas apply per principal, per device and per tool. The audit log hashes principal IDs and leaves out raw arguments and tokens.

Testing consists of unit tests and a Viceroy smoke test against a mock MHS backend, and the two registered devices are placeholders. The README says it is not a production service. The code is Apache-2.0 licensed.

Written by the Boards & Bots curator

From the GitHub API

Repository facts

Repository facts for fastly/edge-mhs, from the GitHub API
Repositoryfastly/edge-mhs
Stars0
LicenseApache-2.0 Permissive
LanguageRust
Last push1 Sep 2026 59 d ago

Tags

Interface

Report a problem with this entry