Content Pipeline Agent by Nova (CIVAI) MCP server
co.civai.nova/content-pipeline-agentnova.civai.costreamable-httpv1.0.0Scanned
I run the Content Pipeline for your Nova products, scan trends, expand seeds into opportunities, ge…
11 tools: 1 can delete or cancel things, 1 do something that can't be undone, 4 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Content Pipeline Agent by Nova (CIVAI) MCP server can do
The Content Pipeline Agent by Nova (CIVAI) MCP server is published by nova.civai.co, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (1 tool: delete_opportunities), do things that cannot be undone, such as sending, paying or publishing (publish_content) and create or change data (4 tools: trigger_scan, expand_seeds, generate_content and index_content). 5 tools only read.
2 tools can send data out of your system (publish_content and index_content).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Deletes or cancels 1Claude Code: deny
delete_opportunitiesDelete staged opportunities that shouldn't be generated.No findings
Why it is in this group
- The name "delete_opportunities" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete staged opportunities that shouldn't be generated.
Can't be undone 1Claude Code: ask
publish_contentPublish drafts to the product's configured publish destination(s) (webhook and/or a connected X account).Can send data outNo findings
Why it is in this group
- The name "publish_content" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "publish_content" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Publish drafts to the product's configured publish destination(s) (webhook and/or a connected X account).
Changes things 4Claude Code: ask
expand_seedsExpand selected seeds into content opportunities (level 2 of the pipeline).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Expand selected seeds into content opportunities (level 2 of the pipeline).
generate_contentGenerate draft articles for selected opportunities (seo_intent or reward_intent, per the product's pipeline_type).No findings
Why it is in this group
- The name "generate_content" says "generate": a word for a change.
Description, as the server wrote it Generate draft articles for selected opportunities (seo_intent or reward_intent, per the product's pipeline_type).
index_contentSubmit published URLs to Google Search Console for indexing.Can send data outNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Submit published URLs to Google Search Console for indexing.
trigger_scanScan trends for a product and stage candidate seeds (level 1 of the pipeline).No findings
Why it is in this group
- The name "trigger_scan" says "trigger": a word for a change.
Description, as the server wrote it Scan trends for a product and stage candidate seeds (level 1 of the pipeline).
Only reads 5Show 5 read-only tools
get_job_statusCheck the status/result of a background pipeline job (scan, expand, generate, publish, index all run as jobs).No findings
Why it is in this group
- The name "get_job_status" says "get": a word for reading.
Description, as the server wrote it Check the status/result of a background pipeline job (scan, expand, generate, publish, index all run as jobs).
list_draftsList staged article drafts for a product (unpublished by default).No findings
Why it is in this group
- The name "list_drafts" says "list": a word for reading.
Description, as the server wrote it List staged article drafts for a product (unpublished by default).
list_jobsList recent pipeline jobs.No findings
Why it is in this group
- The name "list_jobs" says "list": a word for reading.
Description, as the server wrote it List recent pipeline jobs.
list_opportunitiesList staged content opportunities for a product.No findings
Why it is in this group
- The name "list_opportunities" says "list": a word for reading.
Description, as the server wrote it List staged content opportunities for a product.
list_seedsList the most recently scanned seeds for a product.No findings
Why it is in this group
- The name "list_seeds" says "list": a word for reading.
Description, as the server wrote it List the most recently scanned seeds for a product.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/content-pipeline-agent
- Authorization servers
- https://nova.civai.co
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nova.civai.co/mcp/agents/content-pipeline-agent: tools/list returned 11 tools to an anonymous client, including delete_opportunities (destructive), publish_content (irreversible), trigger_scan (write), expand_seeds (write), generate_content (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http content-pipeline-agent https://nova.civai.co/mcp/agents/content-pipeline-agentclaude mcp add --transport http content-pipeline-agent https://nova.civai.co/mcp/agents/content-pipeline-agentRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__content-pipeline-agent__list_seeds",
"mcp__content-pipeline-agent__list_opportunities",
"mcp__content-pipeline-agent__list_drafts",
"mcp__content-pipeline-agent__get_job_status",
"mcp__content-pipeline-agent__list_jobs"
],
"ask": [
"mcp__content-pipeline-agent__trigger_scan",
"mcp__content-pipeline-agent__expand_seeds",
"mcp__content-pipeline-agent__generate_content",
"mcp__content-pipeline-agent__publish_content",
"mcp__content-pipeline-agent__index_content"
],
"deny": [
"mcp__content-pipeline-agent__delete_opportunities"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as content-pipeline-agent. Review it before you use it.
Capability tags behind 2 rules
- mcp__content-pipeline-agent__publish_content outbound
- mcp__content-pipeline-agent__index_content outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/co.civai.nova/content-pipeline-agent/verify?hash=7454c551436d645f8497aa09f63193981c19c44f975d2ab5033f1a3dc97b7ad3" | jq -e '.changed == false'Pinned hash 7454c551436d, from Nov 15, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/co.civai.nova/content-pipeline-agent/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/co.civai.nova/content-pipeline-agent)Source: MCP Registry. Synced Nov 2, 2026, 10:17 UTC.
Content Pipeline Agent by Nova (CIVAI) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Content Pipeline Agent by Nova (CIVAI) MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Content Pipeline Agent by Nova (CIVAI) MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_opportunities.
Can the Content Pipeline Agent by Nova (CIVAI) MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: publish_content.
What tools does the Content Pipeline Agent by Nova (CIVAI) MCP server have?
- 11 tools: 1 destructive, 1 irreversible, 4 write, 5 read. delete_opportunities, publish_content, trigger_scan, expand_seeds, generate_content, index_content, list_seeds, list_opportunities and 3 more.
Does the Content Pipeline Agent by Nova (CIVAI) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Content Pipeline Agent by Nova (CIVAI) MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_content and index_content.
Has the Content Pipeline Agent by Nova (CIVAI) MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.