TrustedMCP
Related Servers
Alternatives to TrustedMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets an agent inspect and audit MCP servers before connecting to them, checking their exposed tools, prompts and resources for tool poisoning, shadowing, excessive permissions, leaked secrets and unsafe transports against 24 deterministic rules. Results are returned as findings with evidence, remediation and CWE/OWASP references, and can fail CI with SARIF, Markdown or standalone HTML reports.118 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect and diagnose their own MCP setup by exposing read-only tools that audit configured servers, report which coding agents have configs, surface misplaced or duplicated registrations, and list curated preset packs. It also powers CLI workflows for checking handshake, tool lint, and tool-surface quality scores of any stdio server.32 npmMIT
- AlicenseAqualityCmaintenanceSecurity scanning for MCP servers from the inside out. Provides runtime inspection, AST-based static analysis, config audit, dependency analysis, and OWASP MCP Top 10 compliance in a single MCP server.55194 npm6MIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP tools over an AgentFox control plane: agents found in a codebase, the tools and MCP servers each can reach, security findings, policy linting and simulation, and audit verification. 25 tools, none changing enforcement; implemented in src/agentfox/apps/mcp_server.py as JSON-RPC 2.0 over stdio on the standard library, with no MCP SDK dependency.227 PyPI4Apache 2.0

repo-doctorofficial
AlicenseNot gradedqualityDmaintenanceMCP server that produces scored, evidence-cited audits of public GitHub repos via tools for fetching metadata, reading files, scanning git history, and checking hygiene.MIT- AlicenseNot gradedqualityCmaintenanceEnables searching and comparing cataloged MCP servers by capability, retrieving installation snippets and trust reports, and checking a ledger of requested abilities through MCP tools.MIT
TDQS
Scored across 4 tools
check_config and find_alternatives are clearly distinct purposes, but lookup_server and registry_lookup overlap heavily: both accept a package name or search term, both return a TrustedMCP grade, and lookup_server even falls back to returning registry entries. An agent must infer 'grade-first vs registry-entry-first' intent from subtle wording rather than a clear boundary.
All four names are snake_case and readable, with three following verb_noun (lookup_server, check_config, find_alternatives). Only registry_lookup flips to noun_verb, a minor deviation that still reads sensibly.
Four tools is a tight, sensible surface for a server-grading service: single lookup, bulk config audit, discovery, and registry metadata. It is slightly lean (no way to browse all categories or compare two servers directly), but every tool earns its place.
The lifecycle is largely covered: query one server, audit a whole config, find better-graded replacements, and fetch registry/security advisories. Minor gaps exist around cross-server comparison, grade explanation/reporting, and enumerating categories, none of which blocks core agent workflows.