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

@interopio/mcp-apps-proxy

v1.0.0

Published

MCP Apps sandbox proxy web component - hosts the MCP Apps sandbox-proxy iframe protocol as a <mcp-apps-proxy> custom element

Readme

@interopio/mcp-apps-proxy

<mcp-apps-proxy> - the MCP Apps sandbox-proxy (per the MCP Apps spec, "Sandbox proxy" section) as an installable web component, instead of a copy-pasted HTML file.

Serve a page that imports this package. In workspace mode, also call IOBrowser()/IODesktop() somewhere on that page - the element discovers and reuses that io instance itself, so you never need to find the element or hand it anything directly:

<script type="module">
    import "@interopio/mcp-apps-proxy";
    import IOBrowser from "@interopio/browser";

    const params = new URLSearchParams(window.location.search);

    if (params.get("mode") === "workspace") {
        await IOBrowser();
    }
</script>

<mcp-apps-proxy></mcp-apps-proxy>

Host apps (e.g. @interopio/ai-web) keep pointing their existing sandboxProxyUrl at wherever you serve this page - nothing changes on the host side. ?mode=workspace on the URL still selects workspace mode, exactly like before.

This package has no dependency on @interopio/browser/@interopio/desktop - it never calls IOBrowser()/IODesktop() itself. In workspace mode it instead discovers the io instance the page already initialized, using the window "Glue42" event handshake that IOBrowser()/IODesktop() wire up internally (see io-connect-agent-init-protocol.md at the repo root for the full protocol). This means:

  • no risk of the proxy running a different io.Connect instance/session than the rest of your app - it reuses whatever the host page already initialized,
  • zero io.Connect runtime code executed for inline-only consumers (never call IOBrowser()/IODesktop() in that page).

See apps/mcp-apps-proxy in this repo for a full reference consumer.