ToolTrust
B15/100
SecretiveShell

mcp-bridge

mcp0.5.1

@SecretiveShell

A middleware to provide an openAI compatible endpoint that can call MCP tools

By SecretiveShell | 4 findings | Scanned 9/14/2026 | tooltrust-scanner/v0.3.19 | 929

1 High3 Info

Risk Summary

Safe With Normal Controls

Secret Handling is the main signal, but overall risk remains within an acceptable range.

Potential impact: Sensitive credentials may be read, logged, or leaked to external systems.

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

  • HighAS-012

    🔄Tool Drift

    Tool set changed silently at v0.5.1: 1 tool(s) added, 1 tool(s) removed without a version bump.

    + 1 added

    bridge_find_best_route

    − 1 removed

    v1_quote

    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-010

    🔑Insecure Secret Handling ×2

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

    bridge_find_best_route

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

    bridge_find_best_route

    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

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

    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 mcp-bridge"

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)