Synchronex
NPM · @SYNCHRONEX/MCP-PROXY · SCANNED SEP 20
Connect any AI agent to your Synchronex workspace — portable memory, decisions, and workers.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 37 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability54
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 279 tokens (~39/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "proxy_call" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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
How do I install the Synchronex MCP server?
Synchronex runs locally as an npm package, launched with npx -y @synchronex/mcp-proxy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @synchronex/mcp-proxy
claude mcp add ai-synchronex-mcp-proxy -- npx -y @synchronex/mcp-proxy
{
"mcpServers": {
"ai-synchronex-mcp-proxy": {
"command": "npx",
"args": [
"-y",
"@synchronex/mcp-proxy"
]
}
}
} {
"servers": {
"ai-synchronex-mcp-proxy": {
"command": "npx",
"args": [
"-y",
"@synchronex/mcp-proxy"
]
}
}
} codex mcp add ai-synchronex-mcp-proxy -- npx -y @synchronex/mcp-proxy
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-synchronex-mcp-proxy": {
"type": "local",
"command": [
"npx",
"-y",
"@synchronex/mcp-proxy"
],
"enabled": true
}
}
} openclaw mcp add ai-synchronex-mcp-proxy --command npx --arg -y --arg @synchronex/mcp-proxy
mcp_servers:
ai-synchronex-mcp-proxy:
command: "npx"
args: ["-y", "@synchronex/mcp-proxy"] {
"McpServers": {
"ai-synchronex-mcp-proxy": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@synchronex/mcp-proxy"
]
}
}
} assistant mcp add ai-synchronex-mcp-proxy -t stdio -c npx -a -y @synchronex/mcp-proxy
{
"mcpServers": {
"ai-synchronex-mcp-proxy": {
"command": "npx",
"args": [
"-y",
"@synchronex/mcp-proxy"
]
}
}
} 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.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 npm/@synchronex/mcp-proxy@1.2.1
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 →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
get_kernel Get Kernel ~20
Returns the local Synchronex identity kernel for the active profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_decision Log Decision ~50
Writes a local decision record to SQLite for the active profile.
| Name | Type | Req | Description |
|---|---|---|---|
| affects_products | array | – | – |
| decision | string | yes | – |
| product | string | – | – |
| reasoning | string | – | – |
No output schema declared.
No examples provided.
proxy_call Proxy Call ~38
Execute an upstream MCP tool with project-aware credential routing.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | – | – | – |
| server | string | yes | – |
| tool | string | yes | – |
No output schema declared.
No examples provided.
proxy_schema Proxy Schema ~25
Fetch the input schema for a specific upstream tool.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | – |
No output schema declared.
No examples provided.
proxy_search Proxy Search ~33
Search available upstream MCP tools from the local schema cache.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| server | string | – | – |
No output schema declared.
No examples provided.
recall Recall ~45
Full-text search over the local kernel, memories, and decisions using SQLite FTS.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| source | string | – | – |
No output schema declared.
No examples provided.
remember Remember ~68
Stores local memory in SQLite. Use scope="kernel" to set the local identity kernel, or scope="memory" for notes.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| mode | string | – | – |
| scope | string | – | – |
| tags | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
What is the Synchronex MCP server?
Synchronex is an MCP server listed in the public MCP registry as ai.synchronex/mcp-proxy. Connect any AI agent to your Synchronex workspace, portable memory, decisions, and workers. This page covers its npm package (@synchronex/mcp-proxy).
Is the Synchronex MCP server safe to use?
Synchronex scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Synchronex MCP server expose?
Synchronex exposes 7 tools: get_kernel, remember, log_decision, recall, proxy_search, and 2 more. Their descriptions and schemas cost roughly 279 tokens of context every time the server is loaded.
Is the Synchronex MCP server still maintained?
Synchronex 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.
What licence is the Synchronex MCP server under?
Synchronex declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.