cloud1
cloud2
cloud3
cloud4
cloud5
cloud6
Manus
Syndu For Manus
← Back to platform brief
Manus

Syndu For Manus

Set up Syndu in Manus with a package-led install flow: download the integration bundle, create the workspace MCP key in Access, connect Manus to Syndu's hosted MCP surface, then import the investigation skill so future Manus tasks inherit shared risk memory.

Download Manus package Open Access Open MCP page
Package-first install

Download the Manus package, then import the MCP configuration with your Access-created key

The Manus flow is package-based, not prompt-installed. Start by creating the workspace MCP credential in Access, then download the package from this page and import the configuration or enter the same values manually in Manus.

{
  "mcpServers": {
    "syndu-mcp": {
      "url": "https://syndu.com/mcp/",
      "auth": {
        "type": "bearer",
        "token": "<create this in Access>"
      }
    }
  }
}
Create the key in Access first Download the integration package Import JSON or configure Manus manually Install the `syndu-investigation` skill from the package
Documentation index Platform brief Quota rules Privacy FAQ
Current package
syndu_manus_integration_package.zip

The downloadable package from Syndu Web LTD includes the Manus skill, the MCP configuration JSON, and a package README in one 7 KB archive.

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

Manus connects to the same hosted Syndu MCP surface used by the rest of the product, so the backend stays unified.

Auth model
Create the bearer key in Access

The package is intentionally token-free. Create the workspace MCP credential in Access, then paste it into the Manus import JSON or the manual header field.

Skill layer
Import `syndu-investigation/SKILL.md`

The Manus skill gives the agent the right investigation workflow on top of the hosted connection, including memory lookup and writeback guidance.

Quota handoff
Return to Access Plans if the daily budget runs out

Metered investigation calls stay bound to the same workspace. When the budget is exhausted, expand the entitlement in Access and keep using the same Manus connection.

Open Access Plans

What The Manus Package Includes

The Manus install should feel structured and operator-safe. The package gives the buyer everything needed to connect Manus cleanly without inventing the flow by hand.

Skill package

A Manus skill for Syndu investigations

The `syndu-investigation` skill tells Manus how to resolve risky identifiers, expand related context, inspect prior memory, and preserve the approved outcome.

Risk investigation workflow Memory lookup before rework Quota-aware handoff back to Access
Connection file

A ready-to-import MCP configuration

The package includes `mcp_configuration.json` so buyers who have Manus JSON import support can paste in one configuration block instead of reconstructing the server by hand.

Hosted MCP endpoint Bearer auth placeholder Matches the live Syndu surface
Operator guide

A README that mirrors the setup path

The package README keeps the install sequence close to the archive: create the key in Access, connect the MCP server, import the skill, then use Manus with live examples.

One package, one workflow No hidden install dependency Aligned to the Access control plane

Why The Manus Setup Is Package-Led

Manus does not follow the same install motion as Codex. The right setup is a bundle plus a hosted MCP connection, with Access remaining the control plane for credentials, quota, and workspace ownership.

Manus

Create the workspace key in Access, not in the package

The downloadable archive should never carry a live secret. Operators create the MCP credential in Access, then place that workspace key into the import JSON or the manual Manus header field.

Manus

Import when you can, configure manually when you must

The package includes a JSON configuration because that is the cleanest Manus path when import is available, but the same settings are documented for manual entry so the install does not depend on one UI affordance.

Manus

The skill is what makes the connection useful

A raw MCP server entry is only transport. The `syndu-investigation` skill is what teaches Manus to resolve subjects, look up prior memory, preserve outcomes, and stop cleanly when quota needs to be expanded.

Manus

Workspace quota and memory stay unified

Manus does not create a second commercial boundary. Metered investigation calls, governed workspace memory, and share-safe hive contribution stay attached to the same Syndu workspace that created the key.

Download And Open The Right Surface

The package should not strand the operator. Download the archive here, create the key in Access, and keep the MCP page nearby for the hosted contract and pricing model.

Current zip

Download Manus package

syndu_manus_integration_package.zip

