Skip to content

Tools keep their labels and safety hints through the gateway

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Aug 11:03
· 13 commits to main since this release
v1.18.0
a50fef5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Every tool behind Hypergate was arriving at your agent stripped of the metadata clients use to decide what needs your approval. This release fixes that and finishes the paperwork for listing Hypergate in Claude's own directories.

Bug fixes

  • A read-only tool no longer looks dangerous to your client. The gateway rebuilt each proxied tool from its name, description and input schema alone, dropping the four other fields an MCP tool carries. Clients read readOnlyHint to decide whether a call can be auto-approved and destructiveHint to warn you before one, so every server behind Hypergate arrived unannotated: safe tools lost their auto-approval and destructive tools lost their warning. Titles, output schemas, icons and hints now all survive the hop.
  • Hypergate's own credential tools say what they do. credentials_list, credential_env and credential_request now carry titles and behavioural hints. credential_env is deliberately not marked read-only: it hands back a live secret, and a client that treated it as read-only could dispense one of your keys without ever asking you.
  • Building the extension works when Homebrew installed Node. npm run build:mcpb died with "could not find npm-cli.js" on a Mac where Homebrew keeps npm under the prefix and Node in a versioned Cellar directory.

New

  • The Claude Desktop extension is signable and carries its icon. npm run build:mcpb -- --sign signs the bundle with a certificate you configure, --self-signed covers a local check, and the archive now bundles the same gate mark the site and the app use, so the install dialog and a directory listing both have an icon to show. Unsigned, Desktop still installs it behind an "unverified" warning.
  • Hypergate can be published to the MCP registry. A server.json describes the hypergated package for mcp-publisher, and the two places the version appears there move with every other version in the repo, so a submission cannot be rejected for disagreeing with itself.
  • Where Hypergate can be listed, written down. docs/listing-submissions.md covers the three directories that are open to a local-first gateway, what each needs, and why the remote Connectors Directory is not one of them: it accepts internet-hosted https:// servers only, and Hypergate serves your own machine.

Install

Download the installer for your platform below. Nothing else needed, not even Node.

Prefer npm? Install from the tarballs attached below: npm install -g hypergate-shell-<os>-<arch>-1.18.0.tgz hypergated-1.18.0.tgz. (hypergated is not on the public registry yet. These are the same packages, and they are what the in-app updater installs.)

Bare hypergate command-line binaries are attached too, and SHA256SUMS is signed with the GPG key at docs/release-signing-key.asc, so you can verify what you downloaded.

Assets 35
Loading