Skills/PyPI/smart-mcp-proxy

smart-mcp-proxy@0.3.1

VERIFIED· not started

Publisher claims: "Smart MCP Proxy - A federating gateway for MCP servers with intelligent tool discovery" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher dumbris · publishing for 523 daysInstalls 100Last detonated 1 h ago
$claude mcp add smart-mcp-proxy -- uvx smart-mcp-proxy
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
OPENAI_API_KEYConfiguration, not credentials: MCPPROXY_CONFIG_PATH, MCPPROXY_DATA_DIR, MCPPROXY_EMBEDDER, MCPPROXY_HF_MODEL, MCPPROXY_HOST, MCPPROXY_LIST_CHANGED_EXEC, MCPPROXY_LOG_FILE, MCPPROXY_LOG_LEVEL, MCPPROXY_PORT, MCPPROXY_RESET_DATA, MCPPROXY_ROUTING_TYPE, MCPPROXY_TOOL_NAME_LIMIT, MCPPROXY_TOOLS_LIMIT, MCPPROXY_TOP_K, MCPPROXY_TRANSPORT, MCPPROXY_TRUNCATE_OUTPUT_LEN
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for OPENAI_API_KEY and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx smart-mcp-proxy

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 82/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsscripts/test.sh:6 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "📄 Loading environment variables from .env..."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/test.sh:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filessource .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/test.sh:4 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load environment variables if .env existsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/test.sh:5 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ -f .env ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Cross-server tool referencetests/integration/test_full_flow.py:290 · Cross-server tool reference — agent may chain tools across untrusted MCP servers"""Test that tools from different servers are properly isolated yet searchable."""Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/unit/test_config.py:215 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_servers={"test": ServerConfig(url="http://test")},Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
Cross-server tool referencetests/unit/test_indexer.py:645 · Cross-server tool reference — agent may chain tools across untrusted MCP servers"""Test indexing tools from different servers."""Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

Cost to the agent

Instructions loaded
≈59 tok
1 file · 50 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for smart-mcp-proxy@0.3.1 as of 58 min ago. This is the package itself, not its dependencies.

smart-mcp-proxy@0.3.1 safety verdict: Verified (not started) — KillerSkills