Support Agent Admin by Nova (CIVAI)
REMOTE · NOVA.CIVAI.CO
I manage your Support Agent CRM, pipeline analytics, follow-ups, Leads Discovery, and workspace out…
Available components
Last scanned (12 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 22 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 9276 tokens (~79/item across 116 items; 115 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 15 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "admin__delete_agent" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 116 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Nov 26 0
- New tool “admin__create_growth_experiment” functional
- New tool “admin__get_growth_experiment” functional
- New tool “admin__get_growth_readout” functional
- New tool “admin__growth_arm_action” functional
- New tool “admin__list_growth_experiments” functional
- New tool “admin__pause_growth_experiment” functional
- New tool “admin__quote_growth_experiment” functional
- New tool “admin__resume_growth_experiment” functional
- New tool “admin__set_growth_auto_tune” functional
- New tool “admin__start_growth_experiment” functional
- “admin__create_agent” added an optional parameter “nudge_on_first_reply” cosmetic
- “admin__update_agent” added an optional parameter “nudge_on_first_reply” cosmetic
- 21 Nov 26 +3
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Tool “admin__create_scan_schedule” rewrote its description, which is the text the model reads security
- Tool “admin__list_leads” rewrote its description, which is the text the model reads security
- Tool “admin__remove_leads” rewrote its description, which is the text the model reads security
- Tool “admin__run_scan” rewrote its description, which is the text the model reads security
- Tool “admin__update_scan_schedule” rewrote its description, which is the text the model reads security
- Tool “admin__upload_attachments” rewrote its description, which is the text the model reads security
- New tool “admin__create_attachment_upload_url” functional
- New tool “admin__list_chats” functional
- New tool “admin__remove_chats” functional
- “admin__remove_leads” reworded the description of “reason” cosmetic
- 20 Nov 26 +1
- New tool “admin__list_leads” functional
- New tool “admin__remove_leads” functional
- “admin__create_agent” added an optional parameter “nudge_handoff_mode” cosmetic
- “admin__update_agent” added an optional parameter “nudge_handoff_mode” cosmetic
- 19 Nov 26 0
- HSTS header: unverified → fail ▼ security
- 18 Nov 26 0
- HSTS header: fail → unverified ▼ security
- Tool “admin__list_channel_accounts” rewrote its description, which is the text the model reads security
- Tool “admin__list_connectors” rewrote its description, which is the text the model reads security
- New tool “admin__connect_channel” functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- Tool “admin__set_pool_mode” rewrote its description, which is the text the model reads security
- New tool “admin__set_whatsapp_account_role” functional
- “admin__create_agent” added an optional parameter “intake_as_lead” cosmetic
- “admin__update_agent” added an optional parameter “intake_as_lead” cosmetic
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- New tool “research__conduct-deep-research” functional
- New tool “research__generate-research-report” functional
- 9 Nov 26 0
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “research__conduct-deep-research” was removed ▼ security
- Tool “research__generate-research-report” was removed ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Probed https://nova.civai.co/mcp/agents/support-agent-admin
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.vearn.co | CN=YR2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 5989a0174450d554cb27dbfdec88b2ff58a |
| SANs: allegedly-api.crypvestai.cloud, allegedly.crypvestai.cloud, api.agi.civai.co, api.browser.civai.co, api.nova.civai.co, api.vearn.co, app.browsergpt.co, app.vearn.co, arcade-assets.civai.co, audience-resolver-api.civai.co, audience-resolver.civai.co, audience.civai.co and 11 more | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nova.civai.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| civai.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/support-agent-admin", scope="mcp:access"
Bearer resource_metadata="https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/support-agent-admin", scope="mcp:access" Protected resource metadata
| Document | https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/support-agent-admin |
|---|---|
| Retrieved | Yes |
| Resource | https://nova.civai.co/mcp/agents/support-agent-admin |
| Authorisation server | https://nova.civai.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nova.civai.co/mcp/agents/support-agent-admin | Verified | 200 | |
| http (plaintext) | http://nova.civai.co/mcp/agents/support-agent-admin | HTTPS enforced | 301 | https://nova.civai.co/mcp/agents/support-agent-admin |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
admin__abort_scans ~46
Stop stuck running scans (marks interrupted, releases schedule lock).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| reason | string | – | – |
| scan_ids | array | yes | – |
No output schema declared.
No examples provided.
admin__assign_instagram_account ~37
Assign or remove Instagram account on agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| instagram_account_id | string | – | – |
No output schema declared.
No examples provided.
admin__assign_jiji_account ~39
Assign or remove Jiji account on agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| jiji_account_id | string | – | – |
No output schema declared.
No examples provided.
admin__assign_smtp_account ~37
Assign or remove SMTP account on agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| smtp_account_id | string | – | – |
No output schema declared.
No examples provided.
admin__assign_telegram_account ~37
Assign or remove Telegram account on agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| telegram_account_id | string | – | – |
No output schema declared.
No examples provided.
admin__assign_whatsapp_account ~39
Assign or remove WhatsApp Web account on agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| whatsapp_account_id | string | – | – |
No output schema declared.
No examples provided.
admin__assign_x_account ~47
Assign main X account on agent (inbound DMs and replies). One agent per handle.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| x_account_id | string | – | – |
No output schema declared.
No examples provided.
admin__assign_x_campaign_account ~86
Assign campaign X account: outbound only, borrows login from another agent's main account.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| move_main_to_agent_id | string | – | When this wave agent is still MAIN for the handle, move MAIN here first (hub/product agent), then set campaign borrow on the wave. |
| x_campaign_account_id | string | – | – |
No output schema declared.
No examples provided.
admin__bulk_delete_sessions ~35
Delete multiple visitor sessions and their files.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| visitor_ids | array | yes | – |
No output schema declared.
No examples provided.
admin__bulk_followup ~49
Bulk follow-up to filtered visitors.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| filter_by | string | – | – |
| message | string | yes | – |
| visitor_ids | array | – | – |
No output schema declared.
No examples provided.
admin__bulk_set_session_labels ~42
Merge labels onto multiple visitor sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| labels | array | – | – |
| visitor_ids | array | yes | – |
No output schema declared.
No examples provided.
admin__clear_discovery_cache ~35
Clear Leads Discovery scan cache for an agent (seen handles / WA progress).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__compose_bulk_draft ~32
AI-compose shared bulk follow-up draft (agent voice only).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__compose_draft ~43
AI-compose a draft reply for one visitor session (Zap; does not send).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| visitor_id | string | yes | – |
No output schema declared.
No examples provided.
admin__connect_channel ~136
Check one outreach channel (whatsapp, instagram, x, telegram, email, jiji, facebook) before messaging on it. Returns status: ready; connected_not_assigned (run next_action to use it on this agent); service_down; or connect_prompted, when the owner's screen now shows Integrations on that channel: put the returned message, with its connect link, in your reply and continue once they say it is connected. Use this whenever the owner wants to reach people on a channel, or a send or follow-up failed for one.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| channel | string | yes | – |
No output schema declared.
No examples provided.
admin__continue_scan ~61
Continue a scan paused for selection (WhatsApp/Telegram groups or IG/X targets).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| max_contacts_per_group | integer | – | – |
| scan_id | string | yes | – |
| selected_resources | array | yes | – |
No output schema declared.
No examples provided.
admin__create_agent ~857
Create a new Support Agent for CRM/outreach.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_list | array | – | Visitor allow list (emails, @handles, Jiji seller ids, X ids). Empty list = allow all visitors. |
| auto_reply_allowed_channels | array | – | Channels where the agent may send AI auto-replies. Empty = all channels (still filtered by allow_list). |
| bulk_followup_enabled | boolean | – | – |
| contact_option | string | yes | – |
| context | string | – | – |
| description | string | – | – |
| disable_ai_reply | boolean | – | – |
| file_support | boolean | – | – |
| followup_email_message | string | – | Email opening template (UI: Outreach opening messages → Email). Used for Leads Discovery Message now, bulk follow-up, and first inbound CRM email auto-reply. |
| followup_email_subject | string | – | Subject line for this agent's outbound follow-up emails (UI: Outreach opening messages → Email). Max 200 characters, no line breaks. Empty = default subject that includes the agent title. Later messa… |
| followup_instagram_message | string | – | Instagram DM opening template for outreach compose. |
| followup_telegram_message | string | – | Telegram opening template for outreach compose. |
| followup_whatsapp_message | string | – | WhatsApp opening template for outreach compose. |
| followup_x_message | string | – | X DM opening template for outreach compose. |
| inapp | boolean | – | – |
| instructions | string | – | – |
| intake_as_lead | boolean | – | When true, an intake form submission is imported as a lead (saved as Leads Discovery-style context) and the agent sends its own first outreach, instead of the form being treated as the contact's firs… |
| intake_enabled | boolean | – | Whether POST /api/public-agents/{agent_id}/intake accepts website form submissions for this agent. No API key is needed to call it, so it is off by default and the endpoint answers 404 while off. |
| intake_origins | array | – | Origins allowed to post to the intake endpoint, e.g. https://civai.co. Empty list = any origin. Up to 10. |
| is_public | boolean | – | – |
| nudge_handoff_mode | boolean | – | For agents whose nudge is the hand-off itself (an order desk reporting each decision in one long-lived chat): only an exact repeat of a nudge reason is skipped, and there is no per-session nudge cap.… |
| nudge_on_first_reply | boolean | – | Offer nudge_operator from the agent's very first reply, instead of only after a few exchanges. For agents whose first reply can already be the event the team needs (an order desk whose vendor answers… |
| nudge_operator_enabled | boolean | – | Whether the nudge_operator tool (email the owner/collaborators when the agent needs human follow-up) is available to this agent. Defaults to false. |
| public_category_id | integer | – | – |
| public_description | string | – | – |
| public_slug | string | – | – |
| theme | string | – | – |
| title | string | yes | – |
| x_followup_max_per_thread | integer | – | Max automated reply rounds in one public thread (main-account thread replies, or a pool peer answering its own quote) before going quiet. Not account-only — layered agent/account/workspace/env like t… |
| x_ld_attention_use_custom | boolean | – | When true, use agent-specific X Leads Discovery public attention (Lane A/B). |
| x_ld_like_before_dm | boolean | – | – |
| x_ld_pool_public_quote_after_dm_fail | boolean | – | – |
| x_ld_public_after_dm | boolean | – | – |
| x_ld_public_only | boolean | – | Cold LD import: public quote/reply only, no DMs. |
| x_ld_public_per_run_limit | integer | – | – |
| x_ld_public_post_goal | string | – | – |
| x_ld_public_poster | string | – | – |
| x_ld_public_surface | string | – | – |
| x_ld_quote_target | string | – | – |
No output schema declared.
No examples provided.
admin__create_attachment_upload_url ~151
Get a one-time HTTPS upload link for ONE large KB file (SQLite/DB/CSV up to 50MB, XLSX 20MB, PDF/DOCX/DOC/TXT 10MB) so the bytes never pass through tool arguments. Returns upload_url and a ready curl command: PUT the raw file there (curl -T file URL) within 15 minutes, no API key needed. The upload response carries attachment_id; then poll list_attachments until status is ready.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| filename | string | yes | Name the attachment will have, with extension (e.g. chatprep-questions.sqlite). The link only accepts this file type. |
No output schema declared.
No examples provided.
admin__create_growth_experiment ~116
Create a draft growth experiment on one agent. Nothing runs and no credits are spent until start_growth_experiment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| custom | object | – | Custom package: days 1-30, reach_per_day (people a day) 10-500, channels (keyword channels: x, instagram, tiktok, facebook). |
| hypothesis | string | – | – |
| name | string | yes | – |
| package_id | string | – | Preset package, or custom with the custom object. |
No output schema declared.
No examples provided.
admin__create_scan_schedule ~208
Create an auto-scan schedule (Import Only or Message now outreach). Discovery params for x/instagram/facebook/tiktok accept max_post_age_days (1-365; omit = no age limit) and post_age_relax_steps (0-4, default 3) to cap how old a source post may be before its engagers are collected; the window widens within a run only.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| auto_import | boolean | – | – |
| auto_outreach | string | – | – |
| channel | string | yes | – |
| enabled | boolean | – | – |
| frequency | string | – | – |
| label | string | – | – |
| max_leads_per_run | integer | – | – |
| max_runs | integer | – | – |
| params | object | – | – |
| relax_target_filter_after_runs | integer | – | – |
| run_hour_utc | integer | – | – |
| source_scan_at | string | – | – |
| source_scan_id | string | – | – |
No output schema declared.
No examples provided.
admin__delete_agent ~25
Permanently delete a Support Agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__delete_attachment ~32
Delete one agent KB attachment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| attachment_id | string | yes | – |
No output schema declared.
No examples provided.
admin__delete_scan_schedule ~34
Delete an auto-scan schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| schedule_id | string | yes | – |
No output schema declared.
No examples provided.
admin__delete_scans ~40
Delete one or more completed scan runs (does not delete schedules).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| scan_ids | array | yes | – |
No output schema declared.
No examples provided.
admin__end_conversation ~40
Mark visitor conversation ended (stops IG/WA follow-ups).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| visitor_id | string | yes | – |
No output schema declared.
No examples provided.
admin__export_contacts ~62
Export filtered contacts as CSV (returns csv_content in result).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| contact_type | string | yes | – |
| created_from | string | – | – |
| created_to | string | – | – |
| filter_by | string | – | – |
No output schema declared.
No examples provided.
admin__generate_agent_preview ~39
AI-generate agent title/instructions/context from business description.
| Name | Type | Req | Description |
|---|---|---|---|
| business_description | string | yes | – |
| business_name | string | yes | – |
No output schema declared.
No examples provided.
admin__get_ad_guide ~90
The ad plan rendered as steps to tap, per channel, in the owner's own words with the daily budget already divided. Use this when the owner wants to run the ads themselves. Nova never touches their ad account.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| channel | string | – | instagram, tiktok or whatsapp. Omit for every channel. |
| leads_target | integer | – | – |
No output schema declared.
No examples provided.
admin__get_ad_plan ~175
The ads this business should run, built from its own scans: three things to film, each citing a count from this agent's own leads, plus the spend and reach for a lead target. Reads only; nothing is launched and no money moves. Returns status=no_evidence when the scans have not found enough to say anything specific.
| Name | Type | Req | Description |
|---|---|---|---|
| account_mode | string | – | Whose ad account. 'nova' needs nothing from the owner and Nova is the advertiser; 'owner' runs on their own connected account. Omit and the plan preselects by what they already have, returning both o… |
| agent_id | string | yes | – |
| country | string | – | Two-letter code, default NG. |
| leads_target | integer | – | Leads a month the owner wants. Spend is derived from it. |
No output schema declared.
No examples provided.
admin__get_agent ~29
Return full agent metadata including chat/public/iframe links.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__get_agent_analytics ~43
Pipeline overview on one agent_id (totals + top visitors).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| top_visitors_limit | integer | – | – |
No output schema declared.
No examples provided.
admin__get_attachment_content ~38
Read converted markdown or database schema summary for one attachment.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| attachment_id | string | yes | – |
No output schema declared.
No examples provided.
admin__get_chat ~87
Open a lead chat by visitor_id, email, phone, or contact handle.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| contact | string | – | Generic contact from analytics/list_sessions (email, phone, or @instagram). |
| instagram_username | string | – | – |
| visitor_email | string | – | – |
| visitor_id | string | – | – |
| whatsapp_no | string | – | – |
No output schema declared.
No examples provided.
admin__get_crm_unreplied_alert_config ~32
Read CRM unreplied digest email settings.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__get_discovery_analytics ~49
Get sourced-leads analytics for an agent (window e.g. 7d, 30d).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| window | string | – | – |
No output schema declared.
No examples provided.
admin__get_followup_run ~37
Get one follow-up run with progress log.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
admin__get_growth_experiment ~47
One growth experiment: status, package, run plan schedules, arms, progress, credits left.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| experiment_id | string | yes | – |
No output schema declared.
No examples provided.
admin__get_growth_readout ~49
Growth experiment readout: arms, keyword leaderboard, lead quality, decision log, recommendation and ad brief.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| experiment_id | string | yes | – |
No output schema declared.
No examples provided.
admin__get_scan ~54
Get one scan with paginated leads (status, progress, leads).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| limit | integer | – | – |
| offset | integer | – | – |
| scan_id | string | yes | – |
No output schema declared.
No examples provided.
admin__growth_arm_action ~61
Owner control on one keyword arm: keep (never retire), unkeep, pause, resume.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| agent_id | string | yes | – |
| arm_id | string | yes | – |
| experiment_id | string | yes | – |
No output schema declared.
No examples provided.
admin__import_contacts ~71
Import contacts onto an agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| channel | string | yes | – |
| contacts | string | – | – |
| emails | string | – | – |
| instagram_usernames | array | – | – |
| telegram_usernames | array | – | – |
| whatsapp_numbers | string | – | – |
No output schema declared.
No examples provided.
admin__import_leads ~69
Import discovered leads into the agent CRM (outreach: none|immediate|bulk_followup).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| label | string | – | – |
| lead_ids | array | yes | – |
| outreach | string | – | – |
| scan_id | string | yes | – |
No output schema declared.
No examples provided.
admin__invite_agent_collaborator ~50
Invite a Nova user by email to collaborate on an agent (owner only).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| string | yes | – | |
| role | string | – | – |
No output schema declared.
No examples provided.
admin__launch_ad_plan ~220
Run one ad on one channel, under a spend cap the owner has named out loud. The cap is debited before anything is created and nothing is ever created above it. Creative is the owner's: this never writes an ad. Needs a connected ad account.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| body | string | yes | Up to 125 characters. |
| call_to_action | string | – | Default LEARN_MORE. |
| cap_minor | integer | yes | The total spend cap in MINOR units (kobo, cents). Required, never inferred: this is the number the owner approved. |
| channel | string | yes | – |
| country | string | – | Two-letter code. |
| currency | string | – | Three letters, default NGN. |
| daily_budget_minor | integer | – | Daily budget in minor units. Defaults to the cap. |
| headline | string | yes | Up to 40 characters. |
| image_url | string | yes | A public image the ad platform can fetch. |
| link_url | string | yes | Where the ad sends people. |
No output schema declared.
No examples provided.
admin__list_ad_plans ~48
Every ad this agent has already launched, newest first, with its cap, its channel and whether it is running or stopped. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__list_agent_collaborators ~34
List team members with access to a support agent (owner only).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__list_agents ~28
List all Support Agents for the signed-in owner.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | – |
No output schema declared.
No examples provided.
admin__list_attachments ~28
List knowledge-base attachments on a Support Agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__list_channel_accounts ~40
List available channel accounts for assignment (WhatsApp, IG, X, Telegram, SMTP, Jiji).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
admin__list_chats ~291
This agent's CRM chats (conversations) as a compact table, 20 per page, most recent activity first. The chat counterpart of list_leads: list_leads reads Leads Discovery scan results, list_chats reads the conversations in the CRM. Each row: visitor_id, name/handle, channel, source (leads_discovery or inbound), labels, outreach_sent and replies counts, last message, created and last activity. 'counts' totals the whole filtered set (with/without outreach, replied). Filter by channel, source, outreach (yes/no/any: any message sent to them), replied (yes/no/any), label (label text or id), since (YYYY-MM-DD, created on or after), query (words in the name, labels or messages). Fetch the next page with page=next_page while has_more is true.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| channel | string | – | x, instagram, tiktok, facebook, whatsapp, email, telegram, jiji, web, ... |
| label | string | – | – |
| outreach | string | – | – |
| page | integer | – | 1-based |
| per_page | integer | – | Default 20, at most 50 |
| query | string | – | – |
| replied | string | – | – |
| since | string | – | YYYY-MM-DD |
| source | string | – | – |
No output schema declared.
No examples provided.
How do I install the Support Agent Admin by Nova (CIVAI) MCP server?
Support Agent Admin by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/support-agent-admin, 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.
remote · nova.civai.co
claude mcp add --transport http co-civai-nova-support-agent-admin 'https://nova.civai.co/mcp/agents/support-agent-admin'
What is the Support Agent Admin by Nova (CIVAI) MCP server?
Support Agent Admin by Nova (CIVAI) is an MCP server listed in the public MCP registry as co.civai.nova/support-agent-admin. I manage your Support Agent CRM, pipeline analytics, follow-ups, Leads Discovery, and workspace out… This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/support-agent-admin).
Is the Support Agent Admin by Nova (CIVAI) MCP server safe to use?
Support Agent Admin by Nova (CIVAI) scores 88 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 Support Agent Admin by Nova (CIVAI) MCP server expose?
Support Agent Admin by Nova (CIVAI) exposes 115 tools: admin__list_agents, admin__list_top_agents, admin__get_agent, admin__get_agent_analytics, admin__list_sessions, and 110 more. Their descriptions and schemas cost roughly 9,245 tokens of context every time the server is loaded.
Does the Support Agent Admin by Nova (CIVAI) MCP server require authentication?
Yes. Support Agent Admin 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 Support Agent Admin by Nova (CIVAI) MCP server still maintained?
Support Agent Admin by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 22 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 Support Agent Admin by Nova (CIVAI) MCP server?
VerifyMCP ran 13 checks on Support Agent Admin 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.