ToolTrust
A2/100
Smithery

slmusayev-tls-radar

mcpsmithery

@Smithery

Run SSL/TLS scans, issue free Let's Encrypt certificates (private key stays local), and monitor certificate expiry from inside Claude Code or Cowork - through a single MCP server, no account needed for scans and issuance.

By Smithery | 27 findings | Scanned 7/16/2026 | tooltrust-scanner/v0.3.19

4 Low23 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 (27)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×4

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    create_certificatefinalize_certificateremove_monitorimport_monitors

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×17

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

    scan_domaincreate_certificatecheck_certificate_propagationfinalize_certificateget_certificate_statusrenew_certificateregister_beacon_orderget_accountlist_monitorsadd_monitoradd_monitorsremove_monitorlist_expiring_certificatesget_scan_historyexport_monitorsimport_monitorsinvite_team_member

    Fix: Review and remediate the identified issue.

  • InfoAS-002

    ⚠️Excessive Permissions ×4

    declared capabilities: network access, filesystem access

    create_certificateremove_monitor

    declared capabilities: code/command execution

    finalize_certificate

    declared capabilities: HTTP requests

    import_monitors

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-010

    🔑Insecure Secret Handling ×2

    input parameter "passphrase" accepts a credential (informational; not evidence of insecure handling)

    finalize_certificate

    input parameter "webhook_secret" accepts a credential (informational; not evidence of insecure handling)

    register_beacon_order

    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.

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 slmusayev-tls-radar"

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 A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)