ToolTrust
B15/100
Smithery

atomadictech-ud4n-aaaa-nexus

mcpsmithery

@Smithery

By Smithery | 11 findings | Scanned 5/27/2026 | tooltrust-scanner/v0.3.12

Repository health

Popularity and maintenance signals alongside the security grade.

Stars

Not collected

Forks

Not collected

GitHub metadata pending

Contributors

Not collected

GitHub metadata pending

Last commit

Not collected

GitHub metadata pending

Last release

Not collected

GitHub metadata pending

Release version

Not collected

Latest GitHub release

Stars trend

Daily star additions · History data pending

—

No observed star events yet.

——

Pull request activity

Weekly PR events · History data pending

No observed PR events yet.

——
Last scan May 27, 2026
2 High9 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 (11)

  • HighAS-010

    🔑Insecure Secret Handling ×2

    input parameter "max_tokens" appears to accept a secret or credential

    inferenceinference_stream

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×9

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

    healthmetricsoracle_entropyoracle_hallucinationratchetgate_sessioninferenceinference_streamratchetgate_registerratchetgate_advance

    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 atomadictech-ud4n-aaaa-nexus"

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)