Hyper Mcp

io.github.tuananhPublished by GitHub account tuananhv1.0.0Updated Oct 27, 2026

📦️ A fast, secure MCP server that extends its capabilities through WebAssembly plugins

VerifiedSTDIODesktop onlyFiles & StorageDeveloper ToolsAI & ML

Overview

AI-generated overview

A local MCP server that loads WebAssembly plugins from OCI registries or files, giving an assistant sandboxed tools such as time, hashing, fetch, SQLite and…

What you can do
  • Load and run WebAssembly plugins configured in a JSON config file, each exposing its own tools to the assistant
  • Use bundled example plugins for time calculations, QR codes, hashing, IP lookup, web fetching and Python evaluation
  • Work with data sources through plugins for SQLite, Qdrant vector search, memory storage, arXiv papers and library documentation lookup
  • Reach developer services through plugins for GitHub, GitLab, Maven, crates.io and Go modules
  • Fetch remote content through plugins for web search, Hacker News, crypto and stock prices
  • Filter or prefix tool names to avoid collisions between plugins
When to use it
Useful when you want one local MCP server whose tool set you assemble yourself from WebAssembly plugins, and you value sandboxed, signed plugin distribution over a fixed built-in feature list. Suited to developers comfortable editing a config file and choosing plugins.
Requirements
Runs as a local process, distributed as an OCI container image (docker.io/tuananh/hyper-mcp). Needs a config file at the platform-specific path listing plugin URLs; plugins are pulled from OCI registries, local files, HTTP(S) or S3. S3 plugin sources require AWS credentials in the environment. Default transport is stdio; SSE and streamable HTTP are optional.
Before you install
Plugins are third-party code: only install ones you trust, and note that loading unsigned OCI plugins requires setting the insecure_skip_signature option or the HYPER_MCP_INSECURE_SKIP_SIGNATURE environment variable, which bypasses signature verification. Plugins such as fetch, fs, sqlite, github and gitlab can read files, run queries or act on remote services; sandbox limits on network, filesystem and memory must be configured per plugin. The README states the project has been transferred to…

Installation

In SourceWeft

  1. Open Hyper Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

hyper-mcp

⚠️ NOTICE: PROJECT TRANSFERRED

This project has been transferred to https://github.com/joseph-wortmann/hyper-mcp

Please refer to the new repository for the latest updates and contributions.

A fast, secure MCP server that extends its capabilities through WebAssembly plugins.

What is it?

hyper-mcp makes it easy to add AI capabilities to your applications. It works with Claude Desktop, Cursor IDE, and other MCP-compatible apps. Write plugins in your favorite language, distribute them through container registries, and run them anywhere - from cloud to edge.

Features

  • Write plugins in any language that compiles to WebAssembly
  • Distribute plugins via standard OCI registries (like Docker Hub)
  • Built on Extism for rock-solid plugin support
  • Sanboxing with WASM: ability to limit network, filesystem, memory access
  • Lightweight enough for resource-constrained environments
  • Support all 3 protocols in the spec: stdio, sse and streamble-http.
  • Deploy anywhere: serverless, edge, mobile, IoT devices
  • Cross-platform compatibility out of the box
  • Support tool name prefix to prevent tool names collision

Security

Built with security-first mindset:

  • Sandboxed plugins that can't access your system without permission
  • Memory-safe execution with resource limits
  • Secure plugin distribution through container registries
  • Fine-grained access control for host functions
  • OCI plugin images are signed at publish time and verified at load time with sigstore.

Getting Started

  1. Create your config file:
    • Linux: $HOME/.config/hyper-mcp/config.json
    • Windows: {FOLDERID_RoamingAppData}. Eg: C:\Users\Alice\AppData\Roaming
    • macOS: $HOME/Library/Application Support/hyper-mcp/config.json
json
{  "plugins": {    "time": {      "url": "oci://ghcr.io/tuananh/time-plugin:latest"    },    "qr_code": {      "url": "oci://ghcr.io/tuananh/qrcode-plugin:latest"    },    "hash": {      "url": "oci://ghcr.io/tuananh/hash-plugin:latest"    },    "myip": {      "url": "oci://ghcr.io/tuananh/myip-plugin:latest",      "runtime_config": {        "allowed_hosts": ["1.1.1.1"]      }    },    "fetch": {      "url": "oci://ghcr.io/tuananh/fetch-plugin:latest",      "runtime_config": {        "allowed_hosts": ["*"],        "memory_limit": "100 MB",      }    }  }}

