Skip to content

MCP servers › io.github.rushirb2001 › cohors

MCP server · registry snapshot 2026-11-17 · last checked 2026-11-17

cohors MCP server

Registry name io.github.rushirb2001/cohors

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

Every git repo on your machine for your agent: status, cross-repo search, tasks, opt-in git actions — the publisher's description

6 of 7 record checks metversion 0.8.21RustMITstandard input/output

Summary

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

Record checks

6 of 7 record checks met · 1 does 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 met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not checked: No known critical or high advisory in the package or its dependencies
  • #2,593 of 20,610 packages by monthly downloads, tied with 2 others
  • #2,831 of 28,859 repositories by GitHub stars, tied with 130 others

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 · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
PyPI · listed version current
License
MIT
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. 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.8.21, published 2026-11-16 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
Version history
9 versions listed, 2026-11-11 to 2026-11-16; 9 in the 90 days before the 2026-11-17 snapshot.
Most recent 9 versions
  • 0.8.21 · 2026-11-16
  • 0.8.20 · 2026-11-16
  • 0.7.7 · 2026-11-16
  • 0.7.6 · 2026-11-12
  • 0.7.5 · 2026-11-12
  • 0.7.4 · 2026-11-12
  • 0.7.2 · 2026-11-12
  • 0.7.1 · 2026-11-12
  • 0.7.0 · 2026-11-11
(versions still listed in the registry only)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. 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.7.7 (published 2026-11-16) → 0.8.21 (published 2026-11-16), between the registry lists of 2026-11-16 and 2026-11-17.

The publisher’s GitHub release note for v0.8.21 (“0.8.21 — 2026-11-16”), published 2026-11-16.

Read the release note (the publisher’s text, shown as plain text)
## Release Notes

### Fixed

- **The package pages say what is new in 0.8**, not 0.7.7, on npm, PyPI,
  crates.io and the Claude Code plugin's page: the self-updating install,
  `cohors doctor` and `cohors install`, commands named like the MCP tools,
  commands that ask before they change anything, exit codes and shell
  completions.
- **Every page's MCP setup points at the copy that keeps itself up to date**
  (`~/.local/bin/cohors`, registered for every folder with `--scope user`),
  with each channel's own path for when updates are off. The npm page no
  longer sends you to a copy npm never updates.
- **Two names in this changelog read right again**: `COHORS_NO_UPDATE` and
  `COHORS_DISABLE_UPDATES` in 0.8.0 and 0.8.1 had a date pasted into them.
  `scripts/version.sh` and `scripts/release.sh` now refuse a date run into a
  word.

## Install cohors 0.8.21

### Install prebuilt binaries via shell script

```sh
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-installer.sh | sh
```

### Install prebuilt binaries via Homebrew

```sh
brew install rushirb2001/tap/cohors
```

### Install prebuilt binaries into your npm project

```sh
npm install @cohors/cli@0.8.21
```

## Download cohors 0.8.21

