# io.github.jschoemaker/mcpgo

Manage your Claude Code MCPs by talking to Claude — list, restart, wrap, and more.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.1.6
- **Author:** io.github.jschoemaker
- **License:** Unknown
- **npm:** @exfil/mcpgo
- **Source:** https://github.com/jschoemaker/mcpgo
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 114 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** clean
- **Scanned:** 2026-06-13T12:04:27.533Z
- **Version scanned:** 0.1.6
- **CVEs:** none found by OSV at scan time

## Tools

11 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `add_mcp`
- `configure_mcp`
- `get_mcp_details`
- `check_mcp_health`
- `list_all_mcps`
- `remove_mcp`
- `restart_codex_mcp_process`
- `restart_mcp_process`
- `unwrap_mcp_stdio`
- `wrap_codex_mcp_stdio`
- `wrap_mcp_stdio`

## Install

**Verdict: review** — Installable, but 1 thing to check first: The last scan is 114 days old — the evidence behind this verdict is dated.
**Cautions** (coverage gaps and advisories — never blocking)
- The last scan is 114 days old — the evidence behind this verdict is dated.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcpgo\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@exfil/mcpgo\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 36, ceiling 60 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.jschoemaker%2Fmcpgo
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.jschoemaker%2Fmcpgo/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.jschoemaker%2Fmcpgo
- HTML page: https://forgeregistry.com/registry/io.github.jschoemaker%2Fmcpgo
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.