Fiftyone MCP Server

fiftyone-mcp-server PyPI v0.1.13

Published by voxel51 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server exposing FiftyOne dataset analysis tools

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 7

high Dynamic evaluation of a non-literal value (src/fiftyone_mcp/tools/view_builder.py)MTC-SRC-010

In the server's implementation (`src/fiftyone_mcp/tools/view_builder.py:82`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: return eval(expr_str, _EVAL_GLOBALS, _EVAL_LOCALS) except Exception as e: raise ValueError(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/fiftyone_mcp/tools/view_builder.py

high Tool "list_evaluations" exposes command/code executionMTC-CAP-001

Tool "list_evaluations" appears to run shell commands or evaluate code (parameter "eval"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool list_evaluations

high Dynamic code execution in server code (src/fiftyone_mcp/tools/view_builder.py)MTC-SRC-001

In the server's implementation (`src/fiftyone_mcp/tools/view_builder.py:82`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: return eval(expr_str, _EVAL_GLOBALS, _EVAL_LOCALS) except Exception as e: raise ValueError(

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/fiftyone_mcp/tools/view_builder.py

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([download_plugin]) co-exist with external-action tools ([list_evaluations]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [download_plugin] → sinks [list_evaluations]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow download_plugin → list_evaluations

medium Unconstrained URL/host parameter "url_or_repo" on "download_plugin"MTC-CAP-007

Tool "download_plugin" takes a URL/host parameter "url_or_repo" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool download_plugin · inputSchema.properties.url_or_repo

medium Unconstrained command parameter "eval_type" on "list_evaluations"MTC-CAP-006

Tool "list_evaluations" takes a command-shaped parameter "eval_type" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool list_evaluations · inputSchema.properties.eval_type

low Mutating tool "list_evaluations" declares no destructiveHintMTC-CAP-005

Tool "list_evaluations" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool list_evaluations

Tools 47

Each tool and what it can reach — statically extracted from the published source.

  • download_pluginingests untrusted input
  • list_evaluationsruns code / shell
  • add_sample_fieldno sensitive capability
  • add_samplesno sensitive capability
  • annotateno sensitive capability
  • boundsno sensitive capability
  • clear_viewno sensitive capability
  • count_sample_tagsno sensitive capability
  • count_valuesno sensitive capability
  • dataset_summaryno sensitive capability
Show 37 more tools ↓
  • disable_pluginno sensitive capability
  • distinctno sensitive capability
  • enable_pluginno sensitive capability
  • execute_operatorno sensitive capability
  • execute_pipelineno sensitive capability
  • get_app_configno sensitive capability
  • get_color_schemeno sensitive capability
  • get_context_infono sensitive capability
  • get_field_schemano sensitive capability
  • get_operator_schemano sensitive capability
  • get_plugin_infono sensitive capability
  • get_sidebar_groupsno sensitive capability
  • get_valuesno sensitive capability
  • histogram_valuesno sensitive capability
  • launch_appno sensitive capability
  • list_brain_runsno sensitive capability
  • list_datasetsno sensitive capability
  • list_delegated_operationsno sensitive capability
  • list_me_scenariosno sensitive capability
  • list_open_panelsno sensitive capability
  • list_operatorsno sensitive capability
  • list_pluginsno sensitive capability
  • load_datasetno sensitive capability
  • meanno sensitive capability
  • reset_color_schemeno sensitive capability
  • set_active_fieldsno sensitive capability
  • set_color_schemeno sensitive capability
  • set_filtersno sensitive capability
  • set_session_color_schemeno sensitive capability
  • set_sidebar_groupsno sensitive capability
  • set_spacesno sensitive capability
  • set_valuesno sensitive capability
  • set_viewno sensitive capability
  • stdno sensitive capability
  • sumno sensitive capability
  • tag_samplesno sensitive capability
  • untag_samplesno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.13 latest A 93/100 7 1.13.0 2026-08-25
v0.1.12 A 93/100 7 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/fiftyone-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/fiftyone-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/fiftyone-mcp-server"><img src="https://mcptrustchecker.com/registry/fiftyone-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/fiftyone-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan fiftyone-mcp-server --online --registry pypi

Use the free API → How scoring works

More in AI & Agents