Skip to content

MCP servers › io.github.xlsft › ymcp

MCP server · registry snapshot 2026-10-30 · last checked 2026-10-30

ymcp MCP server

Registry name io.github.xlsft/ymcp

YouTrack (ymcp) — the publisher's title

by xlsft · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

YouTrack with your login and password: the built-in tools plus deletes, sprints, history and reports — the publisher's description

4 of 4 record checks metversion 0.27.0Gostandard input/output

Summary

io.github.xlsft/ymcp is a local MCP server listed in the official MCP registry at version 0.27.0, under the namespace of the GitHub account xlsft. Its linked repository, github.com/xlsft/ymcp, belongs to the same GitHub account.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 2 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
local package
Transport
standard input/output
Your own values
a secret: YOUTRACK_PASSWORD · settings: YOUTRACK_URL, YOUTRACK_LOGIN
Package
Docker (OCI)
Repository
public
Last tested
not tested

Tool list

Not read: It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.27.0, published 2026-10-29 (registry, as of the 2026-10-30 snapshot)
First listed version
2026-10-28 (earliest version still in the registry; older removed versions would be earlier)
Version history
19 versions listed, 2026-10-28 to 2026-10-29; 19 in the 90 days before the 2026-10-30 snapshot.
Most recent 12 versions
  • 0.27.0 · 2026-10-29
  • 0.26.0 · 2026-10-29
  • 0.25.0 · 2026-10-29
  • 0.24.0 · 2026-10-29
  • 0.23.0 · 2026-10-29
  • 0.22.0 · 2026-10-29
  • 0.21.0 · 2026-10-29
  • 0.20.3 · 2026-10-29
  • 0.20.2 · 2026-10-28
  • 0.20.1 · 2026-10-28
  • 0.20.0 · 2026-10-28
  • 0.19.2 · 2026-10-28
(versions still listed in the registry only)
Registry data
snapshot 2026-10-30
Package and repository
checked 2026-10-30

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.20.2 (published 2026-10-28) → 0.27.0 (published 2026-10-29), between the registry lists of 2026-10-29 and 2026-10-30.

The publisher’s GitHub release note for v0.27.0, published 2026-10-29.

Read the release note (the publisher’s text, shown as plain text)
## What's new

### Added

- The install scripts take -v (--version, -Version on Windows) to install a given release, e.g. sh -s -- -v 0.22.0.



## Changelog
### Features
* 6c22e1746b59312cb48024bc51503ce61b5f6e76: feat(install): install a given release with -v (#71) (@xlsft)

## Install

macOS / Linux:
```sh
curl -fsSL https://raw.githubusercontent.com/xlsft/ymcp/main/install.sh | sh
```

Windows (PowerShell):
```powershell
irm https://raw.githubusercontent.com/xlsft/ymcp/main/install.ps1 | iex
```

Homebrew: `brew install xlsft/tap/ymcp` · Scoop: `scoop bucket add xlsft https://github.com/xlsft/scoop-bucket; scoop install ymcp`.

Already installed: `ymcp update`. Docker: `docker pull xlsoftware/ymcp:0.27.0`.

## Verify

`checksums.txt` is signed with [Sigstore](https://www.sigstore.dev) by this repository's release workflow:
```sh
cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
  --certificate-identity-regexp '^https://github.com/xlsft/ymcp/\.github/workflows/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
sha256sum --ignore-missing -c checksums.txt
```
Each archive has an SPDX SBOM next to it (`*.sbom.json`).

The release on GitHub

Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30; release notes from the GitHub Releases API, checked 2026-10-30.

What it is

How do I add it to my client?

Config from the registry entry

From the Docker image docker.io/xlsoftware/ymcp:0.27.0

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "ymcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YOUTRACK_URL",
        "-e",
        "YOUTRACK_LOGIN",
        "-e",
        "YOUTRACK_PASSWORD",
        "docker.io/xlsoftware/ymcp:0.27.0",
        "serve"
      ],
      "env": {
        "YOUTRACK_URL": "<YOUTRACK_URL>",
        "YOUTRACK_LOGIN": "<YOUTRACK_LOGIN>",
        "YOUTRACK_PASSWORD": "<YOUTRACK_PASSWORD>"
      }
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "ymcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YOUTRACK_URL",
        "-e",
        "YOUTRACK_LOGIN",
        "-e",
        "YOUTRACK_PASSWORD",
        "docker.io/xlsoftware/ymcp:0.27.0",
        "serve"
      ],
      "env": {
        "YOUTRACK_URL": "<YOUTRACK_URL>",
        "YOUTRACK_LOGIN": "<YOUTRACK_LOGIN>",
        "YOUTRACK_PASSWORD": "<YOUTRACK_PASSWORD>"
      }
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "ymcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YOUTRACK_URL",
        "-e",
        "YOUTRACK_LOGIN",
        "-e",
        "YOUTRACK_PASSWORD",
        "docker.io/xlsoftware/ymcp:0.27.0",
        "serve"
      ],
      "env": {
        "YOUTRACK_URL": "${input:youtrack-url}",
        "YOUTRACK_LOGIN": "${input:youtrack-login}",
        "YOUTRACK_PASSWORD": "${input:youtrack-password}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "youtrack-url",
      "description": "YOUTRACK_URL",
      "password": false
    },
    {
      "type": "promptString",
      "id": "youtrack-login",
      "description": "YOUTRACK_LOGIN",
      "password": false
    },
    {
      "type": "promptString",
      "id": "youtrack-password",
      "description": "YOUTRACK_PASSWORD",
      "password": true
    }
  ]
}
Claude Code
claude mcp add --env "YOUTRACK_URL=<YOUTRACK_URL>" "YOUTRACK_LOGIN=<YOUTRACK_LOGIN>" "YOUTRACK_PASSWORD=<YOUTRACK_PASSWORD>" --transport stdio ymcp -- docker run -i --rm -e YOUTRACK_URL -e YOUTRACK_LOGIN -e YOUTRACK_PASSWORD docker.io/xlsoftware/ymcp:0.27.0 serve
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "ymcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YOUTRACK_URL",
        "-e",
        "YOUTRACK_LOGIN",
        "-e",
        "YOUTRACK_PASSWORD",
        "docker.io/xlsoftware/ymcp:0.27.0",
        "serve"
      ],
      "env": {
        "YOUTRACK_URL": "<YOUTRACK_URL>",
        "YOUTRACK_LOGIN": "<YOUTRACK_LOGIN>",
        "YOUTRACK_PASSWORD": "<YOUTRACK_PASSWORD>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "ymcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YOUTRACK_URL",
        "-e",
        "YOUTRACK_LOGIN",
        "-e",
        "YOUTRACK_PASSWORD",
        "docker.io/xlsoftware/ymcp:0.27.0",
        "serve"
      ],
      "env": {
        "YOUTRACK_URL": "<YOUTRACK_URL>",
        "YOUTRACK_LOGIN": "<YOUTRACK_LOGIN>",
        "YOUTRACK_PASSWORD": "<YOUTRACK_PASSWORD>"
      }
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.ymcp]
command = "docker"
args = ["run", "-i", "--rm", "-e", "YOUTRACK_URL", "-e", "YOUTRACK_LOGIN", "-e", "YOUTRACK_PASSWORD", "docker.io/xlsoftware/ymcp:0.27.0", "serve"]

