Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow-up value is specific to Synchronex project credential routing and local memory: Do encrypted vault and profile selection prevent credentials from crossing project boundaries during upstream calls?
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Portable shared memory, decisions, workers and approval-oriented operating context across AI agents.
What we know
Synchronex positions itself as an AI command center where memory, workers, brand/context and approvals live in one operating layer. The npm MCP proxy connects clients to that workspace.
Maintenance / activity evidence
- @synchronex/mcp-proxy 1.2.1 published 2026-08-13T21:29:17.345Z
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Memory/decision/worker access and potential workflow actions. Complete write authority is not verified.
- Authentication not yet verified.
- Sensitive access: Business strategy, Brand kernel, Worker outputs, Decisions
- Broad business memory plus worker actions can be sensitive; tool-level write boundaries need confirmation.
Full authority, access and evidence limits are available in Review context and Access & risk.
All limitations / Review context
Do encrypted vault and profile selection prevent credentials from crossing project boundaries during upstream calls?
The bounded review of the publisher's documented Synchronex project credential routing and local memory and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.
- Broad business memory plus worker actions can be sensitive; tool-level write boundaries need confirmation.
- Memory/decision/worker access and potential workflow actions.
- Workspace memory, decisions, brand context and worker output are handled by Synchronex.
- Sensitive access: Business strategy, Brand kernel, Worker outputs, Decisions
- 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.
- Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
- Documented tool authority and any remote data handling must be checked before installation or use.
- Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
- exact MCP auth env
- full tool inventory
- specific write actions
- retention/privacy
- Exact MCP tool surface and auth variables were not recovered from first-party package docs.
- Workspace may contain broad founder/business context.
- Official site emphasizes approval before shipping, but enforcement details must be checked per tool.
Original activity observations
- @synchronex/mcp-proxy 1.2.1 published 2026-08-13T21:29:17.345Z
Technical identity
npm/@synchronex/mcp-proxy- Exact implementation source
- https://www.npmjs.com/package/@synchronex/mcp-proxy ↗
- Reviewed resource type
- Gateway
- Repository identity
- kmdesle/synchronex
- Package identity
- npm:@synchronex/mcp-proxy
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- Package registry metadata ↗
@synchronex/mcp-proxy
Recorded package identity, distribution or download evidence.
- Evidence source ↗
synchronex.ai/
Source material retained for this review.
Includes references whose attribution is not established.
- GitHub repository ↗
kmdesle/synchronex
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Setup · Watchlist
Gateway setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect gateway
Publisher instructionsPublisher confirms credential-aware MCP proxy and local memory tools, but its npm README does not give a first-party exact launcher. A THIRD-PARTY client directory lists npx -y @synchronex/mcp-proxy@1.1.0; current npm release is 1.2.1, so do not present that as publisher-verified for current version.
Configure / authenticate
MCP100 setup guideSynchronex mcp-proxy is a credential-aware proxy/integration. Hosted vault credentials and monitoring endpoint are distinct from local CLI launch; do not claim zero-config generic stdio.
Check connection
Suggested checkUser-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guideGeneric client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.
Official Documentation & Sources
What it does
Synchronex positions itself as an AI command center where memory, workers, brand/context and approvals live in one operating layer. The npm MCP proxy connects clients to that workspace.
- Capability
- Files & Knowledge
- Resource type
- Gateway
- Best fit
- Portable shared memory, decisions, workers and approval-oriented operating context across AI agents.
Representative uses
- Read/write portable workspace memory
- Access recorded decisions/context
- Invoke or coordinate Synchronex workers
- Use approval state before shipping work
Limitations
- Exact MCP tool surface and auth variables were not recovered from first-party package docs.
- Workspace may contain broad founder/business context.
- Official site emphasizes approval before shipping, but enforcement details must be checked per tool.
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
- Memory/decision/worker access and potential workflow actions.
- Data handling
- Workspace memory, decisions, brand context and worker output are handled by Synchronex.
- Cost
- plan_based
- Risk and cautions
- Broad business memory plus worker actions can be sensitive; tool-level write boundaries need confirmation.
Access scope and cautions
- Write actions
- Not verified
- Sensitive access
- Business strategy Brand kernel Worker outputs Decisions
- Risk level
- high
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-08. Watchlist tracking is not a recommendation or a security certification.