redfox-data-mcp@0.2.0
VERIFIED· not startedPublisher claims: "RedFox data MCP: find, describe, call and result over the RedFoxHub catalog" 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
REDFOX_API_KEYREDFOX_MCP_AUTH_MODEREDFOX_MCP_OAUTH_BASE_URLREDFOX_MCP_OAUTH_ISSUER_URLREDFOX_MCP_OAUTH_RESOURCE_BASE_URLREDFOX_OAUTH_CONSENT_URLREDFOX_OAUTH_STUB_USER_IDREDFOX_OAUTH_TEST_API_KEYREDFOX_OAUTH_USER_KEY_MAPConfiguration, not credentials: REDFOX_MCP_HOST, REDFOX_MCP_PATH, REDFOX_MCP_PORT, REDFOX_MCP_TRANSPORT- Where it talks to
- no vendor host named in the codeAlso redfox.hk — 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 redfox.hk as well as its own vendor. The guard injects REDFOX_API_KEY, REDFOX_MCP_AUTH_MODE, REDFOX_MCP_OAUTH_BASE_URL, REDFOX_MCP_OAUTH_ISSUER_URL, REDFOX_MCP_OAUTH_RESOURCE_BASE_URL, REDFOX_OAUTH_CONSENT_URL, REDFOX_OAUTH_STUB_USER_ID, REDFOX_OAUTH_TEST_API_KEY, REDFOX_OAUTH_USER_KEY_MAP 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-15 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
No findings across 5,966 lines in 14 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
Not checked against OSV yet; the weekly check has not reached this version.