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

@try-maglev/mcp

v0.1.2

Published

Connect an existing MCP agent to Maglev's manufacturing sandbox.

Vulnerabilities

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

Links

Git

Maintainers

sissiwangsissiwang

Keywords

Readme

Maglev MCP

Local manufacturing tools for an existing MCP agent. This first release supports sandbox keys only: capability discovery and inspection, saved quote requests, and project briefs. Node.js >=22.12 is required.

The host keeps its own model, files and user permissions. The connector uses Maglev's existing API and does not start a new agent.

Install

npm install -g @try-maglev/mcp
maglev-mcp --version

Package: @try-maglev/mcp version 0.1.2. The same bytes are available in the versioned archive and its checksum.

If you installed an earlier archive as @maglev/mcp, run npm uninstall -g @maglev/mcp before installing @try-maglev/mcp. Restart the MCP client afterward; its maglev-mcp command and environment settings stay the same.

Configure your local MCP client to launch maglev-mcp over stdio, with MAGLEV_API_KEY supplied through its environment. A GUI application may not inherit the terminal's environment. Use your client's supported secret/environment configuration; do not put a key in chat or a committed project file. See the connection guide for verified client instructions.

Tools

  • get_identity
  • discover_capabilities
  • inspect_capability
  • request_quote
  • list_runs, get_run
  • list_projects, get_project, create_project, update_project

All calls verify sandbox mode. Quote requests require a caller-provided idempotency key; repeat the identical body/key after a lost response. Project creation is not idempotent: list saved projects before creating again. Updating project intake replaces the entire object and has no concurrent-edit revision lock.

Tool results include the API object as structured content and JSON text. API failures set isError and preserve the error code, request ID and safe recovery details. The connector never automatically retries a write. Cancelling a local request does not undo work accepted by the API.

No tool accepts a credential, API URL, arbitrary request path or local file path. The API origin comes from process configuration. Input is bounded by the existing API/CLI limits; API responses above 2 MiB are reported as errors, not silently truncated. Stdio messages are limited to 128 KiB.

Live keys, factory profiles, private/shared knowledge, document actions and delivery tools are excluded pending the reviewed upstream release. This package does not parse native CAD, upload a folder, call suppliers, purchase, certify or ship products.

Development

The root npm run build:mcp copies the reviewed CLI implementation into this package's generated directory. It is the same maintained HTTP/validation source, not a subprocess wrapper. Build before running from source or packing. Tests use synthetic loopback HTTP responses and an actual MCP SDK client; fixture results are not a real supplier or model evaluation.