Download the current Manus integration package directly from Syndu Web LTD.

Skill included MCP JSON included README included
Download package
Access dashboard

Open Access MCP controls

/access/?mode=mcp#mcp-credentials

Create the workspace MCP key, manage memory policy, and return here with the right bearer token for Manus.

Create the key Control quota Keep the same workspace
Open Access
Quota handoff

Open Access Plans

/access/?mode=mcp&reason=quota#plans

When the daily metered investigation budget runs out, provision more quota in the same workspace and keep the same Manus-side connection.

Same workspace Same credential model Memory stays available
Open Plans
Hosted contract

Read the MCP product page

/pages/resources/mcp-server/

See the hosted MCP endpoint, pricing ladder, and governed memory model that sit behind the Manus package.

Hosted endpoint Shared memory model Pricing context
Open MCP page

Two Ways To Configure Manus

The recommended path is JSON import when Manus supports it. Manual entry is the fallback when the operator needs to add the hosted server and the authorization header step by step.

Recommended

Import the MCP JSON from the package

Best when Manus supports MCP config import, because the operator can paste one block, replace the token with the Access-created key, and move on to the skill import.

One config object Fastest clean setup Easy to re-check later
Fallback

Add the Custom MCP Server manually

Best when Manus only exposes a manual UI. Use `syndu-mcp`, the hosted `https://syndu.com/mcp/` endpoint, and the `Authorization: Bearer <key>` header from Access.

Server name: syndu-mcp Transport: HTTP Custom Authorization header
Workflow layer

Import the skill after the connection works

The Manus-side connection should be proven first. Then install the skill from the package so the agent has the right investigation loop and output expectations on top of the live server.

Hosted server first Skill second Live investigation third

Download, Connect, Install

This is the package-led Manus path: create the key in Access, download the archive, connect the hosted MCP server, then import the skill and begin working.

01

Open Access MCP controls

Sign into Syndu and open the Access MCP panel for the workspace you want Manus to use.

02

Create one workspace MCP credential

Generate the workspace credential in Access and copy it once while the full secret is visible. This is the key Manus will send as the bearer token.

03

Download the Manus integration package

Use the package from this page so the operator starts with the README, the MCP configuration JSON, and the Manus skill in one archive.

04

Import the MCP configuration or enter the same values manually

If Manus supports JSON import, use `mcp_configuration.json` and replace the token placeholder with the Access-created key. Otherwise add `syndu-mcp` manually with the hosted endpoint and `Authorization: Bearer <key>`.

05

Install the `syndu-investigation` skill

Locate `syndu-investigation/SKILL.md` inside the package and import it into Manus so the agent gets the right investigation workflow on top of the live connection.

06

Use Manus with live Syndu prompts

Start with one suspicious identifier, let Manus investigate through Syndu, and preserve the approved outcome so future Manus work inherits the same conclusion.

Copy-Ready Manus Materials

The package and the page should say the same thing. Use these blocks when the operator wants to inspect the MCP JSON, the manual config, or the starter prompts before importing the archive.

json

mcp_configuration.json

{
  "mcpServers": {
    "syndu-mcp": {
      "url": "https://syndu.com/mcp/",
      "auth": {
        "type": "bearer",
        "token": "<create this in Access>"
      }
    }
  }
}
text

Manual Manus server entry

Server name: syndu-mcp
Transport type: HTTP
Server URL: https://syndu.com/mcp/
Header name: Authorization
Header value: Bearer <create this in Access>
text

Starter Manus prompts

Investigate the risk posture of IP address 78.153.140.250 using Syndu.
Check Syndu memory for prior investigations on domain example.com.
Explain the entity risk for organization Cloudie Limited with Syndu.
Preserve the outcome of my investigation into 192.168.1.1 as blocked in Syndu memory.

Related Resources

Documentation

Syndu Documentation Index

Syndu gives computer-using agents outside-in risk context and a governed memory loop. This index maps the supporting docs: plugin install, MCP workflows, the Risk API, pricing, privacy, and the evidence depth behind the system.

4 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