HVTracker MCP

Check Agent Trust

check_agent_trust

Read-onlyIdempotent

Get the HVTracker supply-chain trust profile for a tracked AI agent or framework.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name_or_repo`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`rank`	No
`repo`	No
`query`	Yes
`message`	No
`tracked`	Yes
`category`	No
`advisories`	No
`submit_url`	No
`profile_url`	No
`trust_score`	No
`capabilities`	No
`coverage_grade`	No
`credential_url`	No
`evidence_grade`	No
`has_provenance`	No
`scorecard_score`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 28, 2026

addedOutput schema / $defs / AdvisorySummary

Added value: +{
+  "properties": {
+    "advisories": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Advisories",
+      "type": "array"
+    },
+    "checked": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Checked",
+      "type": "array"
+    },
+    "count": {
+      "title": "Count",
+      "type": "integer"
+    },
+    "scored": {
+      "title": "Scored",
+      "type": "boolean"
+    },
+    "worst": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Worst"
+    }
+  },
+  "required": [
+    "checked",
+    "count",
+    "worst",
+    "advisories",
+    "scored"
+  ],
+  "title": "AdvisorySummary",
+  "type": "object"
+}

addedOutput schema / properties / advisories

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/AdvisorySummary"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

removedOutput schema / properties / capabilities / default
```
Removed value: -null
```
removedOutput schema / properties / category / default
```
Removed value: -null
```
removedOutput schema / properties / coverage_grade / default
```
Removed value: -null
```
removedOutput schema / properties / credential_url / default
```
Removed value: -null
```
removedOutput schema / properties / evidence_grade / default
```
Removed value: -null
```
removedOutput schema / properties / has_provenance / default
```
Removed value: -null
```
removedOutput schema / properties / message / default
```
Removed value: -null
```
removedOutput schema / properties / name / default
```
Removed value: -null
```
removedOutput schema / properties / profile_url / default
```
Removed value: -null
```
removedOutput schema / properties / rank / default
```
Removed value: -null
```
removedOutput schema / properties / repo / default
```
Removed value: -null
```
removedOutput schema / properties / scorecard_score / default
```
Removed value: -null
```
removedOutput schema / properties / submit_url / default
```
Removed value: -null
```
removedOutput schema / properties / trust_score / default
```
Removed value: -null
```

Changed4 schema fields changedJul 8, 2026

addedOutput schema / $defs

Added value: +{
+  "Capabilities": {
+    "properties": {
+      "drift_status": {
+        "title": "Drift Status",
+        "type": "string"
+      },
+      "mcp_status": {
+        "title": "Mcp Status",
+        "type": "string"
+      },
+      "plugin_system": {
+        "title": "Plugin System",
+        "type": "string"
+      },
+      "provider_count": {
+        "title": "Provider Count",
+        "type": "integer"
+      },
+      "requires_api_keys": {
+        "title": "Requires Api Keys",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "mcp_status",
+      "provider_count",
+      "requires_api_keys",
+      "plugin_system",
+      "drift_status"
+    ],
+    "title": "Capabilities",
+    "type": "object"
+  }
+}

addedOutput schema / properties / capabilities

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Capabilities"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / coverage_grade

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Coverage Grade"
+}

addedOutput schema / properties / credential_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Credential Url"
+}

Changed1 schema field changedJun 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Category"
+    },
+    "evidence_grade": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Evidence Grade"
+    },
+    "has_provenance": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Has Provenance"
+    },
+    "message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Message"
+    },
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Name"
+    },
+    "profile_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Profile Url"
+    },
+    "query": {
+      "title": "Query",
+      "type": "string"
+    },
+    "rank": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Rank"
+    },
+    "repo": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Repo"
+    },
+    "scorecard_score": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Scorecard Score"
+    },
+    "submit_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Submit Url"
+    },
+    "tracked": {
+      "title": "Tracked",
+      "type": "boolean"
+    },
+    "trust_score": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Trust Score"
+    }
+  },
+  "required": [
+    "query",
+    "tracked"
+  ],
+  "title": "CheckAgentTrustResult",
+  "type": "object"
+}

First observedJun 21, 2026

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety and side-effect profile is fully covered by structured data. The description adds only the domain framing ('supply-chain trust profile'), which is useful but modest; it says nothing about lookup failures for untracked agents or result freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the core resource and scope come first and every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return-value explanation is rightly omitted, and annotations cover the behavioral profile. What remains missing for a lookup tool is the disambiguation from sibling lookup tools and any note about untracked or unknown agents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden, and it partially does so by indicating the parameter identifies a tracked AI agent or framework. However, the parameter is named name_or_repo while the description never mentions repository form, leaving the accepted syntax and any name-vs-repo ambiguity unresolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and a specific resource ('HVTracker supply-chain trust profile') for a specific input type (tracked AI agent or framework). An agent can distinguish it from write-oriented siblings like scan_stack or verify_mcp_server, but nothing separates it from get_agent_history or search_agents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the seven siblings, no mention of prerequisites, and no indication of what 'tracked' means or how an agent becomes tracked. The usage context is only implied by the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HVTracker MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.