Trooth

Trooth is an infrastructure and cybersecurity company providing Machine-Readable Trust.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
100%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,762Tokens (definiciones de herramientas)
~4.0 KBTamaño de respuesta típico
Impacto moderado en la atención (1.38% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "trooth-network": {
      "url": "https://api.trooth.co/public/mcp"
    }
  }
}

Puntos de conexión remotos

https://api.trooth.co/public/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (4)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢trooth_public_trust_profile(company)

Read one company's published record on the Trooth Network, given its domain or Trooth slug. The identifier is matched exactly (a URL is reduced to its host), never by a similar name. Returns a status (published, listed, private, unclaimed or unavailable) and a provenance label; text the company wrote about itself is labeled as its own words. Read only.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "company": {
      "type": "string",
      "description": "Company domain (e.g. acme.com) or Trooth slug"
    }
  },
  "required": [
    "company"
  ]
}

Esquema de salida

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Machine-branchable outcome for this lookup.",
      "enum": [
        "published",
        "listed",
        "unclaimed",
        "private",
        "observed",
        "valid",
        "invalid",
        "expired",
        "revoked",
        "answered",
        "out_of_scope",
        "bad_input",
        "unavailable"
      ]
    },
    "provenance": {
      "type": "string",
      "description": "Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either way; retry rather than concluding.",
      "enum": [
        "witnessed_signed",
        "signed_scan",
        "live_observation",
        "honest_absence",
        "withheld_by_owner",
        "knowledge_base",
        "input_error",
        "self_declared",
        "read_failed"
      ]
    },
    "subject": {
      "type": "string",
      "description": "The company, domain or token this answer is about."
    },
    "summary": {
      "type": "string",
      "description": "The same answer as the text content, for display."
    },
    "claim_url": {
      "type": "string",
      "description": "Present when the subject has no published record (unclaimed or private)."
    }
  },
  "required": [
    "status",
    "provenance",
    "subject",
    "summary"
  ],
  "description": "The typed form of every answer a tool completes. A call that fails partway answers isError: true with text only and no structured record."
}
🟢trooth_outside_in_read(domain)

Fetch https://<domain>/ and /.well-known/security.txt once, when called, from Trooth's server and report whether HTTPS answered, which of five response headers (HSTS, CSP, nosniff, frame protection, referrer policy) are present, and whether security.txt is published, absent or unread. IP literals and names resolving to private, loopback or link-local addresses are refused; redirects are reported, not followed; each request stops after 4 seconds. Observations, not witnessed evidence, not a grade.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Domain to read, e.g. example.com"
    }
  },
  "required": [
    "domain"
  ]
}

Esquema de salida

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Machine-branchable outcome for this lookup.",
      "enum": [
        "published",
        "listed",
        "unclaimed",
        "private",
        "observed",
        "valid",
        "invalid",
        "expired",
        "revoked",
        "answered",
        "out_of_scope",
        "bad_input",
        "unavailable"
      ]
    },
    "provenance": {
      "type": "string",
      "description": "Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either way; retry rather than concluding.",
      "enum": [
        "witnessed_signed",
        "signed_scan",
        "live_observation",
        "honest_absence",
        "withheld_by_owner",
        "knowledge_base",
        "input_error",
        "self_declared",
        "read_failed"
      ]
    },
    "subject": {
      "type": "string",
      "description": "The company, domain or token this answer is about."
    },
    "summary": {
      "type": "string",
      "description": "The same answer as the text content, for display."
    },
    "claim_url": {
      "type": "string",
      "description": "Present when the subject has no published record (unclaimed or private)."
    }
  },
  "required": [
    "status",
    "provenance",
    "subject",
    "summary"
  ],
  "description": "The typed form of every answer a tool completes. A call that fails partway answers isError: true with text only and no structured record."
}
🟢trooth_ask(question)

Answer a question about Trooth itself (what the Trooth Network is, what one company record carries, pricing, how witnessing works) from Trooth's fixed, curated knowledge base. Makes no outside request. A question the knowledge base does not cover returns out_of_scope; for a company's record use trooth_public_trust_profile.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "question": {
      "type": "string",
      "description": "A question about Trooth"
    }
  },
  "required": [
    "question"
  ]
}

Esquema de salida

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Machine-branchable outcome for this lookup.",
      "enum": [
        "published",
        "listed",
        "unclaimed",
        "private",
        "observed",
        "valid",
        "invalid",
        "expired",
        "revoked",
        "answered",
        "out_of_scope",
        "bad_input",
        "unavailable"
      ]
    },
    "provenance": {
      "type": "string",
      "description": "Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either way; retry rather than concluding.",
      "enum": [
        "witnessed_signed",
        "signed_scan",
        "live_observation",
        "honest_absence",
        "withheld_by_owner",
        "knowledge_base",
        "input_error",
        "self_declared",
        "read_failed"
      ]
    },
    "subject": {
      "type": "string",
      "description": "The company, domain or token this answer is about."
    },
    "summary": {
      "type": "string",
      "description": "The same answer as the text content, for display."
    },
    "claim_url": {
      "type": "string",
      "description": "Present when the subject has no published record (unclaimed or private)."
    }
  },
  "required": [
    "status",
    "provenance",
    "subject",
    "summary"
  ],
  "description": "The typed form of every answer a tool completes. A call that fails partway answers isError: true with text only and no structured record."
}
🟢trooth_verify(token)

Check the two signatures on a Trust Ledger Token (tlt2. or tlt. form, or its JTI) against Trooth's own token ledger. Returns valid, invalid (a signature does not check out), expired or revoked, or unclaimed when no token matches. Trooth's signature covers the signing event and the payload at issuance, not the truth of the claims the token carries.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "token": {
      "type": "string",
      "description": "A Trust Ledger Token (tlt2. or tlt. form) or its JTI"
    }
  },
  "required": [
    "token"
  ]
}

Esquema de salida

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "description": "Machine-branchable outcome for this lookup.",
      "enum": [
        "published",
        "listed",
        "unclaimed",
        "private",
        "observed",
        "valid",
        "invalid",
        "expired",
        "revoked",
        "answered",
        "out_of_scope",
        "bad_input",
        "unavailable"
      ]
    },
    "provenance": {
      "type": "string",
      "description": "Where this answer came from. An honest_absence is missing data, never a judgment about the subject. A read_failed means Trooth could not read its own record at this moment and asserts nothing either way; retry rather than concluding.",
      "enum": [
        "witnessed_signed",
        "signed_scan",
        "live_observation",
        "honest_absence",
        "withheld_by_owner",
        "knowledge_base",
        "input_error",
        "self_declared",
        "read_failed"
      ]
    },
    "subject": {
      "type": "string",
      "description": "The company, domain or token this answer is about."
    },
    "summary": {
      "type": "string",
      "description": "The same answer as the text content, for display."
    },
    "claim_url": {
      "type": "string",
      "description": "Present when the subject has no published record (unclaimed or private)."
    }
  },
  "required": [
    "status",
    "provenance",
    "subject",
    "summary"
  ],
  "description": "The typed form of every answer a tool completes. A call that fails partway answers isError: true with text only and no structured record."
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada4 herramientas