Skip to content

Commit edad5fa

Browse files
authored
chore(053): server.json description — local-first + security scanning (#516)
* chore(053): server.json description — surface local-first + security scanning Updates the registry description to reflect current positioning: local-first operation and built-in security scanning (sensitive-data detection) alongside the existing BM25 discovery, quarantine, and token-savings messaging. Version already matches the latest release (0.33.1). Schema-validated (98/100 chars). * chore(053): drop invalid localhost remote from server.json The registry's semantic validation rejects http://localhost:8080/mcp (invalid-remote-url) — remotes[] must be publicly reachable. mcpproxy is local-first with no public remote and no supported package type yet, so the entry is discovery-only (name + description + repo link). Updated the publish guide's schema notes to match. Validated clean with 'mcp-publisher validate'.
1 parent 2a7d54c commit edad5fa

2 files changed

Lines changed: 4 additions & 10 deletions

File tree

docs/mcp-registry-publishing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,8 +97,8 @@ mcp-publisher status --status deleted \
9797

9898
- `version` must be a plain semantic version string (`0.33.1`) — no `v` prefix, no ranges.
9999
- `packages[]` is empty because none of the supported `registryType` values (`npm`, `pypi`, `oci`, `nuget`, `mcpb`) match MCPProxy's distribution channels (Homebrew tap, GitHub release tarballs, `.deb`/`.rpm`, `go install`). The Docker server-edition image at `ghcr.io/smart-mcp-proxy/mcpproxy-server` is not yet published to releases (gated behind `if: false` in the release workflow).
100-
- `remotes[]` describes the actual MCP transport: a locally-run `mcpproxy serve` instance that exposes a Streamable HTTP endpoint at `http://localhost:8080/mcp`. MCP clients that support HTTP transport connect directly to this address.
101-
- If a Docker image for the server edition is published in a future release, add an `oci` entry to `packages[]` pointing at `ghcr.io/smart-mcp-proxy/mcpproxy-server:{version}` with `"transport": {"type": "stdio"}` and the appropriate `runtimeArguments` for `docker run`.
100+
- `remotes[]` is intentionally **omitted**. mcpproxy runs locally (`mcpproxy serve` exposes Streamable HTTP at `http://localhost:8080/mcp`), but the registry's semantic validation **rejects localhost/private remote URLs** (`invalid-remote-url`) — `remotes[]` is reserved for publicly reachable hosted endpoints. With no public remote and no installable package type, the entry is **discovery-only**: it lists the server, description, and repository link so clients can find it and follow the repo's install instructions.
101+
- If a Docker image for the server edition is published in a future release, add an `oci` entry to `packages[]` pointing at `ghcr.io/smart-mcp-proxy/mcpproxy-server:{version}` with `"transport": {"type": "stdio"}` and the appropriate `runtimeArguments` for `docker run`. That would upgrade the entry from discovery-only to one-click installable.
102102

103103
## References
104104

server.json

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,18 +2,12 @@
22
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
33
"name": "io.github.smart-mcp-proxy/mcpproxy-go",
44
"title": "MCPProxy",
5-
"description": "Smart MCP proxy with BM25 tool discovery, quarantine security, and ~99% token savings",
5+
"description": "Local-first MCP proxy with BM25 tool discovery, security scanning, quarantine & ~99% token savings",
66
"websiteUrl": "https://mcpproxy.app",
77
"repository": {
88
"url": "https://github.com/smart-mcp-proxy/mcpproxy-go",
99
"source": "github"
1010
},
1111
"version": "0.33.1",
12-
"packages": [],
13-
"remotes": [
14-
{
15-
"type": "streamable-http",
16-
"url": "http://localhost:8080/mcp"
17-
}
18-
]
12+
"packages": []
1913
}

0 commit comments

Comments
 (0)