đź“– For detailed configuration options including authentication setup, runtime configuration, and advanced features, see RUNTIME_CONFIG.md

Supported URL schemes:

  • oci:// - for OCI-compliant registries (like Docker Hub, GitHub Container Registry, etc.)
  • file:// - for local files
  • http:// or https:// - for remote files
  • s3:// - for Amazon S3 objects (requires that you have your AWS credentials set up in the environment)
  1. Start the server:
sh
$ hyper-mcp
  • By default, it will use stdio transport. If you want to use SSE, use flag --transport sse or streamable HTTP with --transport streamable-http.
  • If you want to debug, use RUST_LOG=info.
  • If you're loading unsigned OCI plugin, you need to set insecure_skip_signature flag or env var HYPER_MCP_INSECURE_SKIP_SIGNATURE to true

Using with Cursor IDE

You can configure hyper-mcp either globally for all projects or specifically for individual projects.

  1. For project-scope configuration, create .cursor/mcp.json in your project root:
json
{  "mcpServers": {    "hyper-mcp": {      "command": "/path/to/hyper-mcp"    }  }}
  1. Set up hyper-mcp in Cursor's settings: [cursor mcp]

  2. Start using tools through chat: [cursor mcp chat]

Available Plugins

We maintain several example plugins to get you started:

V1 Plugins

These plugins use the v1 plugin interface. While still supported, new plugins should use the v2 interface.

  • time: Get current time and do time calculations (Rust)
  • qr_code: Generate QR codes (Rust)
  • hash: Generate various types of hashes (Rust)
  • myip: Get your current IP (Rust)
  • fetch: Basic webpage fetching (Rust)
  • crypto_price: Get cryptocurrency prices (Go)
  • fs: File system operations (Rust)
  • github: GitHub plugin (Go)
  • eval_py: Evaluate Python code with RustPython (Rust)
  • arxiv: Search & download arXiv papers (Rust)
  • memory: Let you store & retrieve memory, powered by SQLite (Rust)
  • sqlite: Interact with SQLite (Rust)
  • crates-io: Get crate general information, check crate latest version (Rust)
  • gomodule: Get Go modules info, version (Rust)
  • qdrant: keeping & retrieving memories to Qdrant vector search engine (Rust)
  • gitlab: GitLab plugin (Rust)
  • meme_generator: Meme generator (Rust)
  • context7: Lookup library documentation (Rust)
  • think: Think tool(Rust)
  • maven: Maven plugin (Rust)
  • serper: Serper web search plugin (Rust)

V2 Plugins

These plugins use the v2 plugin interface. New plugins should use this interface.

  • rstime: Get current time and do time calculations (Rust)

Community-built plugins

  • hackernews: This plugin connects to the Hacker News API to fetch the current top stories and display them with their titles, scores, authors, and URLs.
  • release-monitor-id: This plugin retrieves project ID from release-monitoring.org, which helps track versions of released software.
  • yahoo-finance: This plugin connects to the Yahoo Finance API to provide stock prices (OHLCV) based on a company name or ticker symbol.
  • rand16: This plugen generates random 16 bytes buffer and provides it in base64uri format - very usable for symmetric cryptography online.

Documentation

  • Runtime Configuration Guide - Comprehensive guide to configuration options including:
    • Authentication setup (Basic, Token, and Keyring)
    • Plugin runtime configuration
    • Security considerations and best practices
    • Platform-specific keyring setup for macOS, Linux, and Windows
    • Troubleshooting authentication issues
  • Skip Tools Pattern Guide - Comprehensive guide to filtering tools using regex patterns:
    • Pattern syntax and examples
    • Common use cases and best practices
    • Environment-specific filtering strategies
    • Advanced regex techniques
    • Migration and troubleshooting

Creating Plugins

For comprehensive instructions on creating plugins, see CREATING_PLUGINS.md.

License

Apache 2.0

Star History

[Star History Chart]

Source: README.md at commit f3e1aff

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts