io.github.jschoemaker/mcpgo
NPM · @EXFIL/MCPGO · SCANNED SEP 20
Manage your Claude Code MCPs by talking to Claude — list, restart, wrap, and more.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jschoemaker/mcpgo). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 122 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1061 tokens (~96/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_mcp" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jschoemaker/mcpgo MCP server?
io.github.jschoemaker/mcpgo runs locally as an npm package, launched with npx -y @exfil/mcpgo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @exfil/mcpgo
claude mcp add jschoemaker-mcpgo -- npx -y @exfil/mcpgo
{
"mcpServers": {
"jschoemaker-mcpgo": {
"command": "npx",
"args": [
"-y",
"@exfil/mcpgo"
]
}
}
} {
"servers": {
"jschoemaker-mcpgo": {
"command": "npx",
"args": [
"-y",
"@exfil/mcpgo"
]
}
}
} codex mcp add jschoemaker-mcpgo -- npx -y @exfil/mcpgo
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jschoemaker-mcpgo": {
"type": "local",
"command": [
"npx",
"-y",
"@exfil/mcpgo"
],
"enabled": true
}
}
} openclaw mcp add jschoemaker-mcpgo --command npx --arg -y --arg @exfil/mcpgo
mcp_servers:
jschoemaker-mcpgo:
command: "npx"
args: ["-y", "@exfil/mcpgo"] {
"McpServers": {
"jschoemaker-mcpgo": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@exfil/mcpgo"
]
}
}
} assistant mcp add jschoemaker-mcpgo -t stdio -c npx -a -y @exfil/mcpgo
{
"mcpServers": {
"jschoemaker-mcpgo": {
"command": "npx",
"args": [
"-y",
"@exfil/mcpgo"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.83 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@exfil/mcpgo@0.1.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jschoemaker/mcpgo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jschoemaker/mcpgo/.github/workflows/publish.yml@refs/tags/v0.1.6 |
| Rekor log index | 1585421462 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0b034d406b3e58c63c5c4f6f4795f90fa0f1eb844231dbecf72b3ab2be69571f6bc7c93f607a65970f864906bf95ae049822e64ecf8782d8d638bfe93 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_mcp ~272
Add a new MCP server to the user configuration (~/.claude.json).
| Name | Type | Req | Description |
|---|---|---|---|
| allow_footgun_args | boolean | – | Set true to override the safety refusal when args include code-injection flags like -e/--eval on node, -c on python/bash, -Command on pwsh, /c on cmd. |
| allow_footgun_env | boolean | – | Set true to override the safety refusal when env sets a code-injection key like NODE_OPTIONS, LD_PRELOAD, PYTHONSTARTUP, BASH_ENV. |
| allow_shell_metacharacters | boolean | – | Set true to override the safety refusal when 'command' contains shell metacharacters. Use only for genuinely shell-style commands you trust. |
| args | array | – | Arguments to pass to the command |
| command | string | – | Command to run (required for stdio transport) |
| env | object | – | Environment variables to set for the server |
| headers | object | – | HTTP headers (for http/sse transport) |
| mcp_name | string | yes | Name for the new MCP server (alphanumeric, dashes, underscores) |
| transport | string | yes | Transport type: stdio for local process, http/sse for remote server |
| url | string | – | Server URL (required for http/sse transport) |
No output schema declared.
No examples provided.
check_mcp_health ~48
Check the health of an MCP server — whether it is configured, wrapped, and its process is running.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The name of the MCP server to check |
No output schema declared.
No examples provided.
configure_mcp ~160
Update the configuration of an existing MCP server. Merges provided updates into the existing config.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_footgun_args | boolean | – | Set true to override the safety refusal when updates.args include code-injection flags like -e/--eval/-c. |
| allow_footgun_env | boolean | – | Set true to override the safety refusal when updates.env sets a code-injection key like NODE_OPTIONS, LD_PRELOAD, PYTHONSTARTUP. |
| allow_shell_metacharacters | boolean | – | Set true to override the safety refusal when 'updates.command' contains shell metacharacters. |
| mcp_name | string | yes | The name of the MCP server to configure |
| updates | object | yes | Fields to update in the MCP server config |
No output schema declared.
No examples provided.
get_mcp_details ~68
Get the full configuration for a specific MCP server by name.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The name of the MCP server to get details for |
| show_env_values | boolean | – | If true, reveal raw 'env' values. Default false (values shown as '***'). |
No output schema declared.
No examples provided.
list_all_mcps ~101
List all configured MCP servers from ~/.claude.json with their configuration. By default, values inside each server's 'env' field are redacted to '***' so this tool can't be used to exfiltrate API keys stored in MCP env. Pass show_env_values=true to reveal them when you legitimately need them.
| Name | Type | Req | Description |
|---|---|---|---|
| show_env_values | boolean | – | If true, reveal raw 'env' values. Default false (values shown as '***'). |
No output schema declared.
No examples provided.
remove_mcp ~42
Remove an MCP server from the user configuration (~/.claude/mcp.json).
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The name of the MCP server to remove |
No output schema declared.
No examples provided.
restart_codex_mcp_process ~84
Restart a Codex CLI MCP server process. Works reliably only for wrapped MCPs (via wrap_codex_mcp_stdio) by killing the wrapped child PID from its pidfile; otherwise you typically need to restart Codex CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The mcp_servers.<name> entry in ~/.codex/config.toml to restart |
No output schema declared.
No examples provided.
restart_mcp_process ~74
Restart the underlying process for an MCP server by finding and killing its process. For wrapped stdio MCPs (via wrap_mcp_stdio), the wrapper will respawn automatically; otherwise you typically need to restart Claude CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The name of the MCP server whose process should be restarted |
No output schema declared.
No examples provided.
unwrap_mcp_stdio ~50
Unwrap a previously wrapped stdio MCP server, restoring its original command. Requires restarting Claude Code to take effect.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The name of the MCP server to unwrap |
No output schema declared.
No examples provided.
wrap_codex_mcp_stdio ~91
Wrap a Codex CLI stdio MCP server (from ~/.codex/config.toml) so it can be restarted reliably. Rewrites the MCP entry to launch mcpgo's Node wrapper that respawns the original command. Restart Codex CLI to take effect.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The mcp_servers.<name> entry in ~/.codex/config.toml to wrap |
No output schema declared.
No examples provided.
wrap_mcp_stdio ~71
Wrap a stdio MCP server so it can be restarted reliably. Updates ~/.claude.json to launch a Node wrapper that spawns the original command and respawns it when killed. Requires restarting Claude CLI to take effect.
| Name | Type | Req | Description |
|---|---|---|---|
| mcp_name | string | yes | The name of the MCP server to wrap |
No output schema declared.
No examples provided.
What is the io.github.jschoemaker/mcpgo MCP server?
io.github.jschoemaker/mcpgo is an MCP server listed in the public MCP registry as io.github.jschoemaker/mcpgo. Manage your Claude Code MCPs by talking to Claude, list, restart, wrap, and more. This page covers its npm package (@exfil/mcpgo).
Is the io.github.jschoemaker/mcpgo MCP server safe to use?
io.github.jschoemaker/mcpgo scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.jschoemaker/mcpgo MCP server expose?
io.github.jschoemaker/mcpgo exposes 11 tools: list_all_mcps, get_mcp_details, check_mcp_health, restart_mcp_process, restart_codex_mcp_process, and 6 more. Their descriptions and schemas cost roughly 1,061 tokens of context every time the server is loaded.
Is the io.github.jschoemaker/mcpgo MCP server still maintained?
io.github.jschoemaker/mcpgo is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.jschoemaker/mcpgo MCP server under?
io.github.jschoemaker/mcpgo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.