Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Gmail Agent by Nova (CIVAI)

REMOTE · NOVA.CIVAI.CO

I do everything related to Gmail and productivity

Available components

−23 this week 62 Trust /100

Last scanned (15 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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 Security49
Transport & Reachability0
Schema Quality & AI Usability56
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 123 tokens (~30/item across 4 items; 4 tools + 0 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 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (12)

  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.

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 →

Changelog

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.

  • 21 Nov 26 −23
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: fail → pass ▲ security
    • First check of Authorization: pass security
  • 20 Nov 26 +62
    • Authorization: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 19 Nov 26 −62
    • Endpoint reachability: unreachable → not serving MCP ▼ security
    • HSTS header: unverified → fail ▼ security
    • TLS certificate: unverified → pass ▲ security
    • Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 502. security
  • 18 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Probed https://nova.civai.co/mcp/agents/gmail-agent

TLS unreached
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/gmail-agent", scope="mcp:access"

Bearer resource_metadata="https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/gmail-agent", scope="mcp:access"

Protected resource metadata

Document https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/gmail-agent
Retrieved Yes
Resource https://nova.civai.co/mcp/agents/gmail-agent
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/gmail-agent Unreachable
http (plaintext) http://nova.civai.co/mcp/agents/gmail-agent HTTPS enforced 301 https://nova.civai.co/mcp/agents/gmail-agent
MCP tools · 4 exposed · ~123 tokens

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 →

Tool Tokens
compose_email ~29

Run Google mail action: compose email

NameTypeReqDescription
detailstring–Task-specific details from the objective.

No output schema declared.

No examples provided.

converse ~33

Reply conversationally when the request is ambiguous or needs clarification.

NameTypeReqDescription
reply_hintstring–Optional hint for the conversational reply.

No output schema declared.

No examples provided.

latest_emails ~30

Run Google mail action: latest emails

NameTypeReqDescription
detailstring–Task-specific details from the objective.

No output schema declared.

No examples provided.

read_single_email ~31

Run Google mail action: read single email

NameTypeReqDescription
detailstring–Task-specific details from the objective.

No output schema declared.

No examples provided.

Install

How do I install the Gmail Agent by Nova (CIVAI) MCP server?

Gmail Agent by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/gmail-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

# add to Claude Code
claude mcp add --transport http co-civai-nova-gmail-agent 'https://nova.civai.co/mcp/agents/gmail-agent'
Common questions

What is the Gmail Agent by Nova (CIVAI) MCP server?

Gmail Agent by Nova (CIVAI) is an MCP server listed in the public MCP registry as co.civai.nova/gmail-agent. I do everything related to Gmail and productivity. This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/gmail-agent).

Is the Gmail Agent by Nova (CIVAI) MCP server safe to use?

Gmail Agent by Nova (CIVAI) scores 62 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 Gmail Agent by Nova (CIVAI) MCP server expose?

Gmail Agent by Nova (CIVAI) exposes 4 tools: compose_email, read_single_email, latest_emails, converse. Their descriptions and schemas cost roughly 123 tokens of context every time the server is loaded.

Does the Gmail Agent by Nova (CIVAI) MCP server require authentication?

Yes. Gmail 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 Gmail Agent by Nova (CIVAI) MCP server still maintained?

Gmail Agent by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 21 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 Gmail Agent by Nova (CIVAI) MCP server?

VerifyMCP ran 12 checks on Gmail Agent by Nova (CIVAI), covering Authorization, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Gmail Agent by Nova (CIVAI): TLS certificate. 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.