ameriflux-mcp@r1
VERIFIED· not startedPublisher claims: "Enables agents to search AmeriFlux and FLUXNET eddy-covariance tower sites, check product and year availability, decode FLUXNET variable names and QC flags, and retrieve versioned citations and data-policy obligations. Also supports consented downloads and local previewing of AmeriFlux BASE/BADM, FLUXNET-1F, and FLUXNET2015 FULLSET/SUBSET files." 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
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso lbl.gov, fluxdata.org, githubusercontent.com, fluxnet.org, datacite.org, doi.org, astral.sh, opencode.ai, example.org, openxmlformats.org — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is ameriflux-mcp@r1 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 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 · 3 scenarios · 0 deviationsStatic findings
block += f"\n[mcp_servers.{name}.env]\n" + "\n".join(f"{k} = {q(v)}" for k, v in env.items()) + "\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Replace or append the [mcp_servers.<name>] table and its [mcp_servers.<name>.env] sub-table.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.app = mcp_server.streamable_http_app(Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.if t in (header, f"[mcp_servers.{name}.env]"):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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.