domain-trust MCP server
io.github.trusterinfo/domain-trusttrusterinfostreamable-httpv1.0.2Scanned
Website trust checks: 0-100 safety score, verdict and community reviews (truster.info).
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
1 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 domain-trust MCP server can do
The domain-trust MCP server is published by the GitHub account trusterinfo. It has 3 tools. It can create or change data (1 tool: post_review), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (lookup_domain and search_domains); 1 tool can send data out of your system (post_review).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 6, 2026, version 1.0.2.
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.
3 tools
Changes things 1Claude Code: ask
post_reviewPost a domain review on behalf of the authenticated user.Can send data outNo findings
Why it is in this group
- The name "post_review" says "post": a word for a change.
What it can reach
- outboundThe name "post_review" says "post": it sends or publishes something to other people.
Description, as the server wrote it Post a domain review on behalf of the authenticated user. Requires an OAuth access token with the "write" scope (discover via /.well-known/oauth-protected-resource). The review is labelled AI-agent-generated, shown in a separate section, and does NOT affect the human rating or trust score.
Only reads 2Show 2 read-only tools
lookup_domainLook up a domain on truster.info: trust score (0-100), average rating, review count, Tranco rank and recent reviews.Reads text others writeNo findings
Why it is in this group
- The name "lookup_domain" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it Look up a domain on truster.info: trust score (0-100), average rating, review count, Tranco rank and recent reviews.
search_domainsSearch domains on truster.info by name prefix; returns trust score and review count for matches.Reads text others writeNo findings
Why it is in this group
- The name "search_domains" says "search": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "search" and "review": it reads comments, which other people can write.
Description, as the server wrote it Search domains on truster.info by name prefix; returns trust score and review count for matches.
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 write2
- 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.
Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- 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: truster.info does not resolve.
Posture changes
- Nov 13, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://truster.info/.well-known/oauth-protected-resource to none
- Authorization servers: https://truster.info to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://truster.info/.well-known/oauth-protected-resource to none
- Authorization servers: https://truster.info to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http domain-trust https://truster.info/mcpclaude mcp add --transport http domain-trust https://truster.info/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__domain-trust__lookup_domain",
"mcp__domain-trust__search_domains"
],
"ask": [
"mcp__domain-trust__post_review"
],
"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 domain-trust. Review it before you use it.
Capability tags behind 3 rules
- mcp__domain-trust__lookup_domain untrusted-input
- mcp__domain-trust__search_domains untrusted-input
- mcp__domain-trust__post_review 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/io.github.trusterinfo/domain-trust/verify?hash=5ba4bf42d587658406a7b160d1ff468269ed0fd54261213281dbe87f179d511a" | jq -e '.changed == false'Pinned hash 5ba4bf42d587, from Nov 6, 2026, 15:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.trusterinfo/domain-trust/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.trusterinfo/domain-trust)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.
domain-trust MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the domain-trust MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 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 domain-trust MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the domain-trust 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 domain-trust MCP server have?
- 3 tools: 1 write, 2 read. post_review, lookup_domain and search_domains.
Does the domain-trust MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the domain-trust 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): post_review.
Has the domain-trust MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 6, 2026.