|  File  | Platform | Checksum |
|--------|----------|----------|
| [cohors-aarch64-apple-darwin.tar.xz](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-aarch64-apple-darwin.tar.xz) | Apple Silicon macOS | [checksum](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-aarch64-apple-darwin.tar.xz.sha256) |
| [cohors-x86_64-apple-darwin.tar.xz](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-x86_64-apple-darwin.tar.xz) | Intel macOS | [checksum](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-x86_64-apple-darwin.tar.xz.sha256) |
| [cohors-aarch64-unknown-linux-gnu.tar.xz](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-aarch64-unknown-linux-gnu.tar.xz) | ARM64 Linux | [checksum](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-aarch64-unknown-linux-gnu.tar.xz.sha256) |
| [cohors-x86_64-unknown-linux-gnu.tar.xz](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-x86_64-unknown-linux-gnu.tar.xz) | x64 Linux | [checksum](https://github.com/rushirb2001/cohors/releases/download/v0.8.21/cohors-x86_64-unknown-linux-gnu.tar.xz.sha256) |




<!-- cohors:install-footer (added by .github/workflows/release-notes.yml from packaging/github-release/footer.md) -->

## More ways to install cohors 0.8.21

The installers above (shell, Homebrew, npm) and the downloads all come from this release. The same version is also on:

| Where | Install | How it updates |
|---|---|---|
| PyPI | `pip install cohors` | cohors updates itself, as with Homebrew and the shell installer |
| PyPI, with uv | `uvx cohors@0.8.21` | `uvx cohors@latest` always runs the newest |
| npm, as a command | `npm install -g @cohors/cli` | cohors tells you; run `npm install -g @cohors/cli@latest` |
| crates.io | `cargo install cohors --version 0.8.21` | cohors tells you; run `cargo install cohors` |
| Docker | `docker pull ghcr.io/rushirb2001/cohors:0.8.21` | Pull `:latest` or the next version tag |
| VS Code, Cursor, Windsurf, VSCodium | Search "cohors" in Extensions, or install the `.vsix` attached here | The editor updates it |
| Claude Code | `/plugin marketplace add rushirb2001/cohors`, then `/plugin install cohors@cohors` | `claude plugin update cohors@cohors` |

The VS Code extension and the Claude Code plugin both drive the `cohors` command, so install it one of the ways above first.

**As an MCP server**, register it with the absolute path (agents start servers with a stripped `PATH`): `claude mcp add cohors -- "$(which cohors)" mcp`. It starts read-only; `--allow-writes`, `--allow-run` and `--allow-launchpad` turn on git actions, commands across repos and launchpad writes.

The release on GitHub

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17; release notes from the GitHub Releases API, checked 2026-11-17.

What it is

How do I add it to my client?

Config from the registry entry

From the PyPI package cohors

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "cohors": {
      "command": "uvx",
      "args": [
        "cohors==0.8.21",
        "mcp"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "cohors": {
      "command": "uvx",
      "args": [
        "cohors==0.8.21",
        "mcp"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "cohors": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "cohors==0.8.21",
        "mcp"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"cohors","type":"stdio","command":"uvx","args":["cohors==0.8.21","mcp"]}'
Claude Code
claude mcp add --transport stdio cohors -- uvx cohors==0.8.21 mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "cohors": {
      "command": "uvx",
      "args": [
        "cohors==0.8.21",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "cohors": {
      "command": "uvx",
      "args": [
        "cohors==0.8.21",
        "mcp"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.cohors]
command = "uvx"
args = ["cohors==0.8.21", "mcp"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "cohors": {
      "command": "uvx",
      "args": [
        "cohors==0.8.21",
        "mcp"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx cohors==0.8.21 mcp
  • Optional arguments the entry also lists (left out above): --root.
  • The entry says --root can be given more than once.
  • Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
  • Optional settings the entry also lists (left out above): GITHUB_TOKEN.
  • This runs the publisher's code on your machine (uvx). 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.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.8.21
Latest stable
0.8.21
Status
current
Withdrawn
no

Source: pypi.org · 2026-11-17. About the version the registry lists; a manual install may resolve to a different one.

Integrity, provenance, license

Integrity
sha256-86270fd4e4c0804eb…
License
MIT

Source: the package registry · 2026-11-17.

Usage

Downloads
1,365 in the last month

Source: pypistats.org · 2026-11-17.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-17.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

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
Version 0.8.21 on PyPIExists and can be installedmatchesPyPI · 2026-11-17
Repository github.com/rushirb2001/cohorsOpens publiclymatchesapi.github.com · 2026-11-17

Who made it?

Feature #7 · lineage

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

Namespace
io.github.rushirb2001
GitHub owner
a personal account (rushirb2001)
Repository
github.com/rushirb2001/cohors
Stars
12
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-17; security policy read from GitHub · 2026-11-12.

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

6 of 7 record checks met · 1 does not apply · 1 not checked

  • #2,593 of 20,610 packages by monthly downloads, tied with 2 others
  • #2,831 of 28,859 repositories by GitHub stars, tied with 130 others
  • 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 metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Not checkedNo known critical or high advisory in the package or its dependenciesWe could not resolve its dependencies.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17 (security policy 2026-11-12). 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.rushirb2001/cohors

Answered from the data above

Who publishes io.github.rushirb2001/cohors?

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

Is io.github.rushirb2001/cohors safe to install?

We do not rate servers as safe or unsafe. 6 of its 7 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. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.rushirb2001/cohors been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.rushirb2001/cohors publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.8.21, the latest stable release on PyPI.

Where is the source code of io.github.rushirb2001/cohors?

In github.com/rushirb2001/cohors, 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 could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

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 at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-17
Hosting type
registry · 2026-11-17
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
registry · 2026-11-17
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
package registry · 2026-11-17
Integrity hash
declared (sha256)
package registry · 2026-11-17
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
not known (our limit)
uv could not resolve the dependency tree - our limitation
Popularity
1,365 downloads a month
package registry · 2026-11-17
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 10–99
api.github.com · 2026-11-17
Maintenance
api.github.com · 2026-11-17
Environment
your machine
where it runs, from the hosting type · 2026-11-17

“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.rushirb2001/cohors: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/io.github.rushirb2001/cohors

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: 6 of 7 record checks met

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

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, except for a server whose operator has claimed it and given permission (that server's page says so).

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