Skip to content

Semanto by Trooth MCP server

co.trooth/semantotrooth.costreamable-httpv1.1.0Scanned

Set up, sign, publish and check Semanto, a company's signed website file for AI agents.

16 tools: 11 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 11 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 1
  • 2 findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

11 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Semanto by Trooth MCP server can do

The Semanto by Trooth MCP server is published by trooth.co, a domain the MCP Registry verified. It has 16 tools. It can create or change data (11 tools: semanto_guide, semanto_setup_read_again, semanto_setup_choose, semanto_setup_confirm and 7 more), but cannot delete data. 5 tools only read.

4 tools bring in text other people can write (semanto_setup_read_again, semanto_review_get, semanto_install_check and 1 more); 1 tool can send data out of your system (semanto_verify).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Last scanned Nov 6, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Changes things 11Claude Code: ask
  • semanto_factsThe company's signed facts as JSON-LD.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The company's signed facts as JSON-LD. No key needed.

    Annotations the server declares

    • title: A company's signed facts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_guideWhat Semanto is and the order an agent runs it in, with which steps need the person.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What Semanto is and the order an agent runs it in, with which steps need the person. Read it once before running setup for someone. No key needed.

    Annotations the server declares

    • title: How to finish setup
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_install_checkCheck my site.Reads text others writeNo findings

    Why it is in this group

    • The name "semanto_install_check" says "install": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check my site. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Check my site
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • semanto_install_guideHow to put it on the site.1 finding

    Why it is in this group

    • The name "semanto_install_guide" says "install": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "semanto_install_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "semanto_install_guide" says "install": a word for a change.

      What this check looks for
    Description, as the server wrote it
    How to put it on the site. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: How to put it on the site
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_pageOne page of a company's signed copy as markdown, by its path on the company's site.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One page of a company's signed copy as markdown, by its path on the company's site. No key needed.

    Annotations the server declares

    • title: Read one signed page
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_pages_changedPages changed since the read.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Pages changed since the read. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Pages changed since the read
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_setup_chooseChoose Basic or the full signed copy.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Choose Basic or the full signed copy. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Choose Basic or the full signed copy
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_setup_confirmConfirm the reviewed version.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Confirm the reviewed version. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Confirm the reviewed version
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_setup_read_againRead the website again.Reads text others write1 finding

    Why it is in this group

    • The name "semanto_setup_read_again" says "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "website": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "semanto_setup_read_again" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "semanto_setup_read_again" says "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Read the website again. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Read the website again
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • semanto_signSign and publish.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Sign and publish. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Sign and publish
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • semanto_verifyChecks a page against the current signed version.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Checks a page against the current signed version. With no hash, Trooth fetches the page as an agent does (Accept: text/markdown) and hashes what it is served, which is what semanto_install_check checks too; compared says which. status: matches, differs (hash is what was found, signed_hash what was signed), not_served (the page did not answer with markdown), unknown_url or not_signed. No key needed.

    Annotations the server declares

    • title: Check a signed URL
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • semanto_receipts_listWho read the signed copy.No findings

    Why it is in this group

    • The name "semanto_receipts_list" says "list": a word for reading.
    Description, as the server wrote it
    Who read the signed copy. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Who read the signed copy
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_review_getThe facts to review.Reads text others writeNo findings

    Why it is in this group

    • The name "semanto_review_get" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "semanto_review_get" says "get" and "review": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    The facts to review. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: The facts to review
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_statusSetup status and next step.No findings

    Why it is in this group

    • The name "semanto_status" says "status": a word for reading.
    Description, as the server wrote it
    Setup status and next step. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Setup status and next step
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_versions_listEvery version the company published, newest first, with its state (signed, withdrawn, superseded).No findings

    Why it is in this group

    • The name "semanto_versions_list" says "list": a word for reading.
    Description, as the server wrote it
    Every version the company published, newest first, with its state (signed, withdrawn, superseded). No key needed.

    Annotations the server declares

    • title: List published versions
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • semanto_whoamiWho this key acts for.No findings

    Why it is in this group

    • The name "semanto_whoami" says "whoami": a word for reading.
    Description, as the server wrote it
    Who this key acts for. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

    Annotations the server declares

    • title: Who this key acts for
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
404
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 404.

Posture changes

  1. Nov 16, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 11 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://api.trooth.co/.well-known/oauth-protected-resource/os/semanto/mcp to none
    • Authorization servers: https://special-chimney-41.authkit.app to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  2. Nov 9, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 11
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://api.trooth.co/.well-known/oauth-protected-resource/os/semanto/mcp to none

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "semanto_setup_read_again" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "semanto_setup_read_again" says "read": a word for reading.

    What this check looks for
  • The server marks "semanto_install_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "semanto_install_guide" says "install": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 11 -> 0 (and 5 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 11 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://api.trooth.co/.well-known/oauth-protected-resource/os/semanto/mcp to none
    • Authorization servers: https://special-chimney-41.authkit.app to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 11 (and 3 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 11
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://api.trooth.co/.well-known/oauth-protected-resource/os/semanto/mcp to none

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http semanto https://api.trooth.co/os/semanto/mcp
claude mcp add --transport http semanto https://api.trooth.co/os/semanto/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__semanto__semanto_whoami",
      "mcp__semanto__semanto_status",
      "mcp__semanto__semanto_review_get",
      "mcp__semanto__semanto_versions_list",
      "mcp__semanto__semanto_receipts_list"
    ],
    "ask": [
      "mcp__semanto__semanto_guide",
      "mcp__semanto__semanto_setup_read_again",
      "mcp__semanto__semanto_setup_choose",
      "mcp__semanto__semanto_setup_confirm",
      "mcp__semanto__semanto_sign",
      "mcp__semanto__semanto_pages_changed",
      "mcp__semanto__semanto_install_guide",
      "mcp__semanto__semanto_install_check",
      "mcp__semanto__semanto_page",
      "mcp__semanto__semanto_facts",
      "mcp__semanto__semanto_verify"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as semanto. Review it before you use it.

Capability tags behind 4 rules
  • mcp__semanto__semanto_setup_read_again untrusted-input
  • mcp__semanto__semanto_review_get untrusted-input
  • mcp__semanto__semanto_install_check untrusted-input
  • mcp__semanto__semanto_verify untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/co.trooth/semanto/verify?hash=296fe8d15ab6f742334200d4e21c609c2e2234f9b6c87f7e36c59d85f0d478b0" | jq -e '.changed == false'

Pinned hash 296fe8d15ab6, from Nov 6, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/co.trooth/semanto/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for co.trooth/semanto
[![Anlyon Radar](https://radar.anlyon.com/badge/co.trooth/semanto.svg)](https://radar.anlyon.com/servers/co.trooth/semanto)

Source: MCP Registry · repository. Synced Nov 15, 2026, 19:17 UTC.

Semanto by Trooth MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Semanto by Trooth MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 11 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Semanto by Trooth MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Semanto by Trooth MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Semanto by Trooth MCP server have?

16 tools: 11 write, 5 read. semanto_guide, semanto_setup_read_again, semanto_setup_choose, semanto_setup_confirm, semanto_sign, semanto_pages_changed, semanto_install_guide, semanto_install_check and 8 more.

Does the Semanto by Trooth MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Semanto by Trooth MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): semanto_verify.

Has the Semanto by Trooth MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 6, 2026.