mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions

The best live alternatives to mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions right now are mcp-registry/io.github.pipeworx-io/codeforces/user_status, mcp-registry/io.github.pipeworx-io/nosdeputes-fr/list_votes, mcp-registry/io.github.pipeworx-io/flickr-public/recent, mcp-registry/io.github.pipeworx-io/urlhaus/get_recent, mcp-registry/io.github.benzatkulak-collab/socialperks/listSubmissions — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/codeforces/user_status	io.github.pipeworx-io/codeforces	live status →
mcp-registry/io.github.pipeworx-io/nosdeputes-fr/list_votes	io.github.pipeworx-io/nosdeputes-fr	live status →
mcp-registry/io.github.pipeworx-io/flickr-public/recent	io.github.pipeworx-io/flickr-public	live status →
mcp-registry/io.github.pipeworx-io/urlhaus/get_recent	io.github.pipeworx-io/urlhaus	live status →
mcp-registry/io.github.benzatkulak-collab/socialperks/listSubmissions	io.github.benzatkulak-collab/socialperks	live status →
mcp-registry/io.github.pipeworx-io/codestats/recent	io.github.pipeworx-io/codestats	live status →
mcp-registry/io.github.pipeworx-io/pangaea/recent	io.github.pipeworx-io/pangaea	live status →
mcp-registry/social.superpowers/social-superpowers/reddit-get-user-posts	social.superpowers/social-superpowers	live status →
mcp-registry/io.poolparty/main-stage-airtime/get_open_submission_calls	io.poolparty/main-stage-airtime	live status →
mcp-registry/io.github.mcpservings/paper-mcp/list_recent	io.github.MCPServings/paper-mcp	live status →
mcp-registry/io.github.pipeworx-io/codeforces/recent_actions	io.github.pipeworx-io/codeforces	live status →
mcp-registry/io.github.pipeworx-io/ai-incident-db/list_recent	io.github.pipeworx-io/ai-incident-db	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions?

mcp-registry/io.github.pipeworx-io/codeforces/user_status is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nosdeputes-fr/list_votes, mcp-registry/io.github.pipeworx-io/flickr-public/recent, mcp-registry/io.github.pipeworx-io/urlhaus/get_recent, mcp-registry/io.github.benzatkulak-collab/socialperks/listSubmissions. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions down right now?

mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fleetcode%2Fuser_recent_submissions.

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.pipeworx-io%2Fleetcode%2Fuser_recent_submissions or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/leetcode/user_recent_submissions.