Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Remogram

NPM · @REMOGRAM/MCP

SCM & forge boundary MCP: normalized, typed JSON from attributed Gitea, GitLab, and GitHub providers

Available components

0 this week 76 Trust /100

Last scanned (4 hours ago)

Scores higher than 53% of npm servers

Category Version Control

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2395 tokens (~59/item across 40 items; 40 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% of tool parameters carry a description.Partial
Tool Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 2 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_plan" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 40 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 17 Oct 26 +3
    • Stability: 0.83 → pass security
Diagnostics

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 5 Nov 2026 · Analysed npm/@remogram/mcp@0.2.0-beta.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 100 packages
Packages resolved 100
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 40 exposed · ~2,395 tokens

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 →

Tool Tokens
attestation_read ~33

Read commit status attestation bindings for a SHA.

NameTypeReqDescription
contextstring––
shastringyes–

No output schema declared.

No examples provided.

branch_protection ~32

Branch protection policy facts: required status contexts, protected rules, approvals signal.

NameTypeReqDescription
branch_refstringyes–

No output schema declared.

No examples provided.

command_contract_export ~37

Read command contract metadata for all commands or one command key.

NameTypeReqDescription
commandstring–Optional command key, for example "issue inventory"

No output schema declared.

No examples provided.

cr_body ~24

Change request description body with close_keywords helper.

NameTypeReqDescription
numberintegeryes–

No output schema declared.

No examples provided.

cr_close ~76

Close an open change request on the configured forge without merging.

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
idempotency_keystring––
numberintegeryes–
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)

No output schema declared.

No examples provided.

cr_comments ~30

Review comments for a change request (sanitized bodies, truncation-aware).

NameTypeReqDescription
numberintegeryes–

No output schema declared.

No examples provided.

cr_edit ~98

Update change request title and/or body on the configured forge.

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
bodystring––
body_filestring––
idempotency_keystring––
numberintegeryes–
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)
titlestring––

No output schema declared.

No examples provided.

cr_files ~29

Changed file paths for a change request (bounded, truncation-aware).

NameTypeReqDescription
numberintegeryes–

No output schema declared.

No examples provided.

cr_inventory ~87

Aggregate open change requests with checks and merge-plan facts into a semantic-diff slice.

NameTypeReqDescription
cursorstring–Opaque cursor from prior cr_inventory next_cursor
limitinteger–Max open CR entries (default 3)
slice_refstring–Optional slice ref label for consumers
sortstring–Open-list slice sort preset (default number_asc)

No output schema declared.

No examples provided.

cr_open ~204

Open a change request (pull request) on the configured forge.

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
basestringyesBase branch ref
bodystring–Optional change request body
body_filestring–Path to body file (mutually exclusive with body); use - for stdin
dedupe_keystring–Durable cross-process dedupe key (24h XDG store)
headstringyesHead branch ref
idempotencystring–Idempotency scan mode when forge open-pull scan is incomplete
idempotency_keystring–Optional agent idempotency key for retry-safe writes
repostring–Override forge repo as owner/name on the same host
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)
titlestringyesChange request title

No output schema declared.

No examples provided.

doctor ~44

Read-only provider readiness diagnostics for config, remote trust, auth, capabilities, and checks.

NameTypeReqDescription
liveboolean–When true, perform a bounded live forge API reachability probe

No output schema declared.

No examples provided.

forge_changes ~115

Forge activity events since an observed_at boundary (PR lifecycle, head SHA moves, check conclusions).

NameTypeReqDescription
cursorstring–Opaque cursor from prior forge_changes next_cursor
include_issuesboolean–Include issue open/close lifecycle events
limitinteger–Events per page (default 64)
log_pathstring–Override forge event log path
sincestring–ISO-8601 observed_at boundary (required on first page)
sourcestring–Event source preference

No output schema declared.

No examples provided.

forge_log_ingest ~48

Ingest a Gitea webhook JSON payload into the local forge event log.

NameTypeReqDescription
filestring––
log_pathstring––
stdinboolean––

No output schema declared.

No examples provided.

forge_log_read ~41

Read normalized events from the local forge event log.

NameTypeReqDescription
limitinteger––
log_pathstring––
sincestringyes–

No output schema declared.

No examples provided.

forge_queue_snapshot ~65

Composed forge queue snapshot (repo status, CR slice, merge summaries).

NameTypeReqDescription
base_refstring––
cr_limitinteger––
include_issuesboolean––
include_refsboolean––
integration_refstring––

No output schema declared.

No examples provided.

issue_bundle ~58

Create an issue_bundle packet for issue lifecycle and linked review context.

NameTypeReqDescription
issue_numberintegeryes–
linked_printeger––
statestring––
titlestring––
urlstring––

No output schema declared.

No examples provided.

issue_close ~74

Close an open forge issue on the configured repository.

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
idempotency_keystring––
numberintegeryes–
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)

No output schema declared.

No examples provided.

issue_comment ~87

Post a comment on a forge issue.

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
bodystring––
body_filestring––
idempotency_keystring––
numberintegeryes–
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)

No output schema declared.

No examples provided.

issue_comments ~26

Issue comments (sanitized bodies, truncation-aware).

NameTypeReqDescription
numberintegeryes–

No output schema declared.

No examples provided.

issue_inventory ~85

Aggregate open issues into a semantic-diff inventory slice with pagination cursors.

NameTypeReqDescription
cursorstring–Opaque cursor from prior issue_inventory next_cursor
limitinteger–Max open issue entries (default 3)
slice_refstring–Optional slice ref label for consumers
sortstring–Open-list slice sort preset (default number_asc)