[mcp_servers.ymcp.env]
"YOUTRACK_URL" = "<YOUTRACK_URL>"
"YOUTRACK_LOGIN" = "<YOUTRACK_LOGIN>"
"YOUTRACK_PASSWORD" = "<YOUTRACK_PASSWORD>"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "ymcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "YOUTRACK_URL",
        "-e",
        "YOUTRACK_LOGIN",
        "-e",
        "YOUTRACK_PASSWORD",
        "docker.io/xlsoftware/ymcp:0.27.0",
        "serve"
      ],
      "env": {
        "YOUTRACK_URL": "<YOUTRACK_URL>",
        "YOUTRACK_LOGIN": "<YOUTRACK_LOGIN>",
        "YOUTRACK_PASSWORD": "<YOUTRACK_PASSWORD>"
      }
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -e "YOUTRACK_URL=<YOUTRACK_URL>" -e "YOUTRACK_LOGIN=<YOUTRACK_LOGIN>" -e "YOUTRACK_PASSWORD=<YOUTRACK_PASSWORD>" -- docker run -i --rm -e YOUTRACK_URL -e YOUTRACK_LOGIN -e YOUTRACK_PASSWORD docker.io/xlsoftware/ymcp:0.27.0 serve
  • Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
  • Replace <YOUTRACK_URL>, <YOUTRACK_LOGIN>, <YOUTRACK_PASSWORD> with your own values; the entry marks YOUTRACK_PASSWORD as secret, so keep the file out of version control.
  • Optional settings the entry also lists (left out above): YOUTRACK_PROXY, YMCP_TOOLS.
  • This runs the publisher's code on your machine (docker). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/xlsft/ymcpOpens publiclymatchesapi.github.com · 2026-10-30

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.xlsft
GitHub owner
a personal account (xlsft)
Repository
github.com/xlsft/ymcp
Stars
2
Repository age
0–30 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-30.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 2 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.xlsft/ymcp

Answered from the data above

Who publishes io.github.xlsft/ymcp?

The registry ties the namespace io.github.xlsft to the GitHub account xlsft; only its owner can publish under it. Its linked repository, github.com/xlsft/ymcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.xlsft/ymcp safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.xlsft/ymcp been security tested?

No. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.

Where is the source code of io.github.xlsft/ymcp?

In github.com/xlsft/ymcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. — the server's own choice

Required inputs the publisher declares: YOUTRACK_URL, YOUTRACK_LOGIN, YOUTRACK_PASSWORD (secret).

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-10-30; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
api.github.com · 2026-10-30
Hosting type
registry · 2026-10-30
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-10-30
Required credentials
requires a secret
registry · 2026-10-30 · no declaration is not a guarantee
Package registry
registry · 2026-10-30
Freshness
0–30 days
registry updatedAt · 2026-10-30
Lifecycle status
registry · 2026-10-30
License class
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-30
Maintenance
api.github.com · 2026-10-30
Environment
your machine
where it runs, from the hosting type · 2026-10-30

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.xlsft/ymcp: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/io.github.xlsft/ymcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.xlsft/ymcp)](https://protocolprobe.com/mcp/servers/io.github.xlsft/ymcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology