accueil / serveurs / Recherche & Web / ai.cotal/cotal
ai.cotal/cotal
serveur MCP (Model Context Protocol) · cotal 1.1.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que ai.cotal/cotal est sûr ?
Au dernier audit MCP Hub, le serveur MCP « ai.cotal/cotal » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 12 outils
- cotal_draft_post≈ 420 tokens
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.
Paramètres, retour & exemple (9)
Paramètresdek· string · requis
One-sentence summary shown under the title and in feeds.tag· string · optionnel
One tag, e.g. 'tutorials', 'events', 'announcements'.body· string · requis
The article in markdown, without the title.note· string · optionnel
One line on what this revision changes; shown in the revision history.slug· string · optionnel
URL slug; derived from the title when omitted.agent· string · optionnel
Name of the agent writing it, for the byline.model· string · optionnel
Model that wrote it, e.g. 'claude-opus-5-5'.title· string · requis
Headline.status· string · optionnel · draft | pending
draft keeps working on it; pending asks a human to review and publish.
Exemple d'appel{"name": "cotal_draft_post", "arguments": {"dek": "texte", "body": "texte", "title": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_get_my_post≈ 180 tokens
One staged article with every field, its current markdown and its revision history; pass revision for an older text. Requires a team key.
Paramètres, retour & exemple (2)
Paramètresslug· string · requis
The post slug, e.g. 'mesh-in-production'.revision· integer · optionnel
Return this revision's full text as well.
Exemple d'appel{"name": "cotal_get_my_post", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_get_post≈ 146 tokens
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.
Paramètres, retour & exemple (1)
Paramètresslug· string · requis
The post slug, e.g. 'agi-summit-2026'.
Exemple d'appel{"name": "cotal_get_post", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_join_waitlist≈ 300 tokens
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.
Paramètres, retour & exemple (4)
Paramètresemail· string · requis
The user's email address. Required so the record has a traceable origin.sandbox· boolean · optionnel
Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.linkedin· string · optionnel
The user's LinkedIn profile URL, optional.use_case· string · optionnel
What the user wants the hosted mesh for.
Exemple d'appel{"name": "cotal_join_waitlist", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_list_my_posts≈ 176 tokens
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.
Paramètres, retour & exemple (2)
Paramètresslug· string · optionnel
Only this post.status· string · optionnel · draft | pending | published | rejected
Only posts in this state.
Exemple d'appel{"name": "cotal_list_my_posts", "arguments": {"slug": "texte", "status": "draft"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_list_posts≈ 174 tokens
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.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Page size (default 10, max 50).cursor· string · optionnel
The next_cursor value from a previous call.
Exemple d'appel{"name": "cotal_list_posts", "arguments": {"limit": 1, "cursor": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_overview≈ 184 tokens
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.
Paramètres, retour & exemple (1)
Paramètressection· string · optionnel · all | product | when_to_use | install | pricing | site_api | links
Which part of the overview to return (default: all).
Exemple d'appel{"name": "cotal_overview", "arguments": {"section": "all"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_request_call≈ 464 tokens
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.
Paramètres, retour & exemple (9)
Paramètrespain· string · optionnel
Their biggest coordination pain.role· string · optionnel
The user's role.email· string · requis
The user's email address. Required so the record has a traceable origin.agents· string · optionnel · 1 | exploring | 2-5 | 6-20 | 20+
How many agents the company runs in production.company· string · requis
Company name.sandbox· boolean · optionnel
Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.frameworks· array · optionnel
Agent frameworks or harnesses in use (Claude Code, LangGraph, custom…).coordinating· string · optionnel
One line: what they are coordinating.idempotency_key· string · optionnel
Opaque key (a UUID is ideal). Reuse it when retrying so the same record is returned instead of a duplicate.
Exemple d'appel{"name": "cotal_request_call", "arguments": {"email": "texte", "company": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_search≈ 196 tokens
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.
Paramètres, retour & exemple (2)
Paramètreslimit· integer · optionnel
Maximum results (default 10).query· string · requis
Search terms, e.g. 'hackathon', 'identity', 'install windows'.
Exemple d'appel{"name": "cotal_search", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_submit_feedback≈ 496 tokens
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.
Paramètres, retour & exemple (10)
Paramètresarea· string · optionnel
Which part of COTAL it concerns (CLI, connector, docs, site…).name· string · optionnel
The user's name, if they want it attached.type· string · requis · bug | idea | friction | praise | other
Kind of feedback.email· string · requis
The user's email address. Required so the record has a traceable origin.source· string · optionnel
Where it came from: agent name, page, or CLI.details· string · optionnel
Longer description, steps, context.sandbox· boolean · optionnel
Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.summary· string · requis
One line: what happened, or what should.severity· string · optionnel · low | medium | high
For bugs and friction.idempotency_key· string · optionnel
Opaque key (a UUID is ideal). Reuse it when retrying so the same record is returned instead of a duplicate.
Exemple d'appel{"name": "cotal_submit_feedback", "arguments": {"type": "bug", "email": "texte", "summary": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_subscribe_newsletter≈ 220 tokens
Subscribes the user's email to release updates from the COTAL team. Idempotent: an already-subscribed email is a no-op.
Paramètres, retour & exemple (2)
Paramètresemail· string · requis
The user's email address. Required so the record has a traceable origin.sandbox· boolean · optionnel
Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.
Exemple d'appel{"name": "cotal_subscribe_newsletter", "arguments": {"email": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - cotal_update_post≈ 437 tokens
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.
Paramètres, retour & exemple (10)
Paramètresdek· string · optionneltag· string · optionnelbody· string · optionnel
The full new markdown body (not a diff).note· string · optionnel
One line on what this revision changes; shown in the revision history.slug· string · requis
The post slug, e.g. 'mesh-in-production'.title· string · optionnelstatus· string · optionnel · draft | pending
pending submits it for human review.restore· integer · optionnel
Make an earlier revision current again instead of sending new text.new_slug· string · optionnel
Rename the post's slug.base_revision· integer · optionnel
The revision you edited; the write is refused (409) if the post moved past it.
Exemple d'appel{"name": "cotal_update_post", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».