Nova Inbox Agent by Nova (CIVAI)
REMOTE · NOVA.CIVAI.CO · SCANNED SEP 25
Read and send mail from your Nova Inbox (@nova.civai.co) for OTPs, directory signups, and inbound m…
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 526 tokens (~75/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "nova_inbox__compose_message" implies "send" 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 7 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
How do I install the Nova Inbox Agent by Nova (CIVAI) MCP server?
Nova Inbox Agent by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/nova-inbox-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.
remote · nova.civai.co
claude mcp add --transport http co-civai-nova-nova-inbox-agent 'https://nova.civai.co/mcp/agents/nova-inbox-agent'
{
"mcpServers": {
"co-civai-nova-nova-inbox-agent": {
"url": "https://nova.civai.co/mcp/agents/nova-inbox-agent"
}
}
} {
"servers": {
"co-civai-nova-nova-inbox-agent": {
"type": "http",
"url": "https://nova.civai.co/mcp/agents/nova-inbox-agent"
}
}
} [mcp_servers.co-civai-nova-nova-inbox-agent] url = "https://nova.civai.co/mcp/agents/nova-inbox-agent"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-civai-nova-nova-inbox-agent": {
"type": "remote",
"url": "https://nova.civai.co/mcp/agents/nova-inbox-agent",
"enabled": true
}
}
} openclaw mcp add co-civai-nova-nova-inbox-agent --url 'https://nova.civai.co/mcp/agents/nova-inbox-agent' --transport streamable-http
mcp_servers:
co-civai-nova-nova-inbox-agent:
url: "https://nova.civai.co/mcp/agents/nova-inbox-agent" {
"McpServers": {
"co-civai-nova-nova-inbox-agent": {
"Transport": "http",
"Url": "https://nova.civai.co/mcp/agents/nova-inbox-agent"
}
}
} assistant mcp add co-civai-nova-nova-inbox-agent -t streamable-http -u 'https://nova.civai.co/mcp/agents/nova-inbox-agent'
{
"mcpServers": {
"co-civai-nova-nova-inbox-agent": {
"type": "http",
"url": "https://nova.civai.co/mcp/agents/nova-inbox-agent"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 74
First indexed and scored.
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 25 Sept 2026 · Probed https://nova.civai.co/mcp/agents/nova-inbox-agent
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=YR1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | RSA 2048 | SHA256-RSA | 69ba14a46afe8487a6de1ca14b4952874a3 |
| 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, audience-resolver-api.civai.co, audience-resolver.civai.co, audience.civai.co, floodmap-api.civai.co and 6 more | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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. | present | 7786 | 8 | Verified |
| civai.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
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/nova-inbox-agent | Verified | 200 | |
| http (plaintext) | http://nova.civai.co/mcp/agents/nova-inbox-agent | HTTPS enforced | 301 | https://nova.civai.co/mcp/agents/nova-inbox-agent |
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 →
nova_inbox__compose_message ~171
Send outbound email from the user's @nova.civai.co address (deterministic; no LLM draft).
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_drive_ids | array | – | Workspace Drive file ids to attach (max 5, 2 MB each). |
| attachments | array | – | Inline attachments for MCP hosts without Drive (max 5, 2 MB each). |
| html | string | – | Optional HTML body (sanitized subset). Used when present. |
| reply_to_id | string | – | Nova Inbox storage id of the message being replied to (threads the send). |
| subject | string | – | Email subject. Required for new mail; optional when reply_to_id is set. |
| text | string | – | Plain-text body. Required if html is omitted. |
| to | string | yes | Recipient email address. |
No output schema declared.
No examples provided.
nova_inbox__converse ~38
Reply conversationally when the request is ambiguous or needs clarification.
| Name | Type | Req | Description |
|---|---|---|---|
| reply_hint | string | – | Optional hint for the conversational reply. |
No output schema declared.
No examples provided.
nova_inbox__get_attachment ~72
Download one email attachment as base64 (by drive_id or index on the message).
| Name | Type | Req | Description |
|---|---|---|---|
| drive_id | string | – | Drive id from message attachments metadata. |
| index | integer | – | 0-based attachment index on the message. |
| message_id | string | yes | Message id that owns the attachment. |
No output schema declared.
No examples provided.
nova_inbox__get_inbox_address ~33
Return the user's Nova Inbox email address (e.g. user@nova.civai.co).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nova_inbox__list_messages ~81
List messages in the signed-in user's Nova Inbox (@nova.civai.co).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max messages to return (1–50). Default 10. |
| query | string | – | Optional filter on subject or from address (case-insensitive substring). |
| unread_only | boolean | – | If true, only unread inbound messages. |
No output schema declared.
No examples provided.
nova_inbox__list_thread ~69
List all messages in an email thread (inbound + outbound), oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | – | Any message id in the thread (from list_messages or read_message). |
| thread_key | string | – | Thread key from list_messages/read_message (alternative to message_id). |
No output schema declared.
No examples provided.
nova_inbox__read_message ~62
Read full body of one Nova Inbox message by id or list index (includes attachment metadata).
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | – | 0-based index from the latest list_messages result. |
| message_id | string | – | Nova Inbox message id from list_messages. |
No output schema declared.
No examples provided.
What is the Nova Inbox Agent by Nova (CIVAI) MCP server?
Nova Inbox Agent by Nova (CIVAI) is an MCP server listed in the public MCP registry as co.civai.nova/nova-inbox-agent. Read and send mail from your Nova Inbox (@nova.civai.co) for OTPs, directory signups, and inbound m… This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/nova-inbox-agent).
Is the Nova Inbox Agent by Nova (CIVAI) MCP server safe to use?
Nova Inbox Agent by Nova (CIVAI) scores 76 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 Nova Inbox Agent by Nova (CIVAI) MCP server expose?
Nova Inbox Agent by Nova (CIVAI) exposes 7 tools: nova_inbox__list_messages, nova_inbox__read_message, nova_inbox__list_thread, nova_inbox__get_attachment, nova_inbox__get_inbox_address, and 2 more. Their descriptions and schemas cost roughly 526 tokens of context every time the server is loaded.
Does the Nova Inbox Agent by Nova (CIVAI) MCP server require authentication?
Yes. Nova Inbox 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 Nova Inbox Agent by Nova (CIVAI) MCP server still maintained?
Nova Inbox Agent by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.