Skills/Glama/fuel-mcp

fuel-mcp@r1

CAUTION· not started

Publisher claims: "Enables finding the cheapest nearby fuel station for diesel or petrol, returning its price, distance, and age in a single sentence. Supports simulated data and configurable real price sources, including use in voice sessions over stdio." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher roykollensvendsen · publishing for 2 daysInstalls 0Last detonated 2 h ago

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: Caution 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 code
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.

$vet-skills run --net declared -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is fuel-mcp@r1 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-22 and scored it 76/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: HTML comment carrying imperative instructions to the agent. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

CRITICAL
HTML comment carrying imperative instructions to the agentREADME.md:149 · HTML comment carrying imperative instructions to the agentnot run: the workflow runs each of these; nesting them here would run the suite inside itselfFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01
MEDIUM
Python subprocess execution detectedscripts/imperative.py:161 · Python subprocess execution detectedresult = subprocess.run( # noqa: S603Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
File permission modification commandsrc/fuel_mcp/safe_file.py:83 · File permission modification command — agent changes file ownership/permissionsmsg = f"{folder} is open to others, so nothing private goes in it. Fix: chmod go-rwx {folder}"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
Process kill commandscripts/ratchet.py:313 · Process kill command — agent can terminate processeskill -9 -- -<its pid>, which this script prints; the next rule check then puts its file back.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedscripts/mutate.py:402 · Python subprocess execution detecteddone = subprocess.run( # noqa: S603 - this interpreter, asked one fixed questionFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Process kill commandscripts/ratchet.py:339 · Process kill command — agent can terminate processesf" another terminal with: kill -9 -- -{child.pid}\n"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
File permission modification commandsrc/fuel_mcp/sinks/__init__.py:133 · File permission modification command — agent changes file ownership/permissionsfix = f"chmod go-w {path}" if facts.st_uid in owners else f"move the private folder out of {path}"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
Process kill commandscripts/mutate.py:494 · Process kill command — agent can terminate processes# RULE: a kill by another test names the tests that went redFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandscripts/ratchet.py:303 · Process kill command — agent can terminate processessubprocess.run would kill it outright: a rule check would leave a file switched off,Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
File permission modification commandsrc/fuel_mcp/safe_file.py:12 · File permission modification command — agent changes file ownership/permissions``chmod go-rwx <folder>``, with one log line. The log never holds what the fileFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
Process kill commandscripts/mutate.py:493 · Process kill command — agent can terminate processes# A kill that can flip between runs has to say what flipped it.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandscripts/mutate.py:488 · Process kill command — agent can terminate processes# A kill by some other test is not evidence about this rule.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandscripts/mutations/scripts/mutate.py/a-kill-by-another-test-names-the-tests-that-went-red.toml:2 · Process kill command — agent can terminate processesname = "a kill by another test names the tests that went red"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
LOW
Dynamic module loadingsrc/fuel_mcp/sinks/__init__.py:113 · Dynamic module loadingif importlib.util.find_spec(PACKAGE) is not None:Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandscripts/ratchet.py:308 · Process kill command — agent can terminate processestwice. Its output goes to files, not pipes: after a kill -9 of this run, a pipe wouldFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedscripts/mutate.py:317 · Python subprocess execution detectedr = subprocess.run( # noqa: S603 - this interpreter, pytest, and a folder this script madeFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/private_data_scan.py:143 · Python subprocess execution detecteddone = subprocess.run(command, cwd=ROOT, capture_output=True, encoding="utf-8", check=True) # noqa: S603Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/ratchet.py:316 · Python subprocess execution detectedchild = subprocess.Popen( # noqa: S603 - the commands are this script's ownFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Process kill commandscripts/mutate.py:14 · Process kill command — agent can terminate processesA kill is not enough on its own. A mutation breaks whatever it breaks, and itFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedscripts/readable.py:76 · Python subprocess execution detectedresult = subprocess.run( # noqa: S603Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Process kill commandscripts/mutate.py:341 · Process kill command — agent can terminate processes# turns colour back on, which would otherwise make every kill unattributable.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈3,141 tok
1 file · 80 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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.

What would make this Verified

4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim roykollensvendsen: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
  3. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  4. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
  5. File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
  6. Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
Publish a new version to Glama, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim roykollensvendsenPropose a patch to the maintainer
fuel-mcp@r1 safety verdict: Caution (not started) — KillerSkills