mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score / alternatives

Live alternatives to mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score

The best live alternatives to mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score right now are mcp-registry/com.contrastcyber/api/calculate_risk_score, mcp-registry/io.tooloracle/riskoracle/methodology, mcp-registry/io.tooloracle/agentguard/tool_risk_score, mcp-registry/dev.cz-agents/dd/get_risk_score, mcp-registry/io.tooloracle/riskoracle/risk_assessment — capability-matched and ranked by current reliability. mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score itself is currently "healthy".

alternative	server
mcp-registry/com.contrastcyber/api/calculate_risk_score	com.contrastcyber/api	live status →
mcp-registry/io.tooloracle/riskoracle/methodology	io.tooloracle/riskoracle	live status →
mcp-registry/io.tooloracle/agentguard/tool_risk_score	io.tooloracle/agentguard	live status →
mcp-registry/dev.cz-agents/dd/get_risk_score	dev.cz-agents/dd	live status →
mcp-registry/io.tooloracle/riskoracle/risk_assessment	io.tooloracle/riskoracle	live status →
mcp-registry/io.tooloracle/insuranceoracle/risk_score	io.tooloracle/insuranceoracle	live status →
mcp-registry/no.firmaradar/mcp/firmaradar_get_risk_score	no.firmaradar/mcp	live status →
mcp-registry/io.github.skewing1/insurelink/get_agent_risk_score	io.github.skewing1/insurelink	live status →
mcp-registry/io.github.realmint-io/mcp/realmint_get_score	io.github.realmint-io/mcp	live status →
mcp-registry/com.stratalize/realestate/get_climate_risk_score	com.stratalize/realestate	live status →
mcp-registry/xyz.actiongate.api/actiongate/risk_score	xyz.actiongate.api/actiongate	live status →
pulsemcp/actiongate/risk_score	ActionGate	live status →

FAQ

What is the best alternative to mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score?

mcp-registry/com.contrastcyber/api/calculate_risk_score is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.tooloracle/riskoracle/methodology, mcp-registry/io.tooloracle/agentguard/tool_risk_score, mcp-registry/dev.cz-agents/dd/get_risk_score, mcp-registry/io.tooloracle/riskoracle/risk_assessment. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score down right now?

mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.lazymac2x%2Fcode-pattern-risk-scanner%2Frisk_score.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.lazymac2x%2Fcode-pattern-risk-scanner%2Frisk_score or MCP find_alternatives. Check mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score's live status: https://glimind.com/tool/mcp-registry/io.github.lazymac2x/code-pattern-risk-scanner/risk_score.