Twitter Agent by Nova (CIVAI)
REMOTE · NOVA.CIVAI.CO
I do everything related to Twitter posting and campaigns
Available components
Last scanned (20 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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 Usability59
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 336 tokens (~33/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management22
- Stability check failed: schema churn in the 30 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 9 additions. See how to fix → Fail
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_dm" 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 10 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.
- 21 Nov 26 +4
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- 6 Nov 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
- 1 Nov 26 −12
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “debug_update_existing_code” was removed ▼ security
- Tool “generate_and_execute_code” was removed ▼ security
- Tool “generate_code_only” was removed ▼ security
- Schema quality: 130 → 336 ▼ functional
- Tool coverage: 100% → 65% ▼ functional
- New tool “follow_user” functional
- New tool “get_mentions” functional
- New tool “get_thread” functional
- New tool “like_tweet” functional
- New tool “post_tweet” functional
- New tool “post_twitter_thread” functional
- New tool “retweet” functional
- New tool “search_tweets” functional
- New tool “send_dm” functional
- 29 Oct 26 +14
- Stability: fail → pass ▲ security
- 13 Oct 26 0
- HSTS header: unverified → fail ▼ security
- 12 Oct 26 0
- HSTS header: fail → unverified ▼ security
- 3 Oct 26 0
- Stability: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 1.27.0 → 1.0.0 functional
- 2 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
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/twitter-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=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/twitter-agent", scope="mcp:access"
Bearer resource_metadata="https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/twitter-agent", scope="mcp:access" Protected resource metadata
| Document | https://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/twitter-agent |
|---|---|
| Retrieved | Yes |
| Resource | https://nova.civai.co/mcp/agents/twitter-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/twitter-agent | Verified | 200 | |
| http (plaintext) | http://nova.civai.co/mcp/agents/twitter-agent | HTTPS enforced | 301 | https://nova.civai.co/mcp/agents/twitter-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 →
converse ~33
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.
follow_user ~28
X / Twitter: follow user
| Name | Type | Req | Description |
|---|---|---|---|
| usernames | array | – | Handles to follow (without @) |
No output schema declared.
No examples provided.
get_mentions ~29
X / Twitter: get mentions
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many mentions (1-50) |
No output schema declared.
No examples provided.
get_thread ~31
X / Twitter: get thread
| Name | Type | Req | Description |
|---|---|---|---|
| tweet_id | string | – | – |
| tweet_url | string | – | – |
No output schema declared.
No examples provided.
like_tweet ~32
X / Twitter: like tweet
| Name | Type | Req | Description |
|---|---|---|---|
| tweet_id | string | – | – |
| tweet_url | string | – | – |
No output schema declared.
No examples provided.
post_tweet ~38
X / Twitter: post tweet
| Name | Type | Req | Description |
|---|---|---|---|
| schedule_hint | string | – | Optional timing hint |
| topic | string | – | Tweet topic or angle |
No output schema declared.
No examples provided.
post_twitter_thread ~40
X / Twitter: post twitter thread
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Thread topic |
| tweet_count | integer | – | Approximate number of tweets |
No output schema declared.
No examples provided.
retweet ~31
X / Twitter: retweet
| Name | Type | Req | Description |
|---|---|---|---|
| tweet_id | string | – | – |
| tweet_url | string | – | – |
No output schema declared.
No examples provided.
search_tweets ~39
X / Twitter: search tweets
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Max results (1-20) |
| query | string | – | X search query |
No output schema declared.
No examples provided.
send_dm ~35
X / Twitter: send dm
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | DM body |
| username | string | – | Recipient handle without @ |
No output schema declared.
No examples provided.
How do I install the Twitter Agent by Nova (CIVAI) MCP server?
Twitter Agent by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/twitter-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-twitter-agent 'https://nova.civai.co/mcp/agents/twitter-agent'
What is the Twitter Agent by Nova (CIVAI) MCP server?
Twitter Agent by Nova (CIVAI) is an MCP server listed in the public MCP registry as co.civai.nova/twitter-agent. I do everything related to Twitter posting and campaigns. This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/twitter-agent).
Is the Twitter Agent by Nova (CIVAI) MCP server safe to use?
Twitter 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 Twitter Agent by Nova (CIVAI) MCP server expose?
Twitter Agent by Nova (CIVAI) exposes 10 tools: post_twitter_thread, post_tweet, follow_user, search_tweets, get_thread, and 5 more. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.
Does the Twitter Agent by Nova (CIVAI) MCP server require authentication?
Yes. Twitter 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 Twitter Agent by Nova (CIVAI) MCP server still maintained?
Twitter 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 Twitter Agent by Nova (CIVAI) MCP server?
VerifyMCP ran 13 checks on Twitter Agent 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.