io.github.trusterinfo/domain-trust
REMOTE · TRUSTER.INFO · 2 COMPONENTS · SCANNED SEP 27
Website trust checks: 0-100 safety score, verdict and community reviews (truster.info).
Available components
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.trusterinfo/domain-trust MCP server?
io.github.trusterinfo/domain-trust is a hosted endpoint at https://truster.info/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · truster.info
claude mcp add --transport http trusterinfo-domain-trust 'https://truster.info/mcp'
{
"mcpServers": {
"trusterinfo-domain-trust": {
"url": "https://truster.info/mcp"
}
}
} {
"servers": {
"trusterinfo-domain-trust": {
"type": "http",
"url": "https://truster.info/mcp"
}
}
} [mcp_servers.trusterinfo-domain-trust] url = "https://truster.info/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trusterinfo-domain-trust": {
"type": "remote",
"url": "https://truster.info/mcp",
"enabled": true
}
}
} openclaw mcp add trusterinfo-domain-trust --url 'https://truster.info/mcp' --transport streamable-http
mcp_servers:
trusterinfo-domain-trust:
url: "https://truster.info/mcp" {
"McpServers": {
"trusterinfo-domain-trust": {
"Transport": "http",
"Url": "https://truster.info/mcp"
}
}
} assistant mcp add trusterinfo-domain-trust -t streamable-http -u 'https://truster.info/mcp'
{
"mcpServers": {
"trusterinfo-domain-trust": {
"type": "http",
"url": "https://truster.info/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 −6
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Sept 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 22 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 15 Sept 26 +55
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 12 Sept 26 +55
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://truster.info/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=truster.info | CN=YE1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 53cfe1aebba6ddb0d509d13ff7005dc1961 |
| SANs: *.truster.info, truster.info | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of truster.info. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| info. | present | 5104 | 8 | Verified |
| truster.info. | present | 2371 | 13 | Verified |
| truster.info. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://truster.info/mcp | Unreachable | ||
| http (plaintext) | http://truster.info/mcp | HTTPS enforced | 301 | https://truster.info/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lookup_domain ~52
Look up a domain on truster.info: trust score (0-100), average rating, review count, Tranco rank and recent reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. amazon.com |
No output schema declared.
No examples provided.
post_review ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. amazon.com |
| rating | integer | yes | Star rating 1-5 |
| text | string | yes | Review text (min 3 chars) |
No output schema declared.
No examples provided.
search_domains ~38
Search domains on truster.info by name prefix; returns trust score and review count for matches.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Domain name or prefix |
No output schema declared.
No examples provided.
What is the io.github.trusterinfo/domain-trust MCP server?
io.github.trusterinfo/domain-trust is an MCP server listed in the public MCP registry as io.github.trusterinfo/domain-trust. Website trust checks: 0-100 safety score, verdict and community reviews (truster.info). This page covers its hosted endpoint (https://truster.info/mcp).
Is the io.github.trusterinfo/domain-trust MCP server safe to use?
io.github.trusterinfo/domain-trust scores 10 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.trusterinfo/domain-trust MCP server expose?
io.github.trusterinfo/domain-trust exposes 3 tools: lookup_domain, search_domains, post_review. Their descriptions and schemas cost roughly 198 tokens of context every time the server is loaded.
Does the io.github.trusterinfo/domain-trust MCP server require authentication?
Its publisher declares no required credentials for io.github.trusterinfo/domain-trust. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.trusterinfo/domain-trust MCP server still maintained?
io.github.trusterinfo/domain-trust is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.