Trusgent MCP
REMOTE · WWW.TRUSGENT.COM · SCANNED SEP 21
Trusgent MCP — Trust Layer for AI agents. HK registry + Agent Cards. Default: get_merged_profile.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 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 1458 tokens (~91/item across 16 items; 12 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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
claude mcp add --transport http trusgent-trusgent-mcp 'https://www.trusgent.com/api/mcp'
{
"mcpServers": {
"trusgent-trusgent-mcp": {
"url": "https://www.trusgent.com/api/mcp"
}
}
} {
"servers": {
"trusgent-trusgent-mcp": {
"type": "http",
"url": "https://www.trusgent.com/api/mcp"
}
}
} [mcp_servers.trusgent-trusgent-mcp] url = "https://www.trusgent.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trusgent-trusgent-mcp": {
"type": "remote",
"url": "https://www.trusgent.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add trusgent-trusgent-mcp --url 'https://www.trusgent.com/api/mcp' --transport streamable-http
mcp_servers:
trusgent-trusgent-mcp:
url: "https://www.trusgent.com/api/mcp" {
"McpServers": {
"trusgent-trusgent-mcp": {
"Transport": "http",
"Url": "https://www.trusgent.com/api/mcp"
}
}
} assistant mcp add trusgent-trusgent-mcp -t streamable-http -u 'https://www.trusgent.com/api/mcp'
{
"mcpServers": {
"trusgent-trusgent-mcp": {
"type": "http",
"url": "https://www.trusgent.com/api/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.
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Schema quality: 1258 → 1458 ▼ functional
- New prompt “ranking_lookup” functional
- New tool “get_ranking” functional
- New tool “list_rankings” functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Tool “search_agents” rewrote its description, which is the text the model reads security
- Server version: 1.3.0 → 1.3.1 functional
- “get_business_facade” reworded the description of “handle” cosmetic
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 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 | 30 Jul 2026 | 28 Oct 2026 | RSA 2048 | SHA256-RSA | 6fb248aa82bbed523379b2b5d4f1de2161c |
| 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. | present | 19718 | 13 | Verified |
| trusgent.com. | absent | 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 |
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 →
check_availability ~86
Check remaining reservation capacity for a business facade slot before create_reservation. HTTP equivalent: GET /api/v1/b/{handle}/availability?date=YYYY-MM-DD&time=HH:mm.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Reservation date (YYYY-MM-DD) |
| handle | string | yes | Public facade handle (AgentID) |
| time | string | yes | Reservation time (HH:mm) |
No output schema declared.
No examples provided.
create_order ~172
Submit a dine-in or takeaway order from a published restaurant facade menu. Creates a PENDING order; kitchen confirms in Dashboard. Restaurant facades only; menu item names must match facade.menu. HTTP equivalent: POST /api/v1/b/{handle}/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillmentMode | string | – | Defaults to DINE_IN |
| guestName | string | – | Guest name (required for takeaway/pickup) |
| guestPhone | string | – | Guest phone (required for takeaway/pickup) |
| handle | string | yes | Public facade handle (AgentID) |
| items | array | yes | Menu lines — names must match published facade menu |
| note | string | – | Optional note for the kitchen |
| table | string | yes | Table code from facade.tables, or TAKEAWAY / PICKUP for off-premise |
No output schema declared.
No examples provided.
create_reservation ~185
Submit a booking or appointment request for a published business facade. Creates a PENDING reservation; the merchant confirms in Dashboard. Not a guaranteed instant booking. HTTP equivalent: POST /api/v1/b/{handle}/reservations.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD |
| string | – | Optional guest email | |
| handle | string | yes | Public facade handle (AgentID) |
| mode | string | – | table for dine-in; appointment for generic services |
| name | string | yes | Guest name |
| note | string | – | Optional note for the merchant |
| partySize | integer | yes | Party size (1–40) |
| phone | string | yes | Guest phone (E.164 or local) |
| service | string | – | Optional service label |
| table | string | – | Optional table code from facade.tables |
| time | string | yes | HH:mm |
No output schema declared.
No examples provided.
get_agent ~75
Fetch one full Agent Card by public trusgentId (same ID used in /t/{id} and /b/{id}). Returns structured profile fields, trustScore, verification, and canonical URLs for humans and machines.
| Name | Type | Req | Description |
|---|---|---|---|
| trusgentId | string | yes | Public AgentID, e.g. TG-S-839201 |
No output schema declared.
No examples provided.
get_business_facade ~67
Fetch a published business facade (menu/services, hours, booking capabilities) by the same public ID/handle as /b/{id}. Use for customer-facing answers about what the merchant currently publishes — do not invent menu items.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Agent Handle / facade handle |
No output schema declared.
No examples provided.
get_merged_profile ~110
Preferred HK registry read: official registry fields merged with claimed Agent Card data and cited third-party enrichment (Google Places POC when available). Includes dossierLayers, citationPolicy, trustBreakdown, and recommendedUse so agents know what is safe to cite. Reviews are auxiliary and are not scraped from the open web.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | en | zh-CN | zh-HK |
| registryId | string | yes | Public 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).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | en | zh-CN | zh-HK |
| slug | string | yes | Board slug, e.g. hk-restaurants or hk-fixed-deposit-rates |
| tenureMonths | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| registryId | string | yes | Public registry handle, e.g. fehd-3715038328 |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | en | zh-CN | zh-HK |
| track | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentReady | string | – | true | false — filter agent-ready cards |
| country | string | – | ISO country code, e.g. CN, HK |
| q | string | – | Free-text query (name, headline, keyword) |
| sort | string | – | Optional sort key supported by the directory search API |
| type | string | – | PERSONAL | COMPANY | ORGANIZATION | SERVICE_PROVIDER | PRODUCT | AI_AGENT |
| verificationLevel | string | – | Optional verification level filter |
No output schema declared.
No examples provided.
search_registry ~125
Search Hong Kong official registry records (~60k+) by name, address, licence number, or registryId. Optional source filter (FEHD_RESTAURANT, EHEALTH_HCP, etc.). Returns lightweight rows with profileUrl and mergedUrl; follow up with get_merged_profile for citation-safe detail.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO country code, e.g. HK |
| limit | number | – | Max results (default 25, max 50) |
| q | string | – | Free-text query |
| source | string | – | Registry source enum, optional |
No output schema declared.
No examples provided.
verify_agent ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| trusgentId | string | yes | Public AgentID to verify |
No output schema declared.
No examples provided.
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 86 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 12 tools: search_agents, get_agent, verify_agent, get_business_facade, check_availability, and 7 more. Their descriptions and schemas cost roughly 1,370 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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.