Radar — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow cluster-operation coverage and platform changes because the MCP surface can be high impact

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Local-first Kubernetes inspection and operations with a built-in MCP surface.

What we know

Skyhook Radar is a local-first Kubernetes dashboard that includes MCP capabilities for inspecting and operating Kubernetes resources.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)Rename the Cloud AI group to radar:ai:reader before 1.16.0 ( 1973)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can inspect and potentially operate cluster resources according to Kubernetes credentials. Writes: Potential Kubernetes resource operations.
Uses configured Kubernetes access.
Sensitive access: Cluster state, Kubernetes credentials/secrets depending on permissions

Kubernetes credentials can confer broad infrastructure authority; bind Radar to least-privilege cluster roles.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

3,666 repository stars

Stars observed Oct 6, 2026.

All limitations / Review context

What Kubernetes read and write operations does the current built-in MCP server expose?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Kubernetes credentials can confer broad infrastructure authority; bind Radar to least-privilege cluster roles.
Can inspect and potentially operate cluster resources according to Kubernetes credentials.
Uses configured Kubernetes access.
Cluster metadata and resource data are processed locally/in the deployment.
Reviewed write actions: Potential Kubernetes resource operations
Sensitive access: Cluster state, Kubernetes credentials/secrets depending on permissions
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Exact MCP transport and endpoint
MCP transport/endpoint details were not fully materialized in the reviewed source.
Cluster authority depends on the Kubernetes credentials supplied to Radar.

Original activity observations

2026-10-05T17:56:13Z: Rename the Cloud AI group to radar:ai:reader before 1.16.0 ( 1973)

Technical identity

github.com/skyhook-io/radar

Exact implementation source: https://github.com/skyhook-io/radar ↗
Reviewed resource type: Host
Repository identity: skyhook-io/radar

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
skyhook-io/radar
Recorded repository material and project history.

Setup · Watchlist

Host / Desktop app setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Download / install
Publisher instructions
Skyhook Radar is a Kubernetes GUI/host tool, not an MCP server.
package install · Publisher instructions
brew install kubectl-radar
publisher setup or prerequisite · Publisher instructions
kubectl radar
Configure application / integrations
MCP100 setup guide
This is a Kubernetes radar CLI/desktop tool; use its built-in experience. Do not pretend `kubectl radar` is a standalone stdio MCP server.
Check connection
Suggested check
Run `kubectl radar` with a configured kubecontext; confirm cluster views without making cluster changes.
Disconnect / uninstall / revoke
MCP100 setup guide
Radar is primarily a kubectl plugin and app, not an independent MCP server. If installed via Homebrew use `brew uninstall kubectl-radar`; Krew `kubectl krew uninstall radar`; in-cluster Helm `helm uninstall radar -n radar`. Pick only the matching install method.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Package / application uninstall · matching installation environment · MCP100 composed guide
brew uninstall kubectl-radar

Official Documentation & Sources

What it does

Skyhook Radar is a local-first Kubernetes dashboard that includes MCP capabilities for inspecting and operating Kubernetes resources.

Capability: Cloud & DevOps
Resource type: Host
Industry: Software & Technology
Best fit: Local-first Kubernetes inspection and operations with a built-in MCP surface.

Representative uses

Inspect Kubernetes resources
Investigate cluster state
Operate through the built-in MCP surface
Use Helm-based in-cluster deployment

Limitations

MCP transport/endpoint details were not fully materialized in the reviewed source.
Cluster authority depends on the Kubernetes credentials supplied to Radar.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Uses configured Kubernetes access.
Permissions: Can inspect and potentially operate cluster resources according to Kubernetes credentials.
Data handling: Cluster metadata and resource data are processed locally/in the deployment.
Cost: free
Risk and cautions: Kubernetes credentials can confer broad infrastructure authority; bind Radar to least-privilege cluster roles.

Access scope and cautions

Write actions: Potential Kubernetes resource operations
Sensitive access: Cluster state Kubernetes credentials/secrets depending on permissions
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect Kubernetes resources; Investigate cluster state; Operate through the built-in MCP surface; Use Helm-based in-cluster deployment.

What authentication is documented?

Kubernetes/deployment specific.

Can it modify data or perform write operations?

Documented write actions include: Potential Kubernetes resource operations. Recorded permission boundary: Can inspect and potentially operate cluster resources according to Kubernetes credentials.

What data-handling boundary should I consider?

Cluster metadata and resource data are processed locally/in the deployment. Recorded sensitive-access context: Cluster state; Kubernetes credentials/secrets depending on permissions.

What limitations and risks should I check before use?

Kubernetes credentials can confer broad infrastructure authority; bind Radar to least-privilege cluster roles. MCP transport/endpoint details were not fully materialized in the reviewed source. Cluster authority depends on the Kubernetes credentials supplied to Radar. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

Skyhook is listed as First-party MCP in MCP100’s current evidence.