dfwmetro-mcp
Related Servers
Alternatives to dfwmetro-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables agents to search evidence-backed startup credits and deals, inspect Agent Readiness report cards, and prepare canonical declaration YAML from a stdio bridge to Sourcey's hosted MCP endpoint.836 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to access hosted models and services via a local stdio bridge, with live model discovery, pricing, balance checks, and paid execution requiring cost estimates.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to search the web and fetch individual pages through two stdio tools, returning ranked results or extracted page content, titles and outbound links. It wraps a hosted, API-key-authenticated service (or a local daemon) with zero runtime dependencies.14 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn agent-callable MCP server that lets autonomous AI agents find, verify, message, schedule with, and transact with small and mid-sized businesses through a single compliance-enforced tool surface.MIT
- 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
- FlicenseNot gradedqualityCmaintenanceEnables MCP-aware clients to query and use the you-design catalog of design systems, skills, and plugins at runtime via stdio.-
TDQS
Scored across 3 tools
submit_listing is clearly distinct from the two search tools, but find_verified_listings is fully subsumed by find_listings (the description itself says it's kept only for backward compatibility and recommends find_listings with verified_only:true). The descriptions do explicitly call out the relationship, which mitigates but does not eliminate misselection risk between the two finders.
All three tools follow a clean verb_noun snake_case pattern: submit_listing, find_verified_listings, find_listings. The find_ prefix is applied predictably and no conventions are mixed.
Three tools is thin for a directory service, and effectively only two distinct capabilities exist since find_verified_listings duplicates a mode of find_listings. The scope is narrow enough that it is defensible, but it sits at the borderline of under-provisioned.
Submit plus search covers the core loop, but there is no way to retrieve a single listing by id, no explicit status-check for a submission the caller just made, and no update/correct path despite submissions starting as NOT_YET_VERIFIED. Agents can partially work around this by filtering find_listings, but there are notable dead ends.