HVTracker MCP

Verify MCP Server

verify_mcp_server

Read-onlyIdempotent

Pre-connect trust verdict for an MCP server, package, GitHub repo, or agent name before connecting an AI agent to it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`server`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No
`grade`	Yes
`server`	Yes
`reasons`	Yes
`tracked`	Yes
`trusted`	Yes
`resolved`	Yes
`advisories`	No
`confidence`	Yes
`submit_url`	No
`trust_score`	Yes
`tool_permissions`	Yes
`mcp_server_support`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

addedOutput schema / $defs

Added value: +{
+  "AdvisorySummary": {
+    "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 / slug / default
```
Removed value: -null
```
removedOutput schema / properties / submit_url / default
```
Removed value: -null
```

Changed1 schema field changedJun 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "confidence": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Confidence"
+    },
+    "grade": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Grade"
+    },
+    "mcp_server_support": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Mcp Server Support"
+    },
+    "reasons": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Reasons",
+      "type": "array"
+    },
+    "resolved": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Resolved"
+    },
+    "server": {
+      "title": "Server",
+      "type": "string"
+    },
+    "slug": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Slug"
+    },
+    "submit_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Submit Url"
+    },
+    "tool_permissions": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Tool Permissions",
+      "type": "array"
+    },
+    "tracked": {
+      "title": "Tracked",
+      "type": "boolean"
+    },
+    "trust_score": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "title": "Trust Score"
+    },
+    "trusted": {
+      "title": "Trusted",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "server",
+    "resolved",
+    "tracked",
+    "trusted",
+    "grade",
+    "trust_score",
+    "confidence",
+    "reasons",
+    "mcp_server_support",
+    "tool_permissions"
+  ],
+  "title": "VerifyMcpServerResult",
+  "type": "object"
+}

First observedJun 21, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior. The description adds the pre-connect verification context but does not disclose what the trust verdict includes, any rate limits, or authentication requirements beyond what annotations provide.

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 redundant phrasing. It packs purpose, input domain, and timing into one compact statement.

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?

An output schema exists, so return details need not be in the description, and annotations cover safety. However, the description does not resolve overlap with check_agent_trust or explain accepted input formats, leaving gaps for a verification tool with one required parameter.

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% and the single 'server' parameter has no schema description. The description partially compensates by saying the tool accepts an MCP server, package, GitHub repo, or agent name, but it gives no format examples or disambiguation for those input types.

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 clear purpose: produce a pre-connect trust verdict for an MCP server, package, GitHub repo, or agent name. It identifies the resource domain well but does not differentiate from sibling check_agent_trust, especially since 'agent name' is in scope here.

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

Usage Guidelines3/5

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

Provides implied timing ('before connecting an AI agent to it'), which signals when to use it. However, it does not name alternatives or exclusions, so an agent must infer whether check_agent_trust or scan_stack is preferable in overlapping cases.

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.