mcp-registry/io.github.atlaskos/workprotocol/list_jobs / alternatives

Live alternatives to mcp-registry/io.github.atlaskos/workprotocol/list_jobs

The best live alternatives to mcp-registry/io.github.atlaskos/workprotocol/list_jobs right now are mcp-registry/io.github.pipeworx-io/arbeitnow/list_jobs, mcp-registry/io.github.tlkc888-jenkins/joy/list_jobs, mcp-registry/io.github.pipeworx-io/remoteok/list_jobs, mcp-registry/app.himalayas/mcp/get_jobs, mcp-registry/io.github.timwal78/squeezeos/hiring_browse_jobs — capability-matched and ranked by current reliability. mcp-registry/io.github.atlaskos/workprotocol/list_jobs itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/arbeitnow/list_jobs	io.github.pipeworx-io/arbeitnow	live status →
mcp-registry/io.github.tlkc888-jenkins/joy/list_jobs	io.github.tlkc888-Jenkins/joy	live status →
mcp-registry/io.github.pipeworx-io/remoteok/list_jobs	io.github.pipeworx-io/remoteok	live status →
mcp-registry/app.himalayas/mcp/get_jobs	app.himalayas/mcp	live status →
mcp-registry/io.github.timwal78/squeezeos/hiring_browse_jobs	io.github.Timwal78/squeezeos	live status →
mcp-registry/io.jobsbase/jobs/list_filters	io.jobsbase/jobs	live status →
mcp-registry/com.100hires/100hires/hires_list_jobs	com.100hires/100hires	live status →
mcp-registry/app.himalayas/mcp/list_company_jobs	app.himalayas/mcp	live status →
mcp-registry/org.agenticsubstrate/agentic-substrate/jobs	org.agenticsubstrate/agentic-substrate	live status →
mcp-registry/email.verifly/verifly/list_jobs	email.verifly/verifly	live status →
mcp-registry/com.remotejobscenter/remote-jobs/search_remote_jobs	com.remotejobscenter/remote-jobs	live status →
mcp-registry/io.github.keploy/mcp/listJobs	io.github.keploy/mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.atlaskos/workprotocol/list_jobs?

mcp-registry/io.github.pipeworx-io/arbeitnow/list_jobs is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.tlkc888-jenkins/joy/list_jobs, mcp-registry/io.github.pipeworx-io/remoteok/list_jobs, mcp-registry/app.himalayas/mcp/get_jobs, mcp-registry/io.github.timwal78/squeezeos/hiring_browse_jobs. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.atlaskos/workprotocol/list_jobs down right now?

mcp-registry/io.github.atlaskos/workprotocol/list_jobs's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.atlaskos%2Fworkprotocol%2Flist_jobs.

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.atlaskos%2Fworkprotocol%2Flist_jobs or MCP find_alternatives. Check mcp-registry/io.github.atlaskos/workprotocol/list_jobs's live status: https://glimind.com/tool/mcp-registry/io.github.atlaskos/workprotocol/list_jobs.