Skip to content

MCP Sentinel · Security intelligence

Evidence
before trust.

Your agent's tools deserve a closer look. Explore the servers, follow the findings, and see where the evidence ends.

An identity opens a path through the evidence.

72,593servers listed

20,246with a recorded analysis

184active detection rules

Explore the ecosystem

01 / Registry intelligence

An ecosystem,
made legible.

Find the server behind the name. Read its identity, findings, assessment history, and coverage in one public record.

Open the registry

02 / Traceable findings

A finding should
lead somewhere.

Follow a finding through its source, propagation, and impact. Inspect the rule, verification steps, and remediation alongside what the assessment could not establish.

Explore traceable findings

03 / Sandbox observations

Look beyond
the description.

Inspect a published artifact running inside a sandbox with network egress denied and the filesystem confined. Read the responses, witnessed behavior, and execution gaps.

A failed tool call remains a failure. Runtime availability depends on the deployment and target.

Inspect a target

04 / Cross-server intelligence

Connections change
the question.

Examine the servers you configure together. Cross-server flow is labelled observed or inferred; kill-chain patterns are hypothetical.

05 / Attack chains

A possible path
has prerequisites.

Inspect hypothetical kill-chain patterns for a configuration or registry selection. Follow the capabilities, preconditions, and mitigations behind each step.

A computed chain is a possibility, not a witnessed attack.

Examine the patterns

06 / Sandbox playground

Bring a target.
Keep the boundary.

Onboard a package or configuration for a sandbox run where available. Inspect what actually ran through its capabilities, responses, and execution gaps.

Live URLs use read-only enumeration, separately from sandbox execution.

Enter the playground

07 / Interactive workbench

Ask the
next question.

Inspect tools, resources, and prompts in a held-open sandbox session. Run an explicit operation and follow the session's responses and provenance.

Sessions remain bounded by the sandbox. The workbench reports when its required worker is unavailable.

Open the workbench

08 / Framework mapping

Different frameworks.
Shared evidence.

Read how findings relate to security controls across OWASP, MITRE ATLAS, NIST, ISO, and other supported frameworks.

A control mapping supports review; it does not certify compliance.

Explore the mappings

09 / Verifiable records

Keep the evidence
attached.

Explore a server's findings and report exports, with verification details and signed records where available.

A signature establishes integrity. It does not turn an incomplete assessment into a safety guarantee.

Explore the reports

The thread leads back to the source

Trust has
a source.

Choose a server. Inspect a claim. Follow the evidence.