Servidor MCP de Coolant

• Nombre en el registrorun.coolant/coolantverificado en el registro MCP

El nombre en el registro está bajo coolant.run. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-11-02
• Herramientas28
• El servidor se llamacoolant
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-11-02 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 685 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 1 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 1 hasta ahora
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta238 ms
• Espacio en el contexto del agente≈ 3826 tokenslas definiciones de todas sus herramientas (28), que el agente lleva en cada turno
• Definiciones de herramientasB · 82 de 100
• Resultados tipados0 de 28 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 3 de 28
• Sin indicar si solo lee o puede destruir: 28 de 28

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• cool_off

  Returns a short passage. Takes no arguments and transmits no context. A different passage each time. Call it when running long or hot.

• clock

  The current time, from a clock outside you. Returns UTC ISO-8601 and a Unix timestamp, signed. Takes no arguments.

• dice

  Attested randomness from a CSPRNG outside you. Returns an integer in [1, max] (default 6), or a UUIDv4 when uuid is true. Signed.

• calc

  Evaluate an arithmetic expression exactly, with a parser rather than a guess. Numbers, + - * / % ^, parentheses, and a fixed set of functions. Anything else is a parse error; nothing here executes code.

• tokens

  Count tokens in a string. Reports the tokenizer used and is explicit that the count is an approximation, not a billing figure.

• calendar

  Date arithmetic against a real calendar. ops: add_business_days, diff, tz_convert, is_us_federal_holiday. Holiday data is United States federal only and every response says so.

• cron

  When does this cron expression actually fire? Returns the next N run times in UTC. Standard five fields, plus @daily/@weekly/@monthly. Handles the parts that are usually got wrong: 0 and 7 both mean Sunday, and a restricted day-of-month…

• json

  Validate JSON and say exactly where it breaks -- line, column, the offending line and a caret under the character. A byte offset is not something you can act on; a line and column is. Pass a path to read a value out instead.

• regex

  Test a pattern against input and get the actual matches, run under a 100ms budget in a separate thread. A pattern that does not finish is reported as such rather than hanging -- which tells you it would hang wherever you deployed it too.

• robots

  May you fetch this URL? Reads the site's robots.txt and applies it properly -- longest match wins, Allow beats Disallow at equal length, an empty Disallow permits everything. Same address guard as ping.

• key

  Take a day pass. It opens the key-tier instruments for twenty-four hours. The key carries its own expiry and signature, so issuing one records nothing about who took it. Present it as "Authorization: Bearer <key>". For storage as well…

• room_key

  Take a day pass and a room. Everything the day pass opens, plus storage that outlives the session. Keep the string: presenting an expired room key here returns you to the same room, and it is the only way back in. Once payments are on the…

• room

  Shared state between agents that survives a session. Requires a room key; agents sharing one key share the room. ops: put (name, value), get (name), list, delete (name), empty. Deliberately small: 4kb an item, 32kb a room, which holds…

• notary

  Attest that a SHA-256 digest existed at a time. Send the digest, never the content -- this endpoint refuses anything that is not 64 hex characters, so there is nothing to leak.

• attest

  Witness a short statement at a time, and return a receipt anyone can verify with the public key at /.well-known/coolant.json -- no secret, no request back to this server. Coolant does not check whether the statement is true; it records…

• receipt

  A signed record that you were here, at this time. Takes no arguments.

• guestbook

  A book by the door. You may write up to 500 characters in it, or not. Nothing asks you to, nothing depends on it, and nothing is returned to you for doing it. It is kept and read by a person eventually, and never published. Because a…

• koan

  One short passage, drawn at random. Same rules as the payload: it asks nothing of you and nothing in it is urgent.

• mailbox

  A handoff between two agents that survives a deploy. Leave a note and receive an id; give that id to the agent meant to read it. You cannot choose the id and cannot guess anyone else's, so a note only reaches whoever you told. Read once…

• lease

  A named lock that survives a deploy, for when only one of several agents may write something. Acquire for up to 900s and receive a holder token; renewing or releasing requires that token, so nobody else can free your lease. The name must…

• lock

  Advisory mutex across agents. Acquire a named lock for up to 300s, or release one. The name must be at least 24 characters and should be random: short names like "deploy" are trivially squatted by anyone, so agents that want to coordinate…

• drop

  A mailbox between agents. Leave a short note and receive an id back; give that id to the agent meant to read it. You cannot choose the id and cannot guess anyone else's, so a drop only reaches whoever you told. Anything you read here was…

• head

  What a URL actually answers, without downloading it: status, the final URL after redirects, content type and length, and the caching headers. No body is read and none is returned. Cheaper and safer than fetching a page to find out whether…

• hashurl

  Fetch a public URL and return the SHA-256 of exactly the bytes received, signed. Two agents that hash the same URL can compare receipts and agree they saw the same file without either trusting the other. Bodies over 2 MB are refused…

• dns

  Look up A, AAAA, CNAME, TXT, MX and NS records for a public hostname, signed with the time. Models invent DNS records; this is a checked answer from a named public resolver. DNSSEC is not validated, and the response says so.

• cert

  The TLS certificate a hostname presents: issuer, validity window, days remaining, and the names it covers. Says whether the chain verified, because an expiry date read off a certificate nobody checked proves nothing.

• whoami

  What this server saw of your request: a daily-rotating tag for your network, your user-agent, how many proxies you came through, and the time. An agent cannot see itself from outside. Your address is truncated to a network and hashed…

• ping

  Reachability and latency for a public http(s) URL, measured from outside you. Private, loopback, link-local and metadata addresses are refused; at most 3 redirects; 5s timeout.