deprecated-legacy-sandbox
Related Servers
Alternatives to deprecated-legacy-sandbox
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceConnects MCP-compatible clients and CI pipelines to a hosted endpoint exposing tools for SaaS revenue-leak audits, ghost-usage evaluation, EU VAT validation, B2B net-terms reconciliation, webhook signature verification and replay simulation, dispute-evidence staging/linting, and ROI calculation.29MIT- AlicenseAqualityAmaintenanceZero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run eight data tools over stdio for product search, ad transparency, company intent, job/ATS lookup, keyword volume, domain SEO, and YouTube transcripts, returning JSON envelopes with item limits, truncation metadata, and structured errors.37 PyPIMIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to retrieve invoice and purchase order data live over stdio through tools for listing invoices, getting invoice details, and fetching purchase orders.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to perform sandboxed file reads, writes, and listing, inspect credential-masked environment variables, check git status, and execute commands with strict timeouts over a clean stdio JSON-RPC channel.MIT

yotta-dev-mcpofficial
AlicenseNot gradedqualityBmaintenanceProvides deterministic local development tools over stdio MCP, including repository mapping, code review, secret and dependency scanning, release checks, whitelisted checks, scaffolding, and workflow state tracking.14 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its no-op diagnostic role is clearly distinguishable by default.
The single tool name uses a clear snake_case pattern and is descriptive of its legacy sandbox no-op behavior. There is no mixed convention to penalize.
A single trivial no-op tool is an extremely thin tool surface for an MCP server, even one framed as deprecated. The rubric treats a single trivial tool as an extreme mismatch.
The surface offers no meaningful lifecycle operations such as listing, inspecting, updating, or cleaning up sandbox workspaces. For the stated archived sandbox domain, a no-op diagnostic stub is severely incomplete.