Evidra vs Radar

A side-by-side look at the Evidra and Radar MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Evidra logoEvidraCloud PlatformsFail-closed policy guardrails for AI agents running kubectl, terraform, helm, and argocd.35FairAuth: not declaredRadar logoRadarCloud Platforms · Remote HTTP/SSEBuilt-in MCP server for Radar, a modern Kubernetes visibility tool. Lets AI agents query cluster topology, resources, events, logs, and Helm/GitOps state across multiple clusters. Single binary, no agents, no cloud dependency. Apache 2.0.60GoodAuth: no auth required

Verdict: choose Evidra for cloud platforms work; choose Radar for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Evidra logoChoose Evidra when

  • You need dedicated capabilities in the Cloud Platforms domain.
Explore Evidra

Radar logoChoose Radar when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Radar

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEvidra logoEvidraRadar logoRadar
CategoryCloud PlatformsCloud Platforms
Quality signal35/100 · Fair60/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars153,908
Directory activity 3 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Evidra tools

No tool names declared yet. Check the project README from the listing page.

Radar tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Evidra

No confirmed install command for Evidra yet — follow the setup steps linked from its listing page rather than a guessed package name.

Radar

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "skyhook-io-radar": {
      "url": "https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=1130618&theme=neutral&period=daily"
    }
  }
}

Frequently asked questions

Evidra is categorized under Cloud Platforms and uses an install path we have not confirmed yet. Radar belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Evidra for cloud platforms work and Radar for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Evidra has no confirmed install command yet — follow its own setup instructions.

Evidra has no declared pricing — check the project's own site. Radar is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add evidra-2 and skyhook-io-radar as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Evidra has a quality signal of 35/100 (Fair) with 3 views, 0 installs and 15 GitHub stars. Radar has 60/100 (Good) with 5 views, 0 installs and 3,908 GitHub stars.