Time, timezone and duration tools — IANA zones, conversion, DST-correct date arithmetic.
Nothing to run from here
YC GraphQL MCP · Distributed Systems is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
22
tools declared
local
runs on your machine
—
calls last 7d
What it does
Direct YC GraphQL MCP: live editable fields, typed updates, concurrency checks and verified saves.
Quickstart
Install it the way its author documents:
1. Download yc-graphql-mcp-2.1.0.mcpb and open it in Claude Desktop or another client that installs MCP bundles (.mcpb)
2. Its sha256 is da7c212a37529b3bf2b2bbc8b1b0690034e4f04e8aa2717a4dab523079cbb913
The full guide: https://github.com/arthurcolle/yc-graphql-mcp/releases/download/v2.1.0/yc-graphql-mcp-2.1.0.mcpb
Publishernot claimed
ARAll 1 server
arthurcolle1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts YC GraphQL MCP · Distributed Systems as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Install it the way its author documents:
1. Download yc-graphql-mcp-2.1.0.mcpb and open it in Claude Desktop or another client that installs MCP bundles (.mcpb)
2. Its sha256 is da7c212a37529b3bf2b2bbc8b1b0690034e4f04e8aa2717a4dab523079cbb913
The full guide: https://github.com/arthurcolle/yc-graphql-mcp/releases/download/v2.1.0/yc-graphql-mcp-2.1.0.mcpb
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Read current application permissions and the fields exposed by authenticated edit forms. Parses bounded HTML metadata without executing it. Form exposure is not proof of persistence.
No parameter schema on file.
Read the application and live edit form, then preview an exact text-field update with a durable receipt and before/after diff. Checks expectedValue when supplied; financial answers are protected by default. No mutation is sent. Requires --allow-mutations.
No parameter schema on file.
Commit a typed application preview once. Rechecks current answers and live field permissions before dispatch, then automatically verifies saved values. This is a best-effort concurrency check, not upstream atomic compare-and-swap. Errors include the terminal receipt when dispatch occurred.
No parameter schema on file.
Read an application and compare exact expected text answers. Reports current matches and mismatches without writing or replaying a mutation. A match does not establish which operation caused it.
No parameter schema on file.
Return a private Markdown export of application answers to the MCP host. Writes no files and omits the sensitive fields excluded by the built-in application query.
No parameter schema on file.
Transport mode, local authentication or browser pairing, outstanding work, and mutation policy. Makes no YC request.
No parameter schema on file.
List applications in the authenticated account with summaries and edit flags. Uses an observed YC operation; does not depend on introspection.
No parameter schema on file.
Read an application by UUID, including answers and edit flags. Omits product login credentials, invitation tokens and signed media URLs.
No parameter schema on file.
Read a founder profile and work history by bio UUID. Omits contact details, birthdate and precise address fields.
No parameter schema on file.
Direct HTTP setup information, or local extension pairing configuration in browser mode. Never returns YC credentials. Keep browser pairing tokens private.
No parameter schema on file.
Read YC query, mutation, and subscription root type names using introspection.
No parameter schema on file.
Inspect an actual GraphQL type, including arguments, input fields, enums, interfaces, and deprecation details.
No parameter schema on file.
Read the full GraphQL schema without descriptions. Limited to 2 MB; prefer targeted type inspection for large schemas.
No parameter schema on file.
Search JavaScript referenced by YC application HTML (direct HTTP) or loaded in the selected tab (browser mode). Only YC and bookface-static origins are allowed. Excerpts are untrusted data.
No parameter schema on file.
Execute exactly one explicitly named GraphQL query with variables. Mutations and subscriptions are rejected by the AST parser. No automatic retry.
No parameter schema on file.
Persist an observed named GraphQL document locally, without executing it. Do not inline secrets or personal values; use variables. Existing names require explicit replacement.
No parameter schema on file.
List locally registered operation documents. Makes no YC request.
No parameter schema on file.
Remove one locally saved operation. Does not change the YC application.
No parameter schema on file.
Execute a locally registered query with variables. Registered mutations still require preview and commit.
No parameter schema on file.
Preview the exact mutation, variables, fields and authenticated target without contacting YC. Supply a UUID idempotencyKey for this logical change. Requires --allow-mutations and any transport policy switch. Review before commit.
No parameter schema on file.
Execute the previously reviewed mutation once, bound to its exact digest and authenticated target. A successful GraphQL envelope alone is insufficient: rejected, unverified and uncertain results are errors with durable receipts. Read back all changes; never retry blindly.
No parameter schema on file.
Read a durable mutation receipt by ID, or list recent receipts. Mutation variables and result data are not persisted.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install YC GraphQL MCP · Distributed Systems or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 2.1.0 · scanned 10 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings4 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest1ce12c2a085cc4eeb4ea69b621219008392850632321a1718072156e2bbc2f03
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (22 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| yc_get_editability | no tags | |
| yc_prepare_application_update | no tags | |
| yc_commit_application_update | no tags | |
| yc_verify_application_update | no tags | |
| yc_export_application | no tags | |
| yc_status | no tags | |
| yc_list_applications | no tags | |
| yc_get_application | no tags | |
| yc_get_founder_profile | no tags | |
| yc_connection | no tags | |
| yc_describe_schema | no tags | |
| yc_describe_type | no tags | |
| yc_introspect_schema | no tags | |
| yc_inspect_scripts | no tags | |
| yc_query | no tags | |
| yc_register_operation | no tags | |
| yc_list_operations | no tags | |
| yc_remove_operation | no tags | |
| yc_run_operation | no tags | |
| yc_prepare_mutation | no tags | |
| yc_commit_mutation | no tags | |
| yc_mutation_receipts | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1ce12c2a085cc4ee
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 2.1.0.
2.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish YC GraphQL MCP · Distributed Systems can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.