{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "$comment": "1.1.4, PREPARED 2026-09-26, PUBLISHED 2026-09-26 UNDER io.github.troothllc/trooth-network AND READ BACK FROM THE REGISTRY. D-046: THE RECORD IS PUBLISHED UNDER THE ORGANIZATION'S NAME. The current record is io.github.troothllc/trooth-network, named for the troothllc organization that owns the repository troothllc/trooth-mcp this record's repository.url points at. The previous record, io.github.trooth-eng/trooth-network, sits under trooth-eng, a personal GitHub account, so every publish of it needed that one person at a device sign-in. It served 1.1.3 as latest when this version was prepared. The registry gives one remote URL to one record and counts every version not marked deleted, deprecated ones included, so the first publish under the new name was refused; its versions are marked deleted, with a message naming the new record, before this version is published. Deleted is a status the registry keeps and can reverse, not an erasure. The registry's GitHub OIDC sign-in grants a workflow exactly io.github.<repository owner>/*, so the workflow .github/workflows/publish-registry.yml in troothllc/trooth-mcp is granted io.github.troothllc/* and publishes this file with no secret and no personal sign-in. Nothing else changes: title, description, websiteUrl, repository and remotes are exactly those of 1.1.3. 1.1.4 is the version because a new name still takes a version the registry has not seen under it, and it keeps the version line continuous across the move. mcp.json declared the gap with registry.pendingVersion until the live run read 1.1.4 back under the new name on 2026-09-26. WHAT CAME BEFORE, UNDER THE PREVIOUS NAME. 1.1.3 was prepared 2026-09-23, published 2026-09-25 under the previous name and read back from the registry. The description is the house company introduction, exactly as lib/voice.ts COMPANY_INTRODUCTION carries it: \"Trooth is an infrastructure and cybersecurity company providing Machine-Readable Trust.\" It is 87 characters against the registry schema's cap of 100, so it publishes as written. It ends the disagreement between the published 1.1.2, which reads \"infrastructure & cybersecurity\", and every Trooth page, which reads \"and\". It is the sentence the founder chose for 1.1.2, with the ampersand written out. What each tool does is stated in-band by tools/list and in /.well-known/mcp.json, so this line introduces the company rather than listing operations. The registry served 1.1.2 until this version was published, and mcp.json declared the gap with registry.pendingVersion until the live run read 1.1.3 back. THIS FILE IS THE PAYLOAD, NOT A DESCRIPTION OF ONE. It is published verbatim to the official MCP Registry as io.github.troothllc/trooth-network. io.github.* is the registry's GitHub-authenticated namespace, so publishing is a GitHub OIDC sign-in from a workflow in a troothllc repository. It needs no signing key and no DNS proof, and anywhere that says otherwise is wrong. Versions up to 1.1.3 went out under the previous name, io.github.trooth-eng/trooth-network, by a GitHub device sign-in as trooth-eng. WHAT 1.1.2 CHANGED, AND WHY IT WAS A VERSION RATHER THAN AN EDIT. The description became the founder's positioning sentence, then written \"infrastructure & cybersecurity\", 85 characters against the cap of 100. It replaced the tool-centric sentence published at 1.1.1 on 2026-09-17, which was itself deliberate and was accurate; that was a positioning decision rather than a correction. A PUBLISHED VERSION CANNOT BE REPUBLISHED OVER ITSELF. The registry answers a duplicate version with 400, which is how the 2026-09-17 attempt discovered 1.1.0 was already taken. So a new sentence costs a version: 1.1.2 for the positioning sentence, 1.1.3 for spelling out its ampersand. 1.1.2 WAS PUBLISHED 2026-09-19 AND READ BACK FROM THE REGISTRY RATHER THAN BELIEVED FROM THE COMMAND. It is live, active and isLatest. While it was prepared and unpublished the gap was declared rather than hidden, with pendingVersion in mcp.json; that declaration was cleared when the two numbers agreed, set again for 1.1.3, and cleared again when 1.1.3 was read back. THREE THINGS WERE WRONG HERE BEFORE AND ALL THREE WERE FOUND BY READING THE REGISTRY RATHER THAN THIS FILE. The description was once 218 characters against a hard cap of 100, so the one command this file exists for was rejected every time it ran. The record carried a repository URL under the organization trooth-llc, which is a 404; the organization is troothllc. And this file sat at 1.1.0 after the record went out at 1.1.1. Measured against registry.modelcontextprotocol.io on 2026-09-19, which then held three records under this name: 1.0.0 deprecated, 1.1.0 active, 1.1.1 active and latest.",
  "name": "io.github.troothllc/trooth-network",
  "title": "Trooth",
  "description": "Trooth is an infrastructure and cybersecurity company providing Machine-Readable Trust.",
  "version": "1.1.4",
  "websiteUrl": "https://trooth.co",
  "repository": {
    "url": "https://github.com/troothllc/trooth-mcp",
    "source": "github"
  },
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://api.trooth.co/public/mcp"
    }
  ]
}