foremerge — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Recheck a specific changing behavior of github.com/naw103/foremerge: Are coordination ledger revisions, destructive agent actions and migration guarantees stable after v0.5.1?

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Avoid multi-agent intent conflicts in shared repos

What we know

Foremerge pre-1.0 agent coordination project with stdio MCP server.

Maintenance / activity evidence

Foremerge v0.5.1 was released 2026-10-03.

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Pre-1.0 local MVP; coordination is local-only and schema may change. Reported action classes: Create or change coordination state and agent assignments. Complete write authority is not verified.
Authentication not yet verified.
Can coordinate proposed code changes and run trusted named verification commands; pre-1.0 schemas may change.

Can coordinate proposed code changes and run trusted named verification commands; pre-1.0 schemas may change.
Advisory/security review not completed; no safety badge.
Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

538 repository stars

Stars observed Oct 9, 2026.

Repository total for naw103/foremerge.

All limitations / Review context

Are coordination ledger revisions, destructive agent actions and migration guarantees stable after v0.5.1?

No identified material blocker to an accurately qualified public tracking entry in the limited cited evidence. This is not an installation safety certification; product-specific cautions must remain visible.

Can coordinate proposed code changes and run trusted named verification commands; pre-1.0 schemas may change.
Advisory/security review not completed; no safety badge.
Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.
Pre-1.0 local MVP; coordination is local-only and schema may change.
Reviewed write actions: Create or change coordination state and agent assignments
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Agent coordination writes may affect shared state; earlier security findings were addressed in v0.3.1 but tool permissions require review.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.
Release evidence proves attributable activity, not entire installation or tool-level safety.
Current Discovery source binding and atomic apply must be generated using MCP100 existing pipeline.
verified install or launch command
exact authentication contract
first-party data processing and retention
data retention and permission scope
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Pre-1.0 schemas may change; requires repo and local data context.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Original activity observations

Foremerge v0.5.1 was released 2026-10-03.

Technical identity

github.com/naw103/foremerge

Exact implementation source: https://github.com/naw103/foremerge ↗
Reviewed resource type: MCP Server
Repository identity: naw103/foremerge

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
naw103/foremerge
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

agent-installer

Publisher instructions with a documented client setup path.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Foremerge coordinates agents through a local CLI/MCP connection, with explicit installer and doctor.
package install · Publisher instructions
npm install -g foremerge
self hosted install or run · Publisher instructions
foremerge init
client registration · Publisher instructions
foremerge setup all
Configure / authenticate
Publisher instructions
Install Foremerge via publisher signed release install or npm install -g foremerge; `foremerge setup` configures client skills/hooks. Configuring trusted checks is a separate deliberate choice.
Check connection
Publisher instructions
Run foremerge status; do not launch check pipelines on live repo automatically.
read only local inspection · Publisher instructions
foremerge status
Remove / uninstall / revoke
MCP100 setup guide
First check `foremerge --help` for any setup removal command and undo installed hooks/skills; this command only removes global binary. Preserve repo state.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
npm uninstall -g foremerge

Official Documentation & Sources

What it does

Foremerge pre-1.0 agent coordination project with stdio MCP server.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Avoid multi-agent intent conflicts in shared repos

Representative uses

register_agent
publish_intent
conflict checking
changeset recording

Limitations

Pre-1.0 schemas may change; requires repo and local data context.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Pre-1.0 local MVP; coordination is local-only and schema may change.
Data handling: Not documented in the reviewed sources
Cost: unknown
Risk and cautions: Can coordinate proposed code changes and run trusted named verification commands; pre-1.0 schemas may change.

Access scope and cautions

Write actions: Not verified Create or change coordination state and agent assignments
Risk level: moderate
Security notes: Advisory/security review not completed; no safety badge. Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: register_agent; publish_intent; conflict checking; changeset recording.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio. Client notes: Confirm MCP tool discovery in configured local workspace. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Local SQLite/Git-based coordination; no hosted account required for local mode.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Create or change coordination state and agent assignments. Recorded permission context: Pre-1.0 local MVP; coordination is local-only and schema may change.

What limitations and risks should I check before use?

Can coordinate proposed code changes and run trusted named verification commands; pre-1.0 schemas may change. Pre-1.0 schemas may change; requires repo and local data context. Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode. Advisory/security review not completed; no safety badge. Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Agent coordination writes may affect shared state; earlier security findings were addressed in v0.3.1 but tool permissions require review. Unknown vulnerabilities and provider data handling are not certified by this public tracking review.