No output schema declared.

No examples provided.

issue_open ~139

Open a forge issue on the configured repository (Gitea v1).

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
bodystring–Optional issue body (inline cap; use body_file for larger bodies)
body_filestring–Path to body file for bodies above inline cap (mutually exclusive with body); use - for stdin
idempotency_keystring–Optional agent idempotency key for retry-safe writes
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)
titlestringyesIssue title

No output schema declared.

No examples provided.

issue_view ~25

Issue metadata facts with optional linked change request snapshot.

NameTypeReqDescription
numberintegeryes–

No output schema declared.

No examples provided.

merge_execute ~116

Execute a forge merge for an open change request after SHA-bound preflight.

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
expected_base_shastringyesExpected base SHA (40 hex chars)
expected_head_shastringyesExpected head SHA (40 hex chars)
methodstring–Merge method (v1: merge only)
numberintegeryes–
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)

No output schema declared.

No examples provided.

merge_plan ~34

Merge readiness facts: mergeability, checks, blockers.

NameTypeReqDescription
allowed_pathsarray––
numberintegeryes–

No output schema declared.

No examples provided.

observer_snapshot ~53

Deprecated alias for forge_queue_snapshot — prefer forge_queue_snapshot.

NameTypeReqDescription
cr_limitinteger––
include_issuesboolean––
include_refsboolean––
integration_refstring––

No output schema declared.

No examples provided.

plugin_boundary ~24

Read forge plugin boundary metadata (emit surfaces, denied claims, contract export linkage).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pr_checks ~19

CI/check conclusions for a PR number or git ref.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pr_status ~22

PR metadata and mergeability facts.

NameTypeReqDescription
numberintegeryes–

No output schema declared.

No examples provided.

provider_capabilities ~46

Structured provider capability facts for commands, auth, checks, host binding, pagination, and write support.

NameTypeReqDescription
repostring–Override forge repo as owner/name on the same host

No output schema declared.

No examples provided.

publish_execute ~51

Push a local branch to the configured git remote (requires publish_branch write_commands).

NameTypeReqDescription
headstringyesLocal branch name to publish
remotestring–Git remote (must match configured config.remote)

No output schema declared.

No examples provided.

publish_plan ~49

Plan branch publication to the configured git remote before opening a change request.

NameTypeReqDescription
headstringyesLocal branch name to publish
remotestring–Git remote (must match configured config.remote)

No output schema declared.

No examples provided.

ref_compare ~56

Compare two refs with exact SHAs and ahead/behind counts.

NameTypeReqDescription
basestringyesBase ref
headstringyesHead ref
repostring–Override forge repo as owner/name on the same host

No output schema declared.

No examples provided.

ref_inventory ~41

List repository refs with SHAs, default branch hint, and optional ancestry hints.

NameTypeReqDescription
repostring–Override forge repo as owner/name on the same host

No output schema declared.

No examples provided.

repo_status ~37

Forge repo status facts (auth, capabilities, default branch).

NameTypeReqDescription
repostring–Override forge repo as owner/name on the same host

No output schema declared.

No examples provided.

review_bundle ~63

Create a review_bundle packet for reviewed head/base, decision, and summary facts.

NameTypeReqDescription
decisionstring––
numberintegeryes–
reviewed_base_shastring––
reviewed_head_shastring––
summarystring––

No output schema declared.

No examples provided.

semantic_diff ~20

Composed semantic diff since a time or git ref boundary.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

status_set ~185

Set a commit status (check context) on the configured forge.

NameTypeReqDescription
actor_idstring–Caller actor id; requires session_id when set
contextstringyesStatus context name
descriptionstring–Optional status description
idempotency_keystring–Optional agent idempotency key for retry-safe writes
notestring–Additional attestation note
proof_hashstring–Attestation proof hash (sha256:...)
proof_urlstring–Attestation proof URL
session_idstring–Caller session id; requires actor_id when set (untrusted correlation only)
shastringyes40-character commit SHA
statestringyesStatus state
target_urlstring–Optional target URL for the status
verifierstring–Verifier identity label

No output schema declared.

No examples provided.

sync_plan ~26

Local vs remote sync facts and divergent-remote blockers.

NameTypeReqDescription
remotestring––

No output schema declared.

No examples provided.

verify_bind ~71

Create a verify_bind packet bound to a target SHA and optional proof metadata.

NameTypeReqDescription
notestring–Optional verification notes
proof_urlstring–Verification proof URL
target_shastringyes40-character verified target SHA
verifierstring–Verifier identity or lane label

No output schema declared.

No examples provided.

whoami ~25

Authenticated forge identity facts (login, can_write, token scope/expiry signals).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Remogram MCP server?

Remogram runs locally as an npm package, launched with npx -y @remogram/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @remogram/mcp

# add to Claude Code
claude mcp add attebury-remogram -- npx -y @remogram/mcp
Common questions

What is the Remogram MCP server?

Remogram is an MCP server listed in the public MCP registry as io.github.attebury/remogram. SCM & forge boundary MCP: normalized, typed JSON from attributed Gitea, GitLab, and GitHub providers. This page covers its npm package (@remogram/mcp).

Is the Remogram MCP server safe to use?

Remogram scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Remogram MCP server expose?

Remogram exposes 40 tools: doctor, provider_capabilities, repo_status, ref_compare, ref_inventory, and 35 more. Their descriptions and schemas cost roughly 2,395 tokens of context every time the server is loaded.

Is the Remogram MCP server still maintained?

Remogram is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Remogram MCP server under?

Remogram declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.