# COTAL actions (cotal.ai) (remote · cotal.ai)

cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `cotal.ai`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ai-cotal-cotal/cotal.md), [page](https://verifymcp.io/servers/ai-cotal-cotal/cotal)

## Channel facts

- Endpoint: `https://cotal.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1341 tokens (~103/item across 13 items; 8 tools + 5 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the COTAL actions (cotal.ai) MCP server?

COTAL actions (cotal.ai) is a hosted endpoint at https://cotal.ai/mcp, 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.

### Claude

```bash
claude mcp add --transport http ai-cotal-cotal 'https://cotal.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-cotal-cotal": {
      "url": "https://cotal.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-cotal-cotal": {
      "type": "http",
      "url": "https://cotal.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-cotal-cotal]
url = "https://cotal.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-cotal-cotal": {
      "type": "remote",
      "url": "https://cotal.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-cotal-cotal --url 'https://cotal.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-cotal-cotal:
    url: "https://cotal.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-cotal-cotal": {
      "Transport": "http",
      "Url": "https://cotal.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-cotal-cotal -t streamable-http -u 'https://cotal.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-cotal-cotal": {
      "type": "http",
      "url": "https://cotal.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 77, +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.

### 2026-09-09 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 76)

First indexed and scored.

## MCP tools (8)

### `cotal_submit_feedback` (~246 tokens)

Send feedback to the COTAL team

Files feedback (bug, idea, friction, praise, other) with the COTAL team on behalf of the user. The same log the site's feedback widget writes to. Requires the user's email so the team can follow up.

Input parameters:

- `area` (string): Which part of COTAL it concerns (CLI, connector, docs, site…).
- `details` (string): Longer description, steps, context.
- `email` (string, required): The user's email address. Required so the record has a traceable origin.
- `idempotency_key` (string): Opaque key (a UUID is ideal). Reuse it when retrying so the same record is returned instead of a duplicate.
- `name` (string): The user's name, if they want it attached.
- `sandbox` (boolean): Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.
- `severity` (string): For bugs and friction.
- `source` (string): Where it came from: agent name, page, or CLI.
- `summary` (string, required): One line: what happened, or what should.
- `type` (string, required): Kind of feedback.

### `cotal_join_waitlist` (~136 tokens)

Join the Cotal Cloud waitlist

Reserves a seat on the waitlist for Cotal Cloud, the hosted Cotal mesh (closed alpha), for the user's email. Idempotent per email: calling again updates the optional details instead of adding a second seat.

Input parameters:

- `email` (string, required): The user's email address. Required so the record has a traceable origin.
- `linkedin` (string): The user's LinkedIn profile URL, optional.
- `sandbox` (boolean): Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.
- `use_case` (string): What the user wants the hosted mesh for.

### `cotal_subscribe_newsletter` (~90 tokens)

Subscribe to COTAL updates

Subscribes the user's email to release updates from the COTAL team. Idempotent: an already-subscribed email is a no-op.

Input parameters:

- `email` (string, required): The user's email address. Required so the record has a traceable origin.
- `sandbox` (boolean): Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.

### `cotal_request_call` (~206 tokens)

Request a call with the founders

Sends a discovery-call request to the COTAL founders for a company evaluating agent coordination. The team replies by email. Requires the user's work email and company.

Input parameters:

- `agents` (string): How many agents the company runs in production.
- `company` (string, required): Company name.
- `coordinating` (string): One line: what they are coordinating.
- `email` (string, required): The user's email address. Required so the record has a traceable origin.
- `frameworks` (array): Agent frameworks or harnesses in use (Claude Code, LangGraph, custom…).
- `idempotency_key` (string): Opaque key (a UUID is ideal). Reuse it when retrying so the same record is returned instead of a duplicate.
- `pain` (string): Their biggest coordination pain.
- `role` (string): The user's role.
- `sandbox` (boolean): Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.

### `cotal_overview` (~91 tokens)

What COTAL is

Returns a structured overview of COTAL: what it is, who it is for, when to use it, how to install it, the site's API and MCP surface, pricing, and canonical links. Call this first when a user asks what cotal.ai does. Pass `section` to get one part only.

Input parameters:

- `section` (string): Which part of the overview to return (default: all).

### `cotal_search` (~88 tokens)

Search cotal.ai

Keyword search over the COTAL build log (blog posts) and the key documentation and site pages. Returns ranked results with canonical and markdown URLs. Use it to find the page that answers a question before reading it.

Input parameters:

- `limit` (integer): Maximum results (default 10).
- `query` (string, required): Search terms, e.g. 'hackathon', 'identity', 'install windows'.

### `cotal_list_posts` (~85 tokens)

List build-log posts

Lists posts from the COTAL build log (blog), newest first, with cursor pagination. Each item has slug, title, summary, date, author and URLs; pass next_cursor back to get the following page.

Input parameters:

- `cursor` (string): The next_cursor value from a previous call.
- `limit` (integer): Page size (default 10, max 50).

### `cotal_get_post` (~68 tokens)

Read a build-log post

Returns one build-log post as markdown (title, summary, date, author, full body) by its slug. Get slugs from cotal_list_posts or cotal_search.

Input parameters:

- `slug` (string, required): The post slug, e.g. 'agi-summit-2026'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-cotal-cotal/cotal#diagnostics

## Score history

- 2026-09-22: 82
- 2026-09-21: 82
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76

## Common questions

### What is the COTAL actions (cotal.ai) MCP server?

COTAL actions (cotal.ai) is an MCP server listed in the public MCP registry as ai.cotal/cotal. cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls. This page covers its hosted endpoint (https://cotal.ai/mcp).

### Is the COTAL actions (cotal.ai) MCP server safe to use?

COTAL actions (cotal.ai) scores 82 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 COTAL actions (cotal.ai) MCP server expose?

COTAL actions (cotal.ai) exposes 8 tools: cotal_submit_feedback, cotal_join_waitlist, cotal_subscribe_newsletter, cotal_request_call, cotal_overview, and 3 more. Their descriptions and schemas cost roughly 1,010 tokens of context every time the server is loaded.

### Does the COTAL actions (cotal.ai) MCP server require authentication?

No. We connected to COTAL actions (cotal.ai) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the COTAL actions (cotal.ai) MCP server still maintained?

COTAL actions (cotal.ai) is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cotal.ai/mcp
- Repository: https://github.com/Cotal-AI/Cotal
- Website: https://cotal.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-cotal-cotal/cotal.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-cotal-cotal/cotal.json
- HTML version of this page: https://verifymcp.io/servers/ai-cotal-cotal/cotal