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

@tryagent/mcp-proxy

v0.0.1

Published

MCP proxy that fronts upstream MCP servers with TryAgent human-in-the-loop governance — no code changes, one config file.

Downloads

14

Readme

@tryagent/mcp-proxy

Human-in-the-loop governance for any MCP-speaking agent — no code changes, one config file. The proxy is an MCP server that fronts your upstream MCP servers and re-exports every tool; mapped tools escalate to TryAgent before they execute.

// tryagent-mcp.json
{
  "upstreams": [
    { "name": "stripe", "command": "npx -y @stripe/mcp" }
  ],
  "policies": {
    "stripe:create_refund": "payments.refund"
  },
  "default": "passthrough"
}

Point your MCP client at the proxy instead of the upstreams:

{
  "mcpServers": {
    "governed": {
      "command": "npx",
      "args": ["-y", "@tryagent/mcp-proxy", "--config", "tryagent-mcp.json"],
      "env": { "TRYAGENT_API_KEY": "ain_live_…" }
    }
  }
}

Behavior

  • Tools are re-exported as <upstream>__<tool> (MCP tool names disallow :); the config's policies keys keep the readable upstream:tool form. Governed tools get a [TryAgent: requires approval under "<policy>"] note appended to their description so the model knows.
  • On a governed tools/call the proxy creates a TryAgent escalation (the tool args become structured evidence — rubric conditions like args.amount > 100 evaluate against them) and honors the platform's mode ladder: a required rubric blocks until a human decides; reviewed / sampled / autonomous come back system-decided immediately, so the call passes through while the decision is logged.
  • Unknown policy keys and agentIds auto-register on first escalate — no dashboard prework.
  • Fail closed: a denial returns an MCP error result and the upstream is never called; if the TryAgent API is unreachable, mapped tools error instead of executing. Set "default": "block" for allowlist-style deployments where unmapped tools are refused too.

Config reference

| Field | Meaning | | --- | --- | | upstreams[].name | Namespace prefix ([A-Za-z0-9_-], no __) | | upstreams[].command | Command to spawn; inline args OK, or use args | | upstreams[].env | Extra env for the upstream process | | policies | "upstream:tool" → TryAgent policy key | | default | passthrough (default) or block | | apiKey / baseUrl | Override TRYAGENT_API_KEY / API base | | waitIntervalMs / waitTimeoutMs | Decision polling knobs |

Requires Node.js >= 20.17.