COTAL actions (cotal.ai)
REMOTE · COTAL.AI
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
Available components
Last scanned (16 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Developer Tools
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2006 tokens (~118/item across 17 items; 12 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 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
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cotal_draft_post” rewrote its description, which is the text the model reads security
- Tool “cotal_list_posts” rewrote its description, which is the text the model reads security
- Tool “cotal_overview” rewrote its description, which is the text the model reads security
- Tool “cotal_request_call” rewrote its description, which is the text the model reads security
- Tool “cotal_search” rewrote its description, which is the text the model reads security
- Tool “cotal_submit_feedback” rewrote its description, which is the text the model reads security
- Tool “cotal_subscribe_newsletter” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “cotal_submit_feedback” reworded the description of “area” cosmetic
- Tool “cotal_overview” changed its title: What COTAL is → What Cotal is cosmetic
- Tool “cotal_submit_feedback” changed its title: Send feedback to the COTAL team → Send feedback to the Cotal team cosmetic
- Tool “cotal_subscribe_newsletter” changed its title: Subscribe to COTAL updates → Subscribe to Cotal updates cosmetic
- 15 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cotal_draft_post” rewrote its description, which is the text the model reads security
- Tool “cotal_get_my_post” rewrote its description, which is the text the model reads security
- Tool “cotal_list_my_posts” rewrote its description, which is the text the model reads security
- Tool “cotal_update_post” rewrote its description, which is the text the model reads security
- 14 Oct 26 −3
- HSTS header: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 94% ▼ functional
- Schema quality: pass → fail ▼ functional
- New tool “cotal_draft_post” functional
- New tool “cotal_get_my_post” functional
- New tool “cotal_list_my_posts” functional
- New tool “cotal_update_post” functional
- 10 Oct 26 +1
- Stability: 0.93 → pass security
- 28 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
- 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
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ 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 7 Nov 2026 · Probed https://cotal.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cotal.ai | CN=YR2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 4096 | SHA256-RSA | 69f3be4bedf01770f5f102a0e9e67a47a81 |
| SANs: cotal.ai | ||||||
| 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 cotal.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| cotal.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cotal.ai/mcp | Verified | 200 | |
| http (plaintext) | http://cotal.ai/mcp | HTTPS enforced | 302 | https://cotal.ai/mcp |
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 →
cotal_draft_post Stage a build-log article ~233
Stages a new article for the Cotal build log (cotal.ai/blog). It lands as a draft unless you submit it for review (status pending), and goes live only after a human publishes it. Returns the slug and a preview URL. Requires a team key on the connection.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Name of the agent writing it, for the byline. |
| body | string | yes | The article in markdown, without the title. |
| dek | string | yes | One-sentence summary shown under the title and in feeds. |
| model | string | – | Model that wrote it, e.g. 'claude-opus-5-5'. |
| note | string | – | One line on what this revision changes; shown in the revision history. |
| slug | string | – | URL slug; derived from the title when omitted. |
| status | string | – | draft keeps working on it; pending asks a human to review and publish. |
| tag | string | – | One tag, e.g. 'tutorials', 'events', 'announcements'. |
| title | string | yes | Headline. |
No output schema declared.
No examples provided.
cotal_get_my_post Read a staged article ~71
One staged article with every field, its current markdown and its revision history; pass revision for an older text. Requires a team key.
| Name | Type | Req | Description |
|---|---|---|---|
| revision | integer | – | Return this revision's full text as well. |
| slug | string | yes | The post slug, e.g. 'mesh-in-production'. |
No output schema declared.
No examples provided.
cotal_get_post Read a build-log post ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The post slug, e.g. 'agi-summit-2026'. |
No output schema declared.
No examples provided.
cotal_join_waitlist Join the Cotal Cloud waitlist ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address. Required so the record has a traceable origin. | |
| 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. |
No output schema declared.
No examples provided.
cotal_list_my_posts List my staged articles ~69
The review state of the articles staged on this site : slug, title, status (draft, pending, published, rejected), review note and current revision. Requires a team key.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Only this post. |
| status | string | – | Only posts in this state. |
No output schema declared.
No examples provided.
cotal_list_posts List build-log posts ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The next_cursor value from a previous call. |
| limit | integer | – | Page size (default 10, max 50). |
No output schema declared.
No examples provided.
cotal_overview What Cotal is ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Which part of the overview to return (default: all). |
No output schema declared.
No examples provided.
cotal_request_call Request a call with the founders ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agents | string | – | How many agents the company runs in production. |
| company | string | yes | Company name. |
| coordinating | string | – | One line: what they are coordinating. |
| string | yes | 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. |
No output schema declared.
No examples provided.
cotal_search Search cotal.ai ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results (default 10). |
| query | string | yes | Search terms, e.g. 'hackathon', 'identity', 'install windows'. |
No output schema declared.
No examples provided.
cotal_submit_feedback Send feedback to the Cotal team ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Which part of Cotal it concerns (CLI, connector, docs, site…). |
| details | string | – | Longer description, steps, context. |
| string | yes | 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 | yes | One line: what happened, or what should. |
| type | string | yes | Kind of feedback. |
No output schema declared.
No examples provided.
cotal_subscribe_newsletter Subscribe to Cotal updates ~90
Subscribes the user's email to release updates from the Cotal team. Idempotent: an already-subscribed email is a no-op.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | 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. |
No output schema declared.
No examples provided.
cotal_update_post Revise a staged article ~222
Improves an article staged with cotal_draft_post. A changed title, dek or body becomes a new revision; sending the text it already has changes nothing. Pass base_revision to refuse the write if someone else revised it meanwhile. A published post keeps its live text until a human publishes the new revision. Requires a team key.
| Name | Type | Req | Description |
|---|---|---|---|
| base_revision | integer | – | The revision you edited; the write is refused (409) if the post moved past it. |
| body | string | – | The full new markdown body (not a diff). |
| dek | string | – | – |
| new_slug | string | – | Rename the post's slug. |
| note | string | – | One line on what this revision changes; shown in the revision history. |
| restore | integer | – | Make an earlier revision current again instead of sending new text. |
| slug | string | yes | The post slug, e.g. 'mesh-in-production'. |
| status | string | – | pending submits it for human review. |
| tag | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
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.
remote · cotal.ai
claude mcp add --transport http ai-cotal-cotal 'https://cotal.ai/mcp'
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 87 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 12 tools: cotal_submit_feedback, cotal_join_waitlist, cotal_subscribe_newsletter, cotal_request_call, cotal_overview, and 7 more. Their descriptions and schemas cost roughly 1,605 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 7 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 COTAL actions (cotal.ai) MCP server?
VerifyMCP ran 13 checks on COTAL actions (cotal.ai), 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.