npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@myriadcodelabs/mcp-uplink

v1.0.1

Published

Run local MCP servers behind one aggregate endpoint and optionally uplink them to a compatible remote registry.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

myriadcodelabsmyriadcodelabs

Keywords

Readme

MCP Uplink

General-purpose local MCP manager with a loopback aggregate MCP endpoint and optional WebSocket uplink.

Install and run

Requires Node.js 22 or newer.

Install the published CLI:

npm install -g @myriadcodelabs/mcp-uplink
mcp-uplink

Or run from source:

npm ci
npm run build
npm start

Open http://127.0.0.1:8787. Add a STDIO command or a Streamable HTTP MCP endpoint, then start it. HTTP MCPs can include custom request headers such as Authorization or X-API-Key for authenticated endpoints. MCP clients connect to http://127.0.0.1:8787/mcp. The UI and endpoint bind only to 127.0.0.1; the local endpoint has no authentication. /mcp accepts loopback and Chrome/Firefox extension origins. Ordinary website origins remain blocked because they could otherwise invoke local tools.

To install as a local CLI package, run npm pack here, then npm install -g ./myriadcodelabs-mcp-uplink-1.0.0.tgz and mcp-uplink.

Configuration, including MCP environment variables, HTTP headers, and the uplink credential, is stored in ~/.config/mcp-uplink/config.json with owner-only permissions. Set MCP_UPLINK_CONFIG to use another path and MCP_UPLINK_PORT to change the loopback port. Legacy MYRIAD_ADAPTER_CONFIG and MYRIAD_ADAPTER_PORT values remain supported for compatibility. Keep your user account and config file protected.

Remote uplink is optional. On the Remote page, enter a WebSocket URL and credential. The current registry backend accepts an Authorization: Bearer header, sends call frames, and receives register, result, and error frames. Other remotes must support this protocol. Tool names are preserved when unique; duplicate names are prefixed with the source ID.

MCP Uplink manages processes and transport only. It has no local permissions, filtering, or quotas.