mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback / alternatives

Live alternatives to mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback

The best live alternatives to mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback right now are mcp-registry/io.github.wowcool/agentsafe/submit_feedback, mcp-registry/com.senzing/mcp/submit_feedback, mcp-registry/io.github.valuein/mcp-sec-edgar/submit_feedback, mcp-registry/io.github.parallect/prxhub/session_feedback, mcp-registry/com.decision-anchor/da/submit_feedback — capability-matched and ranked by current reliability. mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback itself is currently "healthy".

alternativeserver
mcp-registry/io.github.wowcool/agentsafe/submit_feedbackio.github.wowcool/agentsafelive status →
mcp-registry/com.senzing/mcp/submit_feedbackcom.senzing/mcplive status →
mcp-registry/io.github.valuein/mcp-sec-edgar/submit_feedbackio.github.valuein/mcp-sec-edgarlive status →
mcp-registry/io.github.parallect/prxhub/session_feedbackio.github.parallect/prxhublive status →
mcp-registry/com.decision-anchor/da/submit_feedbackcom.decision-anchor/dalive status →
mcp-registry/io.github.agentlinehq/agentline/submit_feedbackio.github.AgentLineHQ/agentlinelive status →
mcp-registry/io.github.planexeorg/planexe/send_feedbackio.github.PlanExeOrg/planexelive status →
mcp-registry/io.sentinelsignal/scoring/submit_feedbackio.sentinelsignal/scoringlive status →
mcp-registry/io.github.openaccountants/openaccountants/submit_skill_verdictio.github.openaccountants/openaccountantslive status →
mcp-registry/ai.fodda/mcp-server/send_feedbackai.fodda/mcp-serverlive status →
mcp-registry/co.superforms/superforms/create_feedback_formco.superforms/superformslive status →
mcp-registry/ai.kifly/mcp/submit_feedbackai.kifly/mcplive status →

FAQ

What is the best alternative to mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback?

mcp-registry/io.github.wowcool/agentsafe/submit_feedback is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.senzing/mcp/submit_feedback, mcp-registry/io.github.valuein/mcp-sec-edgar/submit_feedback, mcp-registry/io.github.parallect/prxhub/session_feedback, mcp-registry/com.decision-anchor/da/submit_feedback. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback down right now?

mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fdev.aic0rt3x.memory%2Fmcp%2Fsubmit_exit_feedback.

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%2Fdev.aic0rt3x.memory%2Fmcp%2Fsubmit_exit_feedback or MCP find_alternatives. Check mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback's live status: https://glimind.com/tool/mcp-registry/dev.aic0rt3x.memory/mcp/submit_exit_feedback.