# Content Pipeline Agent by Nova (CIVAI) (remote · nova.civai.co)

I run the Content Pipeline for your Nova products, scan trends, expand seeds into opportunities, ge…

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `nova.civai.co`: 73/100 (this document), [markdown](https://verifymcp.io/servers/co-civai-nova-content-pipeline-agent/mcp-agents-content-pipeline-agent.md), [page](https://verifymcp.io/servers/co-civai-nova-content-pipeline-agent/mcp-agents-content-pipeline-agent)

## Channel facts

- Endpoint: `https://nova.civai.co/mcp/agents/content-pipeline-agent`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 597 tokens (~49/item across 12 items; 11 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 37% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_opportunities" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Content Pipeline Agent by Nova (CIVAI) MCP server?

Content Pipeline Agent by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/content-pipeline-agent, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http co-civai-nova-content-pipeline-agent 'https://nova.civai.co/mcp/agents/content-pipeline-agent'
```

### Cursor

```json
{
  "mcpServers": {
    "co-civai-nova-content-pipeline-agent": {
      "url": "https://nova.civai.co/mcp/agents/content-pipeline-agent"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-civai-nova-content-pipeline-agent": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/content-pipeline-agent"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-civai-nova-content-pipeline-agent]
url = "https://nova.civai.co/mcp/agents/content-pipeline-agent"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-civai-nova-content-pipeline-agent": {
      "type": "remote",
      "url": "https://nova.civai.co/mcp/agents/content-pipeline-agent",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-civai-nova-content-pipeline-agent --url 'https://nova.civai.co/mcp/agents/content-pipeline-agent' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-civai-nova-content-pipeline-agent:
    url: "https://nova.civai.co/mcp/agents/content-pipeline-agent"
```

### Netclaw

```json
{
  "McpServers": {
    "co-civai-nova-content-pipeline-agent": {
      "Transport": "http",
      "Url": "https://nova.civai.co/mcp/agents/content-pipeline-agent"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-civai-nova-content-pipeline-agent -t streamable-http -u 'https://nova.civai.co/mcp/agents/content-pipeline-agent'
```

### Other

```json
{
  "mcpServers": {
    "co-civai-nova-content-pipeline-agent": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/content-pipeline-agent"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 71)

First indexed and scored.

## MCP tools (11)

### `trigger_scan` (~68 tokens)

Scan trends for a product and stage candidate seeds (level 1 of the pipeline).

Input parameters:

- `country_code` (string)
- `limit` (integer)
- `lookback_hours` (integer)
- `product_id` (string, required): The content product id (from list_products on Product Admin).

### `list_seeds` (~38 tokens)

List the most recently scanned seeds for a product.

Input parameters:

- `product_id` (string, required): The content product id (from list_products on Product Admin).

### `expand_seeds` (~76 tokens)

Expand selected seeds into content opportunities (level 2 of the pipeline).

Input parameters:

- `country_code` (string)
- `limit_per_seed` (integer)
- `lookback_hours` (integer)
- `product_id` (string, required): The content product id (from list_products on Product Admin).
- `seed_ids` (array)

### `list_opportunities` (~43 tokens)

List staged content opportunities for a product.

Input parameters:

- `product_id` (string, required): The content product id (from list_products on Product Admin).
- `status` (string)

### `delete_opportunities` (~44 tokens)

Delete staged opportunities that shouldn't be generated.

Input parameters:

- `opportunity_ids` (array, required)
- `product_id` (string, required): The content product id (from list_products on Product Admin).

### `generate_content` (~57 tokens)

Generate draft articles for selected opportunities (seo_intent or reward_intent, per the product's pipeline_type).

Input parameters:

- `opportunity_ids` (array, required)
- `product_id` (string, required): The content product id (from list_products on Product Admin).

### `list_drafts` (~48 tokens)

List staged article drafts for a product (unpublished by default).

Input parameters:

- `product_id` (string, required): The content product id (from list_products on Product Admin).
- `published` (boolean)

### `publish_content` (~87 tokens)

Publish drafts to the product's configured publish destination(s) (webhook and/or a connected X account).

Input parameters:

- `article_ids` (array)
- `auto_index` (boolean)
- `product_id` (string, required): The content product id (from list_products on Product Admin).
- `public_urls` (object): Deprecated manual id->url map, only needed if no webhook destination is configured.

### `index_content` (~44 tokens)

Submit published URLs to Google Search Console for indexing.

Input parameters:

- `product_id` (string, required): The content product id (from list_products on Product Admin).
- `urls` (array, required)

### `get_job_status` (~41 tokens)

Check the status/result of a background pipeline job (scan, expand, generate, publish, index all run as jobs).

Input parameters:

- `job_id` (string, required)

### `list_jobs` (~27 tokens)

List recent pipeline jobs.

Input parameters:

- `limit` (integer)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-civai-nova-content-pipeline-agent/mcp-agents-content-pipeline-agent#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71

## Common questions

### What is the Content Pipeline Agent by Nova (CIVAI) MCP server?

Content Pipeline Agent by Nova (CIVAI) is an MCP server listed in the public MCP registry as co.civai.nova/content-pipeline-agent. I run the Content Pipeline for your Nova products, scan trends, expand seeds into opportunities, ge… This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/content-pipeline-agent).

### Is the Content Pipeline Agent by Nova (CIVAI) MCP server safe to use?

Content Pipeline Agent by Nova (CIVAI) scores 73 out of 100 on VerifyMCP. 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 Content Pipeline Agent by Nova (CIVAI) MCP server expose?

Content Pipeline Agent by Nova (CIVAI) exposes 11 tools: trigger_scan, list_seeds, expand_seeds, list_opportunities, delete_opportunities, and 6 more. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.

### Does the Content Pipeline Agent by Nova (CIVAI) MCP server require authentication?

Yes. Content Pipeline Agent by Nova (CIVAI) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Content Pipeline Agent by Nova (CIVAI) MCP server still maintained?

Content Pipeline Agent by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Content Pipeline Agent by Nova (CIVAI) MCP server?

VerifyMCP ran 13 checks on Content Pipeline Agent by Nova (CIVAI), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://nova.civai.co/mcp/agents/content-pipeline-agent
- Website: https://nova.civai.co/agent/content-pipeline-agent
- Changelog RSS feed: https://verifymcp.io/servers/co-civai-nova-content-pipeline-agent/mcp-agents-content-pipeline-agent.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-civai-nova-content-pipeline-agent/mcp-agents-content-pipeline-agent/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/co-civai-nova-content-pipeline-agent/mcp-agents-content-pipeline-agent.json
- HTML version of this page: https://verifymcp.io/servers/co-civai-nova-content-pipeline-agent/mcp-agents-content-pipeline-agent