YC GraphQL MCP
Related Servers
Alternatives to YC GraphQL MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to interact with a fixed business GraphQL API as typed, safely guarded tools, including JWT authentication, rate limiting, and query/mutation protections.-
- AlicenseBqualityBmaintenanceEnables MCP clients to read account status, plans, and recent workouts, search official exercise names, and, when writes are enabled, apply confirmed preview-first plan changes and historical workout logs.22MIT
- AlicenseNot gradedqualityFmaintenanceEnables a private, owner-authenticated MCP client to call approved upstream APIs through a server-owned registry, with server-held credentials, fixed origins, bounded responses, and distinct read/write tools. Writes are opt-in and durably recorded with stable operation identifiers.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to sign in, list workspaces, and inspect workspace-scoped review findings and hosted runs. It can also prepare and, after explicit user confirmation, start or rerun an existing hosted pull-request review without exposing raw diffs, full reports, artifacts, credentials, or prompt text.2 npm-
- AlicenseNot gradedqualityCmaintenanceEnables database querying and modification through an MCP server where each action is gated by human-granted scopes, per-call confirmations for destructive operations, and revocable access.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect through a single Streamable HTTP endpoint, discover allowed backend servers and tools, inspect schemas, and invoke allowlisted catalog operations with authentication and scope checks.621 npmMIT
TDQS
Scored across 22 tools
Most tools occupy clearly distinct slots: read (yc_get_application), export, schema introspection, local operation registry, and a preview/commit/verify/receipt mutation pipeline. A few boundaries are soft — yc_status vs yc_connection both describe transport/auth state, and yc_query vs yc_run_operation both execute queries (inline vs registered), while the application-specific prepare/commit pair duplicates the generic yc_prepare_mutation/yc_commit_mutation. The descriptions do enough to resolve these, so misselection is possible but unlikely.
Strong, predictable convention: a uniform yc_ prefix with snake_case verb_noun names (yc_get_application, yc_prepare_mutation, yc_list_operations, yc_remove_operation). Minor deviations are noun-only names such as yc_status, yc_connection, and yc_mutation_receipts, which break the verb pattern but remain readable and unambiguous.
At 22 tools this sits at the heavy end of the reasonable band. The safety model (preview, commit, verify, receipts) plus schema introspection and an operation registry explains most of the surface, but the set could be trimmed — e.g. collapsing describe_schema/introspect_schema or the two prepare/commit pairs — without losing capability.
Coverage of the stated domain is unusually thorough: discovery (status, connection), schema introspection, arbitrary query execution, a local operation registry with lifecycle (register/list/remove/run), and a guarded mutation lifecycle with readback and durable receipts. Gaps are modest — no subscription support, no application deletion/withdrawal path, and financial fields are read-only by default, all of which appear intentional rather than dead ends.