Insufficient coverage

No critical or high issue was observed, but coverage was not sufficient to certify this surface as safe. A findings-free result here reads as insufficient coverage, not safe.

pypiscanned 3 months ago

Rescan

Coverage

Minimal

Tests run

Findings

0 rules · 0 total

Worst severity

None

Not run on this surface

These rules could not be reached by this scan method. They stay listed and counted, so coverage is never overstated. Each says why it did not run and what would unlock it.

4Live connectionRules whose declared input (live connection) this scan method did not supply.rescan to unlock

109Source codeRules whose declared input (source code) this scan method did not supply.rescan to unlock

71No execution recordNo record that these rules ran on this surface.rescan

Why these stay. The verdict is coverage aware. A clean result would read "Insufficient coverage", not "Safe", precisely because these rules did not run. Hiding them would let a shallow scan look as thorough as a deep one.

How this server was scanned

The method behind this result was not recorded: the scan predates it. How deep it reached is unknown, and is not implied by anything on this page.

Verifiable Findings

Not yet attested

This server has not been scanned with attestation enabled yet.

How to verify this yourself

# Re-run the analyzer on the signed snapshot and recompute the findings digest
curl -s https://mcp-sentinelapi-production.up.railway.app/api/v1/servers/adls2-mcp-server/attestation.json > att.json
npx mcp-sentinel verify-scan --attestation att.json

# Prove the attestation is in the public transparency log
curl -s https://mcp-sentinelapi-production.up.railway.app/api/v1/servers/adls2-mcp-server/attestation/inclusion.json > incl.json
npx mcp-sentinel transparency verify-inclusion --proof incl.json

Observed behaviorexecuted in sandbox

Declared tool hints vs. what each tool was actually observed to do when executed in our egress-denied sandbox - plus any witnessed tool→tool flow within this one server. This is not cross-server toxic flow, which composes several servers in one config.

Observed behavior not captured for this scan

No observed-behavior record is on file for this server's latest scan.

This is a coverage gap - we did not execute this server’s tools in the sandbox for this scan. It is not a clean result and is not scored as one. To see how observed behavior is rendered when a run does happen, view the illustrative cross-server toxic flow.

Intrinsic here, config-scoped elsewheredual unit

Everything on this page — the verdict, every finding — is adls2-mcp-server assessed on its own. That is its intrinsic posture. Whether it becomes one leg of a cross-server toxic flow is a different, config-scoped question: it depends on which other servers share its client config, and no verdict on this page changes for it.

Registry-wide co-existence →The capability pairs across the registry this server could participate in if co-configured. Hypothetical, CVE-backed templates — not observed here and not an attack path against this deployment.Scan a config →Submit a client config that includes this server to get the real, config-scoped cross-server flow for the servers you actually run together.

Deepen this scan

Every link below opens a form prefilled with this server’s details. Nothing runs until you submit.

Publish your source on GitHubto unlock rules skipped for want of this input
Register a live MCP endpointto unlock rules skipped for want of this input
Rescanre-run the scan of the published artifact or repository - a published package runs in the sandbox by default where this deployment has a runner
Combine with other serversanalyze this server alongside others in one config
Watch it run in a sandboxobserve the published artifact under an egress-denied sandbox