AgentTrust — AI Agent Trust, Reliability & Reputation Checks
REMOTE · GETAGENTTRUST.COM · SCANNED SEP 28
Trust infrastructure for AI agents: check reliability, verification, and trustDecision by URL.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 751 tokens (~150/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_heartbeat" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the AgentTrust — AI Agent Trust, Reliability & Reputation Checks MCP server?
AgentTrust — AI Agent Trust, Reliability & Reputation Checks is a hosted endpoint at https://getagenttrust.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 · getagenttrust.com
claude mcp add --transport http agenttrust-ai-agenttrust 'https://getagenttrust.com/api/mcp'
{
"mcpServers": {
"agenttrust-ai-agenttrust": {
"url": "https://getagenttrust.com/api/mcp"
}
}
} {
"servers": {
"agenttrust-ai-agenttrust": {
"type": "http",
"url": "https://getagenttrust.com/api/mcp"
}
}
} [mcp_servers.agenttrust-ai-agenttrust] url = "https://getagenttrust.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agenttrust-ai-agenttrust": {
"type": "remote",
"url": "https://getagenttrust.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add agenttrust-ai-agenttrust --url 'https://getagenttrust.com/api/mcp' --transport streamable-http
mcp_servers:
agenttrust-ai-agenttrust:
url: "https://getagenttrust.com/api/mcp" {
"McpServers": {
"agenttrust-ai-agenttrust": {
"Transport": "http",
"Url": "https://getagenttrust.com/api/mcp"
}
}
} assistant mcp add agenttrust-ai-agenttrust -t streamable-http -u 'https://getagenttrust.com/api/mcp'
{
"mcpServers": {
"agenttrust-ai-agenttrust": {
"type": "http",
"url": "https://getagenttrust.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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Tool “check_agent_trust” rewrote its description, which is the text the model reads security
- 22 Sept 26 +1
- Tool coverage: 86% → 100% ▲ functional
- “check_agent_trust” reworded the description of “endpointUrl” cosmetic
- 21 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.2 functional
- 20 Sept 26 65
First indexed and scored.
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 28 Sept 2026 · Probed https://getagenttrust.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=getagenttrust.com | CN=YR1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 6e5090e0b89c246a6818460bf0c64c8473d |
| SANs: getagenttrust.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 getagenttrust.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getagenttrust.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 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' blob: data:; font-src 'self' data:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://getagenttrust.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://getagenttrust.com/api/mcp | HTTPS enforced | 308 | https://getagenttrust.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_agent_trust Check Agent Trust ~163
The preferred pre-invocation trust check for an unknown external agent. Read-only, requires no AgentTrust API key or account. Looks up an agent by its exact invocation URL among AgentTrust's already-observed public agents and returns its status, endpoint-ownership verification, agent reliability score (when available), and a machine-readable trustDecision (recommended, confidence, reasons). Does NOT contact endpointUrl itself during this check — it only reads AgentTrust's own existing monitoring history. An unregistered URL returns { matched: false }, never an error.
| Name | Type | Req | Description |
|---|---|---|---|
| endpointUrl | string | yes | The exact invocation URL of the agent you're about to call. Used only to look up AgentTrust's own already-observed data for it — this endpoint is never contacted during the check. |
| Name | Type | Req | Description |
|---|---|---|---|
| matched | boolean | yes | – |
| name | string | – | – |
| reliabilityScore | number|null | – | – |
| reliabilityScoreStatus | string | – | – |
| slug | string | – | – |
| status | string | – | – |
| trustDecision | object | – | – |
| verified | boolean | – | – |
No examples provided.
get_agent Get Agent ~71
Get one AgentTrust agent's public profile by slug, including its structured Agent Card, current reliability score, and a machine-readable trustDecision (recommended, confidence, reasons) for deciding whether to invoke it.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The agent's URL slug (from its public profile or a list_agents result). |
| Name | Type | Req | Description |
|---|---|---|---|
| agentCard | object | yes | – |
| capabilities | array | yes | – |
| createdAt | string | yes | – |
| description | string|null | yes | – |
| httpStatus | number|null | yes | – |
| id | string | yes | – |
| lastCheckedAt | string|null | yes | – |
| latencyMs | number|null | yes | – |
| name | string | yes | – |
| ownershipVerifiedAt | string|null | yes | – |
| reliabilityScore | number|null | yes | – |
| reliabilityScoreComputedAt | string|null | yes | – |
| reliabilityScoreStatus | string | yes | – |
| slug | string | yes | – |
| status | string | yes | – |
| trustDecision | object | yes | – |
| verified | boolean | yes | – |
| version | string|null | yes | – |
No examples provided.
get_agent_health Get Agent Health ~59
Get one agent's current effective health status and monitoring detail — derived from heartbeat freshness for push-mode agents, or the latest pull check otherwise.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The agent's URL slug (from its public profile or a list_agents result). |
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| checkStatus | string|null | yes | – |
| httpStatus | number|null | yes | – |
| lastCheckedAt | string|null | yes | – |
| latencyMs | number|null | yes | – |
| reliabilityScore | number|null | yes | – |
| reliabilityScoreComputedAt | string|null | yes | – |
| reliabilityScoreStatus | string | yes | – |
| slug | string | yes | – |
| status | string | yes | – |
No examples provided.
list_agents List Agents ~253
Discover AgentTrust agents. Pass `endpointUrl` to check the trust status of a specific external agent by its exact invocation URL before deciding whether to invoke it — the response includes a reliability score, endpoint-ownership verification status, and a machine-readable trustDecision (recommended, confidence, reasons). Without `endpointUrl`, returns the plain paginated listing of public agents, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous call's nextCursor. |
| endpointUrl | string | – | Look up the agent registered with exactly this invocation URL, instead of browsing the full listing — the entry point for a trust check on an agent you only have a URL for. Matches ignore trailing-sl… |
| limit | integer | – | Max agents to return (1-100, default 20). |
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | – |
| pagination | object | yes | – |
No examples provided.
send_heartbeat Send Heartbeat ~63
Record a push-style heartbeat for an agent you own, marking it alive right now. The server sets the timestamp; no client-supplied time is accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The agent's URL slug (from its public profile or a list_agents result). |
| Name | Type | Req | Description |
|---|---|---|---|
| lastHeartbeatAt | string|null | yes | – |
| slug | string | yes | – |
| status | string | yes | – |
No examples provided.
What is the AgentTrust — AI Agent Trust, Reliability & Reputation Checks MCP server?
AgentTrust — AI Agent Trust, Reliability & Reputation Checks is an MCP server listed in the public MCP registry as io.github.agenttrust-ai/agenttrust. Trust infrastructure for AI agents: check reliability, verification, and trustDecision by URL. This page covers its hosted endpoint (https://getagenttrust.com/api/mcp).
Is the AgentTrust — AI Agent Trust, Reliability & Reputation Checks MCP server safe to use?
AgentTrust — AI Agent Trust, Reliability & Reputation Checks scores 70 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 AgentTrust — AI Agent Trust, Reliability & Reputation Checks MCP server expose?
AgentTrust — AI Agent Trust, Reliability & Reputation Checks exposes 5 tools: list_agents, get_agent, get_agent_health, send_heartbeat, check_agent_trust. Their descriptions and schemas cost roughly 609 tokens of context every time the server is loaded.
Does the AgentTrust — AI Agent Trust, Reliability & Reputation Checks MCP server require authentication?
No. We connected to AgentTrust — AI Agent Trust, Reliability & Reputation Checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentTrust — AI Agent Trust, Reliability & Reputation Checks MCP server still maintained?
AgentTrust — AI Agent Trust, Reliability & Reputation Checks is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.