simple-mcp-client@1.0.11
VERIFIED· not startedPublisher claims: "A simple MCP client for testing MCP servers" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
DEEPSEEK_API_KEYLANGCHAIN_API_KEYOPENAI_API_KEYOPENROUTER_API_KEYConfiguration, not credentials: LANGCHAIN_ENDPOINT, LANGCHAIN_PROJECT, LANGCHAIN_TRACING_V2, MCP_LOG_LEVEL- Where it talks to
- no vendor host named in the codeAlso deepseek.com, openrouter.ai, langchain.com — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names deepseek.com, openrouter.ai, langchain.com as well as its own vendor. The guard injects DEEPSEEK_API_KEY, LANGCHAIN_API_KEY, OPENAI_API_KEY, OPENROUTER_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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 87/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 deviationsStatic findings
assert saved_config["mcpServers"]["new_server"]["type"] == "sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.config.type = "sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."""Load environment variables from .env file."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert config.config.mcpServers["test_server"].url == "http://test-server.com/sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.assert saved_config["mcpServers"]["new_server"]["url"] == "http://new-server.com/sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.# Handle special case for npx and validate commandFix: Pin versions and sources; vendor anything fetched at install time.assert config.config.mcpServers["test_server"].type == "sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.config.url = "http://test-server.com/sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.config.url = "http://test-server.com/sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.config.type = "sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.MCPServerError, ToolExecutionError, ResourceAccessError, PromptErrorFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.execute_tool.assert_called_with("test_tool1", {"param1": "value1"}, retries=2)Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.config.url = "http://test-server.com/sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.config.type = "sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.execute_tool.assert_called_with("test_tool1", {"param1": "value1"}, retries=2)Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.read_resource.assert_called_with("test/resource1")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.config.type = "sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.mock_mcp_server.read_resource.assert_called_with("test/resource1")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
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 simple-mcp-client@1.0.11 as of 22 min ago. This is the package itself, not its dependencies.