io.github.Rosentic/rosentic
PYPI · ROSENTIC-MCP · SCANNED SEP 20
Deterministic cross-branch conflict detection for AI coding agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 15 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 381 tokens (~127/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.Rosentic/rosentic MCP server?
io.github.Rosentic/rosentic runs locally as a PyPI package, launched with uvx rosentic-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · rosentic-mcp
claude mcp add rosentic-rosentic -- uvx rosentic-mcp
{
"mcpServers": {
"rosentic-rosentic": {
"command": "uvx",
"args": [
"rosentic-mcp"
]
}
}
} {
"servers": {
"rosentic-rosentic": {
"command": "uvx",
"args": [
"rosentic-mcp"
]
}
}
} codex mcp add rosentic-rosentic -- uvx rosentic-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rosentic-rosentic": {
"type": "local",
"command": [
"uvx",
"rosentic-mcp"
],
"enabled": true
}
}
} openclaw mcp add rosentic-rosentic --command uvx --arg rosentic-mcp
mcp_servers:
rosentic-rosentic:
command: "uvx"
args: ["rosentic-mcp"] {
"McpServers": {
"rosentic-rosentic": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"rosentic-mcp"
]
}
}
} assistant mcp add rosentic-rosentic -t stdio -c uvx -a rosentic-mcp
{
"mcpServers": {
"rosentic-rosentic": {
"command": "uvx",
"args": [
"rosentic-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/rosentic-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 15 packages
| Packages resolved | 15 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_conflicts Check Conflicts ~181
Check a local git repository for Rosentic cross-branch conflicts. Call this before merging or after an agent edits a branch. The summary format is the normal agent-facing response. The json format returns unique findings with finding_id values for follow-up explain_conflict calls.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Base branch used for branch diffs. Defaults to main. |
| branch | – | – | Branch to check against other active branches. If omitted, the current checked-out branch is used. |
| branches | – | – | Explicit list of branch names to scan. Bypasses enumeration and age filters. Use this when you know exactly which branches to check. |
| format | string | – | Use summary for concise text. Use json only when the agent needs finding_ids or full structured findings. |
| repo_path | string | yes | Absolute or relative path to the local git repository to scan. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
explain_conflict Explain Conflict ~102
Explain one Rosentic finding and what the developer should do next. Call this after check_conflicts(format="json") when the user asks why a specific finding matters or how to resolve it. Uses the recent scan cache when available and falls back to a fresh scan.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | finding_id returned by check_conflicts with format=json. |
| repo_path | string | yes | Absolute or relative path to the local git repository that was scanned. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_branches List Branches ~70
List local branches so an agent can choose a branch before scanning. Call this when the user has not named a branch or asks what branches Rosentic can scan. Results are sorted by most recent commit date.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | Absolute or relative path to the local git repository to inspect. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the io.github.Rosentic/rosentic MCP server?
io.github.Rosentic/rosentic is an MCP server listed in the public MCP registry as io.github.Rosentic/rosentic. Deterministic cross-branch conflict detection for AI coding agents. This page covers its PyPI package (rosentic-mcp).
Is the io.github.Rosentic/rosentic MCP server safe to use?
io.github.Rosentic/rosentic scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Rosentic/rosentic MCP server expose?
io.github.Rosentic/rosentic exposes 3 tools: check_conflicts, explain_conflict, list_branches. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.
Is the io.github.Rosentic/rosentic MCP server still maintained?
io.github.Rosentic/rosentic is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.