front-proxy
NPM · FRONT-PROXY
Map local domains (and HTTPS) to apps on local ports, OS-wide, via /etc/hosts and a reverse proxy.
Available components
Last scanned (55 minutes ago)
Scores higher than 88% of npm servers
Category Cloud Infrastructure
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
- 47 of 136 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to gutomezencio/front-proxy). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 565 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 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
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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +4
- Stability: unverified → 0.30 ▲ functional
- 14 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 34
First indexed and scored.
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 24 Oct 2026 · Analysed npm/front-proxy@0.8.2
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 | gutomezencio/front-proxy |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/gutomezencio/front-proxy/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3150997828 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:707d6a7f6ab5638b257d0311b9f59e12b296f01dc3a53bba2ef8e05b57cb2dab72190347ec784d4934c55dcdc7d7d7944e0b0679c0c44a79898202428 |
Background: How many MCP packages publish verified provenance →
Dependencies 136 packages
| Packages resolved | 136 |
|---|---|
| Stale | 47 |
| 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_host Add host ~100
Map a local domain to an app on a local port, eq. myapp.local → 3000. Saved to the config; call apply_config to use it in the running proxy.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to map, eq.: myapp.local (letters, digits, hyphens and dots) |
| port | number|string | yes | Local port the app listens on, 1-65535 (not 80 or 443) |
No output schema declared.
No examples provided.
apply_config Apply the config ~46
Load the saved config into the running proxy: routes, HTTPS certs and the /etc/hosts block, without restarting it. Needs the proxy running with its admin page (the default).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
generate_certs Generate HTTPS certs ~77
Create locally trusted HTTPS certs with mkcert for one domain, or for every configured domain when none is given. Needs mkcert installed, with its local CA installed once (`mkcert -install`).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Hostname to map, eq.: myapp.local (letters, digits, hyphens and dots) |
No output schema declared.
No examples provided.
list_hosts List hosts ~30
List the configured domains with their local port and HTTPS cert status ("own", "missing" or "default").
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
proxy_status Proxy status ~43
Whether front-proxy is running, whether HTTPS is on, whether saved changes are waiting for apply_config, and whether each app listens on its port ("up"/"down").
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_host Remove host ~58
Remove a domain from the config. Call apply_config to remove it from the running proxy and /etc/hosts.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to map, eq.: myapp.local (letters, digits, hyphens and dots) |
No output schema declared.
No examples provided.
update_host Change a host port ~82
Point a configured domain to another local port. Call apply_config to use it in the running proxy.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to map, eq.: myapp.local (letters, digits, hyphens and dots) |
| port | number|string | yes | Local port the app listens on, 1-65535 (not 80 or 443) |
No output schema declared.
No examples provided.
How do I install the front-proxy MCP server?
front-proxy runs locally as an npm package, launched with npx -y front-proxy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · front-proxy
claude mcp add gutomezencio-front-proxy -- npx -y front-proxy
What is the front-proxy MCP server?
front-proxy is an MCP server listed in the public MCP registry as io.github.gutomezencio/front-proxy. Map local domains (and HTTPS) to apps on local ports, OS-wide, via /etc/hosts and a reverse proxy. This page covers its npm package (front-proxy).
Is the front-proxy MCP server safe to use?
front-proxy scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 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 front-proxy MCP server expose?
front-proxy exposes 7 tools: list_hosts, add_host, update_host, remove_host, generate_certs, and 2 more. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Is the front-proxy MCP server still maintained?
front-proxy is still listed as active in the MCP registry. We last reached this channel on 24 October 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 front-proxy MCP server under?
front-proxy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.