fastmcp 4.1.1
- Source
- https://github.com/PrefectHQ/fastmcp
- Tag scanned
v4.1.1- Compared with
v4.1.0(0 signals introduced since)- Files
- 992 scanned, 749 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 25 info
- Scan time
- 19.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 25 of 25 warn and critical signals; 25 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-19 04:11
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewframe-introspectionfastmcp_slim/fastmcp/client/transports/inference.py:41:13= 1 =likely benign Walks the call stack via sys._getframe to locate the first frame outside the package.Reasoning
sys._getframe(1) walks the call stack to find the first caller outside the fastmcp package, which is a common way to attribute inference to the calling user code. The snippet shows no obfuscation, encoding, or network or exec behavior, so it is most likely a legitimate design choice.
-
# Generated code should compilelikely benign Test asserts that generated source code compiles.Reasoning
In a test, compile() checks that generated CLI source is syntactically valid. The source is produced by the code under test, not attacker input, and compile() does not execute it.
-
assert not inlikely benign Test compiles generated source to verify syntax.Reasoning
Same pattern as the other generate-CLI tests: compile() validates generated source in a test. It only compiles and never executes the code.
-
assert inlikely benign Test compiles generated source to check syntax.Reasoning
compile() is used in a test to check that generated code is syntactically valid. The input is generator output and nothing is executed.
-
)likely benign Test compiles generated source to check syntax.Reasoning
compile() validates generated code inside a unit test. This is a syntax check on output from the code under test.
-
assert inlikely benign Test compiles generated source to check syntax.Reasoning
compile() is a syntax-validation step on generated source in a test. No execution occurs.
-
)likely benign Test compiles a generated script to verify it is valid.Reasoning
compile() on a generated script string in a test is a syntax check. The script comes from the generator under test.
-
) assert inlikely benign Test compiles a generated script to verify validity.Reasoning
compile() of a generated script in a test is a syntax check on generator output, not dynamic execution of untrusted input.
-
# Should compile without syntax errors # App name should have escaped quotes assert r inlikely benign Test verifies a generated script compiles and has escaped quotes.Reasoning
The comment says the script should compile without syntax errors, which confirms a syntax-validation purpose. The escaped-quote assertion shows the test is checking generator output.
-
)likely benign Test compiles generated script output for syntax.Reasoning
compile() on generated script text in a test is a syntax check. Nothing is executed.
-
)likely benign Test compiles generated script output for syntax.Reasoning
compile() validates generated script output in a test. This is not an execution path for untrusted data.
-
=likely benign Test compiles a generated output file to check syntax.Reasoning
compile() is applied to a file the test just wrote, to check it is valid Python. It is a syntax check only.
-
= assert in =likely benign Test compiles a generated output file and checks its content.Reasoning
compile() on generated output read from a temp file is a syntax check in a test. The non-ASCII assertion shows it is testing generator output content.
-
)likely benign Base64-encoded PNG image fixture in a conformance test server.Reasoning
The snippet is a base64 string that starts with the PNG signature (iVBORw0KGgo) and matches the test-image pattern in a conformance server. Embedded image fixtures are normal, and the low compression ratio fits compressed PNG data.
-
likely benign Test dynamically imports modules referenced in documentation examples to verify they resolve.
Reasoning
In a docs-example test, __import__ checks that modules named in documentation imports can be loaded. The module name comes from parsing doc source, and the result is only used to record ImportError failures. Critical severity reflects the dynamic import pattern, not malicious use here.
-
=likely benign Test imports a module from a documentation example with fromlist to check it resolves.Reasoning
This __import__ call with fromlist loads a module named in a doc example so the test can verify the import works. It is a test-harness pattern, and its failures are collected as errors.
-
: = returnlikely benign Test helper executes Python code examples extracted from upgrade guide docs.Reasoning
exec of compiled source extracted from documentation code blocks in a test harness. Source comes from repo docs under test, not untrusted input; standard doc-example testing pattern.
-
: = returnlikely benign compile() of extracted doc example source inside the same test helper.Reasoning
compile() is the companion of the exec above and operates on repo-local doc source; no external input or obfuscation.
-
likely benign Executes upgrade guide example code in a test with warnings ignored.
Reasoning
Test runs documentation examples from the repository, with warnings suppressed. Consistent with doc-testing; source is local and trusted.
-
likely benign compile() of documentation example source for test execution.
Reasoning
compile() of local documentation example source feeding the exec; no obfuscation evident.
-
= =likely benign Base64-encoded tiny PNG image constant used as test fixture data.Reasoning
A small base64-encoded 1x1 PNG test fixture decoded at module load for a downstream test server. Typical embedded test image, not a dropper.
-
return awaitlikely benign Test executes wrapped code-mode snippet in an isolated namespace.Reasoning
Test wraps generated code in a namespace and execs it; the code is produced by the code-mode transform under test, not attacker input. Expected for testing a code-execution feature.
-
info
warn→ info by reviewdynamic-executiontests/experimental/transforms/test_code_mode_discovery.py:76:9return awaitlikely benign Test execs a wrapped code-mode test program in a namespace.Reasoning
Same pattern as the sibling code_mode test: exec of locally generated wrapped test code within a test function.
-
# Create a simple 1x1 white pixel PNG = b returnlikely benign Inline PNG bytes literal used to build a test Image.Reasoning
A bytes literal containing a 1x1 PNG built in a test to create an Image object. Legitimate fixture data with no execution or exfiltration.
-
= =likely benign Base64 PNG data URI string used in an icon inspection test.Reasoning
A base64 PNG data URI used as icon test input for a FastMCP server. Standard test fixture.
Reproduce This Scan
Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
&&