MCP servers › io.github.rubtsov-stan › rift-mcp
MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19
rift-mcp MCP server
Registry name io.github.rubtsov-stan/rift-mcp
Rift — the publisher's title
by rubtsov-stan · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗
Diff two huge text files under a fixed memory limit: summary, hunks and the next difference. — the publisher's description
Summary
io.github.rubtsov-stan/rift-mcp is a local MCP server listed in the official MCP registry at version 0.4.0, under the namespace of the GitHub account rubtsov-stan. Its linked repository, github.com/rubtsov-stan/rift, belongs to the same GitHub account.
Record checks
5 of 5 record checks met · 4 do not apply
- 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
- met: 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: 1 star (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 · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- MCP bundle
- 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.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.4.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-18 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-11-18 to 2026-11-19; 2 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.4.0· 2026-11-190.3.4· 2026-11-18
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
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.3.4 (published 2026-11-18) → 0.4.0 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.
The publisher’s GitHub release note for v0.4.0 (“0.4.0 - 2026-11-19”), published 2026-11-19.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
## Release Notes ### Added - `rift A B` on two directories compares the trees, as `diff -r` prints them: files only in one tree, a unified diff per changed file under a `diff -r` header, `Binary files ... differ` for files with a NUL in their first 8 KiB, and `Renamed:` for a file moved with its content unchanged. Symbolic links are compared by target and never followed. `--summary` lists one status per path and the counts. The whole run stays under `--mem`; one directory's listing must fit in a quarter of it, about 2 million entries at the default `256M`, or the run is refused with a limit to rerun with. - `rift --key --show-fields` prints under each changed key the fields that differ, one per line: ` price: 10 -> 12`. Fields are CSV columns named by the header (numbered for `csv:N`), top-level NDJSON members, or `COPY` columns. Values are cut at 64 bytes with `...`, and `(none)` marks a field one record lacks. - `--fields a,b` compares only the named fields and implies `--show-fields`: a key whose other fields changed is not printed and does not count for the exit status. - `rift-mcp` has two tools for key mode. `keyed_summary` counts the keys added, removed and changed between two files and lists the first ten of each kind. `keyed_changes` returns a page of the changed keys with both records and, for a changed key, the fields that differ, a page at a time by an opaque `cursor`: one from another call, or after a file changed, is refused with a message to start again. A key from a `pg_dump` carries its `COPY` table as a `table` field. `key` takes the CLI's `csv:NAME`, `csv:N`, `json:PATH` and `copy:NAME`, and errors use the CLI's wording, a budget refusal ending in `rerun with --mem`. A keyed run counts its `mem` in the server's 512 MiB total and takes one of its four slots, but is not kept between calls: each page reruns the whole comparison, and a `mem` under about 260K to 400K, depending on the pair, is refused (caching is #89). - Each `.deb`, `.vsix` and `.mcpb` in a release has a `<file>.sha256` next to it, in the format of the archives' checksums: `sha256.sum` lists only the files `dist` builds (#69). - `bench/compare.sh BASE HEAD SCRATCH` builds two refs, runs them interleaved on fixed generated pairs, checks that their outputs match and prints the medians, spreads, peak heap and load as a table. ### Changed - Output change: with `--key copy:NAME`, every key line names its table before the key, `~public.item:1` instead of `~1`, in every output mode, so the same key in two tables no longer prints as the same line. Scripts that parse `COPY` key lines must strip the new prefix. A colon in the table name prints as `\:`. Duplicate-key errors name the table too: `duplicate keys: public.item:7`. CSV and NDJSON output is unchanged. In `rift-core`, `KeyedChange` gains a `table` field and `KeyError::Duplicate` lists `TableKey` values. - A directory given with a file is refused with `give two files or two directories` (exit 2) instead of `not a regular file`. - `rift serve` waits up to 5 seconds for room, at most four calls at a time, before it answers busy, but only for a client that declares `capabilities.retry_after` in `initialize`. Other clients keep the immediate busy answer. `initialize` ignores a capability it does not know and refuses a known one of the wrong type. ### Fixed - `--key csv:` on a file whose last record leaves a quote open and that ends in a lone CR reported that record as changed against the same file without the CR, and kept the line breaks in the key when the quote was in the key column. The final CR now counts as a line break, as it does outside quotes, and such files compare equal. - Key mode gave its threads' memory back to the budget before the threads had exited, so a few KiB they allocated on the way out counted against no reservation, and under `rift serve` or the MCP server against the next
Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
How do I add it to my client?
Config from the registry entry
- No config: the MCP bundle is a file to install in a client that supports bundles, not a command.
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.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Bundle platforms (MCPB). The bundle lists platforms darwin and linux (manifest.json compatibility). Source: read 2026-11-19.
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. 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-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Own host
- security.txt. No security.txt at https://rubtsov-stan.github.io/.well-known/ (HTTP 404, 2026-11-19). Source: rubtsov-stan.github.io/.well-known/security.txt · read 2026-11-19.
- A2A agent card. No A2A agent card at https://rubtsov-stan.github.io/.well-known/ (HTTP 404, 2026-11-19). Source: rubtsov-stan.github.io/.well-known/agent-card.json · read 2026-11-19.
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 #6The 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 says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/rubtsov-stan/rift | Opens publicly | matches | api.github.com · 2026-11-19 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.rubtsov-stan
- GitHub owner
- a personal account (rubtsov-stan)
- Repository
- github.com/rubtsov-stan/rift
- Stars
- 1
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-18.
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 rating5 of 5 record checks met · 4 do not apply
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 1 star (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.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- 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-11-19 (security policy 2026-11-18). 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.rubtsov-stan/rift-mcp
Answered from the data aboveWho publishes io.github.rubtsov-stan/rift-mcp?
The registry ties the namespace io.github.rubtsov-stan to the GitHub account rubtsov-stan; only its owner can publish under it. Its linked repository, github.com/rubtsov-stan/rift, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.rubtsov-stan/rift-mcp safe to install?
We do not rate servers as safe or unsafe. 5 of its 5 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.rubtsov-stan/rift-mcp 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.rubtsov-stan/rift-mcp publish a security policy?
Yes: its repository has a public security policy (github.com/rubtsov-stan/rift/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Where is the source code of io.github.rubtsov-stan/rift-mcp?
In github.com/rubtsov-stan/rift, which opens publicly.
Found this page useful?
Anonymous · no sign-inA 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 #1It 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.
“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.rubtsov-stan/rift-mcp: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.rubtsov-stan/rift-mcp
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
[](https://protocolprobe.com/mcp/servers/io.github.rubtsov-stan/rift-mcp)
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