Home / MCP registry index / co.civai.nova/mcp-audience-resolver

Audience Resolver MCP by Nova (CIVAI)

co.civai.nova/mcp-audience-resolver in the official MCP registry. Endpoint https://nova.civai.co/mcp/agents/mcp-audience-resolver.

The registry describes it as: Manage Audience Resolver content calendars, rows, and social scheduling on your AR project.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http mcp-audience-resolver https://nova.civai.co/mcp/agents/mcp-audience-resolver

{
  "mcpServers": {
    "mcp-audience-resolver": {
      "url": "https://nova.civai.co/mcp/agents/mcp-audience-resolver"
    }
  }
}

code --add-mcp '{"name":"mcp-audience-resolver","type":"http","url":"https://nova.civai.co/mcp/agents/mcp-audience-resolver"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_content_calendars create_content_calendar get_content_calendar update_content_calendar delete_content_calendar create_calendar_row update_calendar_row delete_calendar_row delete_calendar_rows schedule_calendar_row schedule_all_calendar_rows upload_publisher_image upload_publisher_video export_content_calendar_json import_content_calendar_json list_twitter_accounts list_social_accounts nova_generate_calendar import_webpage_calendar get_row_generate_asset_context generate_calendar_row_asset regenerate_calendar_row_asset list_publishing_history get_publishing_history_item cancel_publishing_history unschedule_calendar_row list_project_assets asset_from_drive get_project_asset update_project_asset delete_project_asset cancel_project_asset list_projects create_project get_project_initialization_status generate_research get_research_status list_research_reports list_project_drive upload_project_drive_file publish_asset

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-02): 3318a4bd3b6c6418. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/co-civai-nova-mcp-audience-resolver/badge.svg)](https://lazaretto.dev/mcp-registry/co-civai-nova-mcp-audience-resolver)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Calendar MCP servers