opensearch-mcp-server-py@0.12.0
VERIFIED· not startedPublisher claims: "OpenSearch MCP Server" 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
OPENSEARCH_HEADER_AUTHOPENSEARCH_NO_AUTHOPENSEARCH_PASSWORDConfiguration, not credentials: AWS_IAM_ARN, AWS_OPENSEARCH_COLLECTION_ID, AWS_OPENSEARCH_DOMAIN_NAME, AWS_OPENSEARCH_SERVERLESS, AWS_PROFILE, AWS_REGION, MEMORY_AGENT_ID, MEMORY_INDEX_NAME, MEMORY_TOOLS_ENABLED, MEMORY_USER_ID, OPENSEARCH_ALLOW_AMBIENT_AWS_FALLBACK, OPENSEARCH_DISABLED_CATEGORIES, OPENSEARCH_DISABLED_TOOLS, OPENSEARCH_DISABLED_TOOLS_REGEX, OPENSEARCH_DYNAMIC_CONNECTION, OPENSEARCH_ENABLED_CATEGORIES, OPENSEARCH_ENABLED_TOOLS, OPENSEARCH_ENABLED_TOOLS_REGEX, OPENSEARCH_MAX_RESPONSE_SIZE, OPENSEARCH_MEMORY_CONTAINER_ID, OPENSEARCH_MEMORY_MONITOR_INTERVAL, OPENSEARCH_MODE, OPENSEARCH_QUERY_TIMEOUT, OPENSEARCH_SETTINGS_ALLOW_WRITE, OPENSEARCH_SETTINGS_ALLOW_WRITE_CATEGORIES, OPENSEARCH_SSL_VERIFY, OPENSEARCH_SSRF_GUARD, OPENSEARCH_TIMEOUT, OPENSEARCH_TOOL_CATEGORIES, OPENSEARCH_URL, OPENSEARCH_USERNAME- Where it talks to
- no vendor host named in the codeAlso claude.com, cursor.com, amazon.com, githubusercontent.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 claude.com, cursor.com, amazon.com, githubusercontent.com as well as its own vendor. The guard injects OPENSEARCH_HEADER_AUTH, OPENSEARCH_NO_AUTH, OPENSEARCH_PASSWORD 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-13 and scored it 95/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
"""Append memory instructions to CLAUDE.md if not already present."""Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.No other findings across 14,948 lines in 50 files.
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 opensearch-mcp-server-py@0.12.0 as of 15 h ago. This is the package itself, not its dependencies.