M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
H

Hyper MCP

Community
A fast, secure MCP server that extends its capabilities through WebAssembly plugins.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #26 of 438
Stars
★ 882 Very popular
Transport
stdio (local process)
Runtime
Prebuilt binary · Rust · Docker
Credentials
No credential needed
License
Apache-2.0
Last commit
Tools
3
67FMRS · C

hyper-mcp is an innovative MCP server that uses WebAssembly plugins for high extensibility. It is secure, lightweight, and supports multiple clients. The main limitations are stdio-only transport and the requirement for cosign to load OCI plugins. Overall, it is well-suited for developers who want to customize and expand AI tooling.

Strongest · Documentation 16/20 Weakest · Reliability 11/20

Reliability
11/20
Security and permissions
13/20
Maintenance
15/20
Documentation
16/20
Setup experience
12/20
Why each score
Reliability 11/20
The server provides stdio transport and describes startup in README. No actual tests or CI config were checked, so reliability cannot be confirmed from static evidence. Happy path seems plausible, but lack of tests and edge-case handling details prevents score above 12.
Security and permissions 13/20
The server has security design: WASM sandboxing, signature verification via cosign, configurable resource limits and network allowlists. It offers an option to skip signature verification but warns against it. No malware or overreach observed. Least privilege and confirmation are partially clear, but some aspects rely on external config and tools, so deduction.
Maintenance 15/20
The repository appears actively maintained: multiple releases, many plugin repos, and community engagement. License is Apache-2.0. No specific evidence of dependency updates or security response, but overall activity is high.
Documentation 16/20
Documentation is comprehensive: README with installation, RUNTIME_CONFIG.md, BUILT_IN_TOOLS.md, SKIP_TOOLS_GUIDE.md, CREATING_PLUGINS.md, and TEMPLATES.md. Covers installation, config, troubleshooting, security, and plugin development. Missing detailed API parameter listings, but overall excellent.
Setup experience 12/20
Installation steps are clear: pre-built binaries, Homebrew, cargo, and MCP bundle for Claude Desktop. Config examples provided. External dependency (cosign) needed for OCI plugins but optional. Client config examples (Cursor, Claude Code) exist. Deduct for manual steps and cosign requirement, so below 15.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the network

Best for

  • Developers who need highly extensible and secure AI services with the flexibility to write plugins in multiple languages.
  • Teams that want to distribute and manage plugins via OCI registries.
  • Enterprise applications requiring sandboxing and resource limits.

Not for

  • Clients that require HTTP transports (like SSE or streamable-http), since hyper-mcp defaults to stdio only.
  • Users who prefer not to install cosign and still load OCI plugins (unless they set insecure_skip_signature).
  • Users who need specific built-in tools (e.g., database operations) without wanting to configure plugins themselves.

Required permissions

  • Read config files (for plugin configuration).
  • Execute cosign CLI to verify OCI plugin signatures.
  • Network access (to download plugins or for plugin runtime, e.g., allowed hosts).
  • Filesystem access (for local file plugins or logs).
  • Environment variables (e.g., RUST_LOG, HYPER_MCP_LOG_PATH, HYPER_MCP_INSECURE_SKIP_SIGNATURE).

Risks and side effects

  • Loading malicious or unverified plugins could compromise the system or leak data, though signature verification and sandboxing mitigate risks.
  • OCI signature verification depends on cosign; skipping it reduces security.
  • Misconfiguring plugins may allow them to access unauthorized network or filesystem resources.

Setup

Before you start

Runtime：Prebuilt binary · Rust · Docker

Other optional settings (3)
HYPER_MCP_INSECURE_SKIP_SIGNATURE optional Set to true to skip cosign signature verification for OCI plugins; for testing only, not recommended in production.
HYPER_MCP_LOG_PATH optional Custom log directory path overriding the default log location.
RUST_LOG optional Controls log verbosity (info, debug, warn); use debug for troubleshooting.
  1. Install prerequisites: cosign (required for loading plugins from OCI registries with signature verification).
  2. Install hyper-mcp via Homebrew (brew install hyper-mcp or brew install hyper-mcp-rs/tap/hyper-mcp), via cargo (cargo install hyper-mcp), or download a pre-built binary from GitHub Releases.
  3. Create a config file (e.g., ~/.config/hyper-mcp/config.json) specifying the WASM plugins to load.
  4. Start the server from the command line: hyper-mcp.
claude_desktop_config.json 
{
  "mcpServers": {
    "hyper-mcp": {
      "command": "/path/to/hyper-mcp"
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "hyper-mcp": {
      "command": "/path/to/hyper-mcp"
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add hyper-mcp -- /path/to/hyper-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Start hyper-mcp with a config file, connect from your client (e.g. Claude Desktop or Cursor), and confirm the hyper_mcp-list_plugins tool appears; calling it should return the plugins configured in config..

Troubleshooting

  1. Ensure cosign is installed and in PATH, otherwise loading OCI plugins will fail.
  2. Check that the config file path is correct and the JSON is valid.
  3. Use `RUST_LOG=debug hyper-mcp` to get verbose logs for troubleshooting.
  4. If log file location is not as expected, verify the HYPER_MCP_LOG_PATH environment variable.

Things to try

Once connected, you can ask your AI assistant things like:

  • List all currently loaded plugins on the hyper-mcp server
  • Load the time plugin from oci://ghcr.io/hyper-mcp-rs/time-plugin:latest
  • Unload the qr_code plugin
  • Use the hash plugin to compute the SHA-256 of a string

Tools 3

hyper_mcp-list_plugins read-only
Lists all loaded plugins.
hyper_mcp-load_plugin writes
Dynamically loads a plugin at runtime.
hyper_mcp-unload_plugin writes
Dynamically unloads a plugin at runtime.

Use cases

Add AI capabilities to applications such as Claude Desktop, Cursor IDE, and other MCP-compatible apps.
Extend the MCP server with custom WebAssembly plugins for tasks like time queries, QR code generation, hashing, IP lookup, web fetching, and more.
Deploy lightweight AI services in resource-constrained environments.

Supported clients

Claude Desktop
Cursor
Claude Code

Listed from the project's documentation, not tested by this site.

Overview

hyper-mcp is a fast and secure MCP server that extends its capabilities through WebAssembly plugins. It allows writing plugins in any language that compiles to WebAssembly, and distributing them via standard OCI registries (like Docker Hub). Built on Extism for robust plugin support, it provides sandboxing to limit network, filesystem, and memory access. It supports the stdio transport protocol, is lightweight enough for resource-constrained environments, and can be deployed anywhere: serverless, edge, mobile, IoT. Dynamic plugin loading/unloading and tool name prefixing are supported to prevent collisions.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision fb2b24fbbe66 Data synced 2026-10-12 Read the FMRS scoring method