Servidor MCP de Coolant

• Nome no registrorun.coolant/coolantverificado no registro MCP

O nome no registro fica sob coolant.run. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-11-02
• Ferramentas28
• O servidor se chamacoolant
• Versão do servidor1.0.0
• Versão do protocolo2025-06-18

Em 2026-11-02 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 685 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 1 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 1 até agora
• Respondeumedindo1 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta238 ms
• Espaço no contexto do agente≈ 3.826 tokensas definições de todas as ferramentas (28), que o agente carrega a cada turno
• Definições das ferramentasB · 82 de 100
• Resultados tipados0 de 28 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 3 de 28
• Sem dizer se só lê ou se pode destruir: 28 de 28

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e 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.