ToolTrust
B15/100
Smithery

hubertroy-test

mcpsmithery

@Smithery

Provide the product’s purpose, primary users, and the top three tasks it enables to receive a concise name and summary. List any key integrations, data sources, and unique value. Share tone or branding preferences (e.g., playful, professional) to shape the wording.

By Smithery | 3 findings | Scanned 4/10/2026 | tooltrust-scanner/v0.3.8

1 High2 Info

Risk Summary

Safe With Normal Controls

Dep Visibility is the main signal, but overall risk remains within an acceptable range.

Potential impact: This finding indicates the tool should be reviewed before it is trusted.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (3)

  • HighAS-012

    🔄Tool Drift

    Tool set changed silently at vsmithery: 2 tool(s) added, 3 tool(s) removed without a version bump.

    + 2 added

    check_domainlist_tlds

    3 removed

    ask_questionread_wiki_contentsread_wiki_structure

    Fix: The set of tools exposed by this server changed between scans of the same version — a sign the package was silently updated without a version bump. Audit the changelog and all tool definitions before trusting this server. Pin to a specific commit hash rather than a floating version tag.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×2

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    check_domainlist_tlds

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y hubertroy-test"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade B](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-b.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)