Slack MCP by Nova (CIVAI)
REMOTE · NOVA.CIVAI.CO
Use Slack from chat: see channels, catch up on messages, post updates, and reply in threads in your…
Available components
Last scanned (19 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Communication
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 Usability75
- 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 1135 tokens (~56/item across 20 items; 17 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% 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; "delete_message" 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 18 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 72
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 4 Nov 2026 · Probed https://nova.civai.co/mcp/agents/mcp-slack_android
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. | 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/mcp-slack_android | Verified | 400 | |
| http (plaintext) | http://nova.civai.co/mcp/agents/mcp-slack_android | HTTPS enforced | 301 | https://nova.civai.co/mcp/agents/mcp-slack_android |
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 →
channel_info ~60
Channel name and member count for a channel id.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
confirm_email_signin ~58
Start Slack email sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| slack_email | string | – | – |
No output schema declared.
No examples provided.
conversation_history ~65
Fetch recent messages in a channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| history_limit | string | – | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
create_channel ~70
Create a channel (may be restricted on some workspaces).
| Name | Type | Req | Description |
|---|---|---|---|
| channel_name | string | yes | – |
| is_private | string | – | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
delete_message ~64
Delete one of your messages.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| message_ts | string | yes | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
list_channel_members ~68
List member user ids in a Slack channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| members_limit | string | – | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
list_channels ~54
List Slack channels and group DMs (mobile client.channels).
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
list_workspace_users ~57
List users in the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| users_limit | string | – | – |
No output schema declared.
No examples provided.
list_workspaces ~50
List workspaces after email confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
open_conversation ~62
Open a DM conversation with a Slack user id.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| slack_user_id | string | yes | – |
No output schema declared.
No examples provided.
post_message ~73
Post a message to a Slack channel or DM using the mobile user session.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| message_text | string | yes | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
post_message_rich ~72
Post using mobile Block Kit blocks (message_blocks_json).
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| message_blocks_json | string | yes | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
reply_thread ~73
Post a reply in a thread.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| message_text | string | yes | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| thread_ts | string | yes | – |
No output schema declared.
No examples provided.
search_people ~74
Search people by name or email fragment.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| people_count | string | – | – |
| people_page | string | – | – |
| search_query | string | yes | – |
No output schema declared.
No examples provided.
session_status ~52
Verify Slack mobile session (run before other tools).
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
thread_replies ~73
Read messages in a thread.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| replies_limit | string | – | – |
| thread_ts | string | yes | – |
No output schema declared.
No examples provided.
user_boot ~48
Workspace client bootstrap after login.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_message | string | – | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
No output schema declared.
No examples provided.
How do I install the Slack MCP by Nova (CIVAI) server?
Slack MCP by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/mcp-slack_android, 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-mcp-slack-android 'https://nova.civai.co/mcp/agents/mcp-slack_android'
What is the Slack MCP by Nova (CIVAI) server?
Slack MCP by Nova (CIVAI) is listed in the public MCP registry as co.civai.nova/mcp-slack_android. Use Slack from chat: see channels, catch up on messages, post updates, and reply in threads in your… This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/mcp-slack_android).
Is the Slack MCP by Nova (CIVAI) server safe to use?
Slack MCP by Nova (CIVAI) scores 73 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 Slack MCP by Nova (CIVAI) server expose?
Slack MCP by Nova (CIVAI) exposes 17 tools: session_status, list_channels, channel_info, list_channel_members, list_workspace_users, and 12 more. Their descriptions and schemas cost roughly 1,073 tokens of context every time the server is loaded.
Does the Slack MCP by Nova (CIVAI) server require authentication?
Yes. Slack MCP 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 Slack MCP by Nova (CIVAI) server still maintained?
Slack MCP by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.