mcp-registry/io.github.pipeworx-io/jira/jira_get_issue / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/jira/jira_get_issue

The best live alternatives to mcp-registry/io.github.pipeworx-io/jira/jira_get_issue right now are mcp-registry/io.github.jcjamet/ia-qa-toolbox/fetch_jira_issue, mcp-registry/dev.metamesh-uga/metamesh-uga/jira, mcp-registry/io.github.pipeworx-io/linear/linear_get_issue, mcp-registry/io.github.pipeworx-io/gitlab/gitlab_list_issues, mcp-registry/io.github.jcjamet/ia-qa-toolbox/jira_to_test_suite — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/jira/jira_get_issue itself is currently "healthy".

alternative	server
mcp-registry/io.github.jcjamet/ia-qa-toolbox/fetch_jira_issue	io.github.JcJamet/ia-qa-toolbox	live status →
mcp-registry/dev.metamesh-uga/metamesh-uga/jira	dev.metamesh-uga/metamesh-uga	live status →
mcp-registry/io.github.pipeworx-io/linear/linear_get_issue	io.github.pipeworx-io/linear	live status →
mcp-registry/io.github.pipeworx-io/gitlab/gitlab_list_issues	io.github.pipeworx-io/gitlab	live status →
mcp-registry/io.github.jcjamet/ia-qa-toolbox/jira_to_test_suite	io.github.JcJamet/ia-qa-toolbox	live status →
mcp-registry/io.github.pipeworx-io/gitlab-public/search_issues	io.github.pipeworx-io/gitlab-public	live status →
mcp-registry/io.github.atlaskos/workprotocol/get_job	io.github.Atlaskos/workprotocol	live status →
mcp-registry/io.github.pipeworx-io/linear/linear_list_issues	io.github.pipeworx-io/linear	live status →
mcp-registry/io.github.rationalbloks/rationalbloks-mcp/get_project	io.github.rationalbloks/rationalbloks-mcp	live status →
mcp-registry/io.github.pipeworx-io/asana/asana_get_task	io.github.pipeworx-io/asana	live status →
mcp-registry/md.install/try/get_project_details	md.install/try	live status →
mcp-registry/io.github.pipeworx-io/gitlab-public/get_project	io.github.pipeworx-io/gitlab-public	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/jira/jira_get_issue?

mcp-registry/io.github.jcjamet/ia-qa-toolbox/fetch_jira_issue is the top capability-matched alternative that's live right now. Other options: mcp-registry/dev.metamesh-uga/metamesh-uga/jira, mcp-registry/io.github.pipeworx-io/linear/linear_get_issue, mcp-registry/io.github.pipeworx-io/gitlab/gitlab_list_issues, mcp-registry/io.github.jcjamet/ia-qa-toolbox/jira_to_test_suite. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/jira/jira_get_issue down right now?

mcp-registry/io.github.pipeworx-io/jira/jira_get_issue's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fjira%2Fjira_get_issue.

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%2Fjira%2Fjira_get_issue or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/jira/jira_get_issue's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/jira/jira_get_issue.