osdu-mcp-server@1.0.0
VERIFIED· not startedPublisher claims: "MCP server for OSDU platform integration" 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
AWS_ACCESS_KEY_IDAZURE_CLIENT_SECRETGOOGLE_APPLICATION_CREDENTIALSOSDU_MCP_AUTH_SCOPEOSDU_MCP_USER_TOKENConfiguration, not credentials: AWS_PROFILE, AZURE_CLIENT_ID, AZURE_TENANT_ID, OSDU_MCP_ENABLE_DELETE_MODE, OSDU_MCP_ENABLE_WRITE_MODE- Where it talks to
- your-osdu.com (its own)Also amazon.com, google.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 amazon.com, google.com as well as its own vendor. The guard injects AWS_ACCESS_KEY_ID, AZURE_CLIENT_SECRET, GOOGLE_APPLICATION_CREDENTIALS, OSDU_MCP_AUTH_SCOPE, OSDU_MCP_USER_TOKEN only into requests to your-osdu.com (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-14 and scored it 88/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
from osdu_mcp_server import list_mcp_assetsFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.export OSDU_MCP_SERVER_URL="https://your-osdu.com"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.from osdu_mcp_server import list_mcp_assetsFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."Check AWS_PROFILE environment variable or ~/.aws/config"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.2. AWS CLI profiles (~/.aws/config)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 osdu-mcp-server@1.0.0 as of 6 h ago. This is the package itself, not its dependencies.