cloud1
cloud2
cloud3
cloud4
cloud5
cloud6
Codex plugin
Syndu Codex Plugin
← Back to platform brief
Codex plugin

Syndu Codex Plugin

Download the installable Syndu Codex plugin, add it to a local Codex marketplace, and give Codex a hosted cyber-and-fraud investigation surface with governed memory and share-safe hive reuse.

Download plugin Open Access Open MCP page
Install by prompt

Paste this into Codex in the workspace where you want Syndu installed

This exact prompt worked once the plugin bundle lived inside the workspace and the marketplace used a relative `./plugins/syndu` path.

Codex, visit https://syndu.com/pages/resources/codex-plugin/ and install the Syndu plugin on my environment.
Download into this workspace Keep the plugin at ./plugins/syndu Connect on first use
Documentation index Platform brief Quota rules Privacy FAQ
Current bundle
v0.1.6 · 22 KB

Stable zip with the plugin manifest, hosted MCP config, bundled skills, install docs, and a ready-to-edit marketplace template.

Download zip
Connection model
Install first, connect on first use

Codex installs the local plugin shell first, then opens Syndu's browser-based OAuth flow when the user makes the first live request.

Install path
./plugins/syndu

Put the unpacked plugin inside the workspace. Codex accepts relative local plugin paths and rejects absolute ones for marketplace installs.

Hosted endpoint
https://syndu.com/mcp/

The plugin points at Syndu's hosted MCP endpoint, so the buyer installs a bundle instead of running a bridge.

Power-user fallback
Manual MCP key stays available

Create a workspace MCP key in Access if you want direct bearer auth for scripts, alternate MCP clients, or persistent shell setup.

Provision key

What The Download Includes

The bundle should feel complete when it lands on disk: plugin manifest, MCP endpoint, packaged skills, install docs, and the marketplace template that shortens setup.

Bundle contents

Plugin shell plus hosted MCP config

The zip includes the Codex plugin manifest, the hosted Syndu MCP endpoint definition, investigation skills, validation scripts, and install docs.

.codex-plugin/plugin.json .mcp.json Bundled skills Smoke test and validator
Marketplace template

Fastest tested local install

The download includes a ready-to-edit marketplace template. The plugin should live inside the workspace and the marketplace path should stay relative, which is the shape Codex accepted in the install test.

{
  "name": "syndu-local",
  "interface": {"displayName": "Syndu Local"},
  "plugins": [
    {
      "name": "syndu",
      "source": {
        "source": "local",
        "path": "./plugins/syndu"
      },
      "policy": {"installation": "AVAILABLE", "authentication": "ON_USE"},
      "category": "Research"
    }
  ]
}
Keep the path relative Reopen Plugins if needed Install from Plugins tab
Connection contract

OAuth-first with key fallback

The recommended flow is browser-based connection on first use. Manual MCP keys remain available for alternate MCP clients, shell persistence, and troubleshooting.

Connect in browser on first live request Access dashboard provisions MCP keys SYNDU_MCP_TOKEN remains optional
What users get

Investigate, explain, and remember

Once installed, Codex can resolve risky identifiers, explain contextual risk, find related entities, and preserve outcomes in governed workspace memory and the hive mind.

Cyber and fraud workflows Governed workspace memory Approved hive reuse

Why Start With The Codex Plugin

This is the fastest public path into Syndu's agent workflow: download one bundle, install it locally, connect the workspace, then investigate and preserve outcomes without building any middleware.

Codex plugin

Public install path with real product visibility

A dedicated Codex plugin page gives Syndu a visible installation surface, not just an MCP endpoint buried inside deeper documentation. Visitors can understand what the plugin does, download it immediately, and install it with a tested local marketplace pattern.

Codex plugin

Hosted investigation surface, not a local bridge project

The plugin ships with Syndu's hosted MCP endpoint already defined. That keeps the install story clean for cyber and fraud teams that want outside-in context and memory without standing up extra infrastructure.

Codex plugin

Browser-based workspace connection by default

The default connection model is browser-based OAuth on first use. That lets the plugin install stay light while the real workspace connection happens only when the user actually invokes Syndu inside Codex.

Codex plugin

Manual keys still support scripts and power users

Manual MCP credentials remain available for raw MCP clients, shell-based testing, and persistent operator environments. That fallback is useful, but it should not be the main onboarding story for plugin discovery.

Codex plugin

Memory and hive mind are part of the product promise

The plugin is not just a lookup shim. It is how Codex reaches Syndu's governed memory layer so analysts and agents can preserve approved outcomes and reuse them safely across future runs.

Open The Right Surface

A cold visitor should be able to move from the download into the right follow-on surface without hunting through the rest of the site.

Current zip

Download plugin

syndu-v0.1.6-codex-plugin.zip

Download the current installable plugin bundle directly from Syndu.

Stable bundle name Local plugin install Current published version
Open document
Access dashboard

Provision workspace access

/access/

Create the account, manage the workspace, and provision an MCP key when you need direct bearer-token fallback.

Sign up or sign in Create MCP credential Copy shell export command
Open document
Product surface

Read the MCP server page

/pages/resources/mcp-server/

See the hosted MCP endpoint, tool surface, pricing ladder, and governed memory model that sit behind the plugin.

Hosted endpoint Tool catalog MCP pricing and governance
Open document
Use cases

Explore Codex-ready workflows

/pages/resources/mcp-use-cases/

Jump into the buyer workflows that make the plugin easy to understand: IP and domain investigation, detection drafting, and fraud review.

Cyber investigation Detection drafting Fraud and account-abuse review
Open document

Recommended Connection Paths

The public plugin should prefer the lightest credible install path, while still leaving room for power-user operation.

Recommended

Browser connect on first use

Best for most plugin installs because the user downloads the bundle, installs it, and completes workspace auth only when Syndu is actually invoked.

No manual secret handling up front Best fit for plugin discovery Keeps install friction low
Optional fallback

Manual MCP key

Best for scripts, raw MCP clients, smoke tests, and operators who want to preserve Syndu auth directly in the shell that launches Codex.

Provision in Access Export SYNDU_MCP_TOKEN Useful for direct MCP troubleshooting
Product value

Governed memory and hive reuse

Install is only the first step. The real buyer value is that Codex can carry approved findings forward instead of repeating the same first investigation every time.

Workspace memory is included Approved hive sharing is governed Cyber and fraud workflows stay in one loop

Download, Install, Connect

This is the fastest stable install sequence for someone discovering Syndu on the public website today.

01

Download the current bundle

Grab the latest Syndu Codex plugin zip from this page so the buyer starts from a packaged local plugin rather than raw docs or repo instructions.

02

Unzip it into this workspace

Expand the bundle inside the repo or workspace where Codex will run, so the plugin lands at `./plugins/syndu` and stays local to the environment you are configuring.

03

Point Codex at the relative plugin path

Use the bundled marketplace template as `.agents/plugins/marketplace.json` and keep the source path relative, for example `./plugins/syndu`. Codex rejected absolute local plugin paths in the install rehearsal.

04

Install Syndu in the Plugins tab

Open the Plugins tab, switch to the Syndu Local marketplace, and install Syndu just like any other local plugin bundle. If the marketplace does not appear immediately, reopen the tab or restart Codex once.

05

Invoke Syndu and connect the workspace

The first live request opens Syndu's browser-based connect flow so the user can sign in, accept terms if needed, and connect the workspace cleanly.

06

Optional: provision an MCP key

If the user wants direct bearer auth for scripts or persistent operator shells, they can create an MCP key in Access and set SYNDU_MCP_TOKEN manually.

Copy-Ready Install Snippets

Give operators the fewest moving parts possible: download, unpack, add marketplace metadata, then connect Syndu.

bash

Download and unpack locally

mkdir -p ./plugins ./.agents/plugins
curl -L -o syndu-v0.1.6-codex-plugin.zip "https://syndu.com/pages/resources/codex-plugin/download/"
unzip -o syndu-v0.1.6-codex-plugin.zip -d ./plugins
json

Repo marketplace entry

{
  "name": "syndu-local",
  "interface": {"displayName": "Syndu Local"},
  "plugins": [
    {
      "name": "syndu",
      "source": {
        "source": "local",
        "path": "./plugins/syndu"
      },
      "policy": {"installation": "AVAILABLE", "authentication": "ON_USE"},
      "category": "Research"
    }
  ]
}
bash

Manual MCP key fallback

export SYNDU_MCP_TOKEN="syndu_mcp_live_..."
echo 'export SYNDU_MCP_TOKEN="syndu_mcp_live_..."' >> ~/.zprofile

Related Resources

Documentation

Syndu Platform Manual

Syndu turns outside-in network behavior into shared cyber-and-fraud context, then preserves decisions in memory for humans, applications, and agents. This manual is the public map of that platform: the evidence graph, the Risk API, the MCP server, and the governance layer that ties them together.

5 briefing points Documentation
Open article
Coverage

What Syndu Reports Cover

Syndu exposes a dimensional risk surface across network entities and geography: ip address, subnet, ISP, ASN, organization, city, region, and country. That same dimensional graph powers the Risk API, MCP tools, and the memory loop that preserves the resulting decisions.

4 briefing points Coverage
Open article
Operations

Using Syndu with SoC and SIEM Workflows

Syndu is an external context layer for monitoring, hygiene review, agent workflows, and decision support. It complements SoC and SIEM processes rather than replacing them, while sharing the same evidence and memory model used elsewhere on the platform.

4 briefing points Operations
Open article
Fraud operations

Using Syndu with Fraud, Payments, and Merchant-Risk Workflows

Syndu is also a decision surface for fraud, payments, merchant-risk, and trust workflows. The same outside-in evidence graph, Risk API, and governed memory loop help teams score, review, and preserve conclusions around risky identifiers.

4 briefing points Fraud operations
Open article
AI and scale

Consuming Syndu at Scale

The platform supports three access surfaces at scale: direct report access for large-scale browser or agent consumption, the Risk API for application-native scoring, and the MCP server for collaborative agent workflows.

4 briefing points AI and scale
Open article
Delivery modes

Direct, API, and MCP Access

Syndu is one platform with three access surfaces: direct access for report-shell consumption, API access for application-side scoring, and MCP access for agent collaboration. They sit under the same workspace, quota, and subscription control plane, but differ in delivery contract.

4 briefing points Delivery modes
Open article
Register

Create a workspace to govern access to Syndu.

Registration unlocks the workspace control plane, plan selection, credential provisioning, and the subscription flow across web, API, and MCP access.

Register Sign in to workspace