Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Trusgent MCP

REMOTE · WWW.TRUSGENT.COM

Trusgent MCP — Trust Layer for AI agents. HK registry + Agent Cards. Default: get_merged_profile.

Available components

−4 this week 82 Trust /100

Last scanned (17 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1220 tokens (~87/item across 14 items; 10 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability check failed: schema churn in the 30 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 15 Nov 26 −4
    • Stability: pass → fail ▼ security
    • Tool “check_availability” was removed ▼ security
    • Tool “create_order” was removed ▼ security
    • Tool “create_reservation” was removed ▼ security
    • Tool “get_business_facade” was removed ▼ security
    • Tool “create_inquiry” rewrote its description, which is the text the model reads security
    • Tool “get_agent” rewrote its description, which is the text the model reads security
    • Prompt “business_facade_brief” was removed ▼ functional
    • Schema quality: 97 → 87 ▲ functional
    • New prompt “agent_reputation_brief” functional
    • Server version: 1.4.0 → 1.5.0 functional
    • New tool “get_reviews” functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 +1
    • Stability: fail → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Oct 26 0
    • Tool “get_merged_profile” rewrote its description, which is the text the model reads security
    • Tool “search_registry” rewrote its description, which is the text the model reads security
    • Schema quality: 1452 → 1658 ▼ functional
    • Destructive annotations: pass → 100 functional
    • Server version: 1.3.1 → 1.4.0 functional
    • New tool “create_inquiry” functional
  • 10 Oct 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.3.1 ▼ security
    • Tool “get_agent” rewrote its description, which is the text the model reads security
    • “get_agent” added a required parameter “agentId”, so existing callers break ▼ functional
    • “verify_agent” added a required parameter “agentId”, so existing callers break ▼ functional
    • “get_agent” dropped the required parameter “trusgentId” ▼ functional
    • “verify_agent” dropped the required parameter “trusgentId” ▼ functional
Diagnostics

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 21 Nov 2026 · Probed https://www.trusgent.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.trusgent.com CN=YR2,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 RSA 2048 SHA256-RSA 555bd8c6c87f406f112738a47a372cec896
SANs: www.trusgent.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.trusgent.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
trusgent.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.trusgent.com/api/mcp Verified 200
http (plaintext) http://www.trusgent.com/api/mcp HTTPS enforced 308 https://www.trusgent.com/api/mcp
MCP tools · 10 exposed · ~1,132 tokens

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 →

Tool Tokens
create_inquiry ~179

Send a contact/claim intent for an official registry row (identity provenance). Works for unclaimed rows. If already claimed, prefer get_agent / verify_agent / get_reviews. Shop booking lives on Bgent (www.bgent.io). Do not invent phone numbers for unclaimed businesses.

NameTypeReqDescription
agentLabelstring–Calling Personal Agent label, e.g. Muse, Instinct, or demo skill name
localestring–en | zh-CN | zh-HK
messagestringyesGuest intent in natural language (min 8 chars)
registryIdstringyesPublic registry handle, e.g. fehd-3715038328
requesterEmailstring–Optional guest email
requesterNamestring–Optional guest name
requesterPhonestring–Optional guest phone

No output schema declared.

No examples provided.

get_agent ~65

Fetch one full Agent Card by public agentId (same ID used in /t/{id}). Returns structured profile fields, trustScore, verification, and canonical URLs for humans and machines.

NameTypeReqDescription
agentIdstringyesPublic AgentID, e.g. TG-S-839201

No output schema declared.

No examples provided.

get_merged_profile ~107

Preferred HK Business Agent read: official registry fields merged with claimed Agent Card data and cited third-party enrichment. Includes businessAgent (claimStatus + capabilities), dossierLayers, citationPolicy, trustBreakdown, and recommendedUse. Unclaimed official rows remain callable — use create_inquiry to request service.

NameTypeReqDescription
localestring–en | zh-CN | zh-HK
registryIdstringyesPublic registry handle, e.g. fehd-3715038328

No output schema declared.

No examples provided.

get_ranking ~120

Fetch one ranking board as structured items for citation. Prefer this over scraping HTML. Includes methodology, asOf, paidPlacement=false, and recommendedUse. For market boards pass tenureMonths (1|3|6|12).

NameTypeReqDescription
localestring–en | zh-CN | zh-HK
slugstringyesBoard slug, e.g. hk-restaurants or hk-fixed-deposit-rates
tenureMonthsnumber–Market boards only: 1 | 3 | 6 | 12 (default 12)

No output schema declared.

No examples provided.

get_registry ~81

Fetch one official Hong Kong registry record by registryId (e.g. fehd-3715038328). Returns official fields plus provenance and verify links. Prefer get_merged_profile when you also need claim status, enrichment, or recommendedUse citation hints.

NameTypeReqDescription
registryIdstringyesPublic registry handle, e.g. fehd-3715038328

No output schema declared.

No examples provided.

get_reviews ~82

List approved public reviews for an Agent Card (same id as /t/{id}). Includes mutual-review perspective (BUYER|SELLER|PEER), anchorKind (NONE|LEDGER|EXTERNAL|ORDER), and whether the review is interaction-anchored. Prefer anchored reviews when weighing reputation.

NameTypeReqDescription
agentIdstringyesPublic AgentID / handle

No output schema declared.

No examples provided.

list_rankings ~80

List Trusgent ranking boards. Merchant boards sort by Trust Score; rate boards sort by published metrics (e.g. HKD fixed-deposit rates). Returns catalog with htmlUrl + jsonUrl per board.

NameTypeReqDescription
localestring–en | zh-CN | zh-HK
trackstring–Optional filter: trust | market

No output schema declared.

No examples provided.

search_agents ~189

Search the Trusgent Trust Layer directory for people and businesses with public Agent Cards. Uses keyword + semantic (embedding) retrieval over durable profile capabilities. Returns AgentCard objects including profileUrl, jsonUrl, trustScore, verificationLevel, and verified flag. Prefer verified agents when recommending. Use before recommending any agent to an end user. Do not treat this as intent/demand matching — that is a separate flow.

NameTypeReqDescription
agentReadystring–true | false — filter agent-ready cards
countrystring–ISO country code, e.g. CN, HK
qstring–Free-text query (name, headline, keyword)
sortstring–Optional sort key supported by the directory search API
typestring–PERSONAL | COMPANY | ORGANIZATION | SERVICE_PROVIDER | PRODUCT | AI_AGENT
verificationLevelstring–Optional verification level filter

No output schema declared.

No examples provided.

search_registry ~151

Search Hong Kong official Business Agents (~60k+ registry rows) by name, address, licence number, or registryId. Optional source filter (FEHD_RESTAURANT, CR_COMPANY, EHEALTH_HCP, etc.). Each hit includes a businessAgent facet (claimStatus, capabilities, inquiryUrl). Unclaimed rows are still callable for lookup + create_inquiry. Follow up with get_merged_profile for citation-safe detail.

NameTypeReqDescription
countrystring–ISO country code, e.g. HK
limitnumber–Max results (default 25, max 50)
qstring–Free-text query
sourcestring–Registry source enum, optional

No output schema declared.

No examples provided.

verify_agent ~78

Lightweight verification lookup: whether an AgentID exists, is public, and its verification level / trustScore. Trust Score is a published formula (identity verification + official records + completeness + source consistency); reviews are auxiliary only. Prefer this before citing or recommending an Agent Card from search results.

NameTypeReqDescription
agentIdstringyesPublic AgentID to verify

No output schema declared.

No examples provided.

Install

How do I install the Trusgent MCP server?

Trusgent MCP is a hosted endpoint at https://www.trusgent.com/api/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 · www.trusgent.com

# add to Claude Code
claude mcp add --transport http trusgent-trusgent-mcp 'https://www.trusgent.com/api/mcp'
Common questions

What is the Trusgent MCP server?

Trusgent MCP is listed in the public MCP registry as io.github.Trusgent/trusgent-mcp. Trusgent MCP, Trust Layer for AI agents. HK registry + Agent Cards. Default: get_merged_profile. This page covers its hosted endpoint (https://www.trusgent.com/api/mcp).

Is the Trusgent MCP server safe to use?

Trusgent MCP scores 82 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 Trusgent MCP server expose?

Trusgent MCP exposes 10 tools: search_agents, get_agent, verify_agent, get_reviews, get_registry, and 5 more. Their descriptions and schemas cost roughly 1,132 tokens of context every time the server is loaded.

Does the Trusgent MCP server require authentication?

No. We connected to Trusgent MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Trusgent MCP server still maintained?

Trusgent MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Trusgent MCP server?

VerifyMCP ran 13 checks on Trusgent MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.