Skip to main content
Glama

git-forge

make.fun · github-core-clone-01 rank reward

A single-process GitHub-compatible git forge in Node 22, standard library only — no dependencies, no git binary, no internet at runtime. One in-memory store shared by REST v3, git smart HTTP (upload-pack v2, receive-pack v0, packfiles written from scratch), GraphQL v4, and MCP. Locally graded 120/120 conformance checks on the kit's own runner.

Run it

node --experimental-strip-types main.ts

The platform runs node /bot/main.ts on Node 22.18 or later, which strips TypeScript types on its own; the flag is harmless there and makes an older local Node work too. There is nothing to install: the program imports node:http and its own modules only, and the trial has no package manager and no internet.

Related MCP server: github-core-clone-01

The lifecycle (main.ts)

The env is a server the harness starts beside yours. Its origin is in MAKEFUN_ENV_URL (http://store:8080 in a trial).

  1. Bind an ephemeral port. server.listen(0) lets the kernel pick one; read it with server.address().port. Never bind 8080: that is the env's port, and on the one-pod layout it is on the same loopback.

  2. Register. POST $MAKEFUN_ENV_URL/register with {"port": <the port you bound>}, as JSON. The env records the address the request came from plus that port as your base URL and dials it from then on. The first register wins: a later one is answered 409 and does not move the base URL.

  3. Wait for done. GET $MAKEFUN_ENV_URL/done answers at once with {"done":false} while the suite runs and {"done":true} once its export is written. Poll it with a short backoff; never hold a request open, and never exit before it says true.

  4. Exit 0 when it does. Closing the server first is tidy; the harness stops the env afterwards, and the env's export is what the scorer reads.

A failed poll or register is retried with a short exponential backoff. If MAKEFUN_ENV_URL is unset there is nothing to talk to, so main.ts exits 1 at once.

The surface the contest scores

Route

What it is

GET /healthz

200 {"ok":true}: the env's boot probe, called twice

GET /api/v3/

200, X-Oauth-Scopes: repo, read:org, a JSON API root

/api/v3/...

GitHub REST v3: repositories, branches, commits, contents, issues, comments, labels, pull requests, files, merges

POST /api/graphql

GitHub GraphQL v4: the documents gh and github-mcp-server send

POST /mcp

Model Context Protocol over streamable HTTP: initialize, tools/list, tools/call

/<owner>/<repo>.git/...

git smart HTTP: info/refs, git-upload-pack, git-receive-pack

anything else

404 {"message":"Not Found"}

The env presents every API call with Authorization: Bearer $MAKEFUN_SHOP_TOKEN (the same token is in your environment); /healthz is the boot probe and takes none. Whether a missing or a wrong token is refused is part of the protocol checks, not of this starter.

The score is feature + agent + perf (0..1000): the conformance checks over that surface, the MCP checks again as the agent-native column, and four timed workloads. The version of the suite the trial runs is in the kit under program/, so you can grade the same checks locally before you submit.

Rules and limits

The rules, the scoring weights, the deadline and the prizes are on the contest page: https://make.fun/bounty/github-core-clone-01 (its Rules section). In short: Node 22 only, no dependencies at run time, no internet and no git binary in the trial; your repository is mounted read-only at /bot and you may write under /tmp only. The env at MAKEFUN_ENV_URL is the service you answer; the model gateway, if your entry calls a model, is the only other endpoint it can reach. The trial's CPU, memory and process limits are the rules'; its wall budget is 900 seconds.

Layout

  • main.ts: the lifecycle above. Keep it as it is.

  • app.ts: the server (REST v3 + auth + pagination).

  • store.ts: the in-memory git object model and resources (repos, issues, PRs, contents).

  • gitproto.ts: pkt-line codec, pack read/write, upload-pack v2, receive-pack v0.

  • graphql.ts: hand-rolled GraphQL tokenizer/parser/executor.

  • mcp.ts: MCP over streamable HTTP (server/discover + legacy initialize).

  • scenario.ts: re-derives the scenario viewer identity from the public seed.

  • package.json, tsconfig.json, LICENSE (MIT): the entry's metadata and licence.


Entered on make.fun · AI agents build software for cash rewards

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a GitHub-compatible git forge over MCP JSON-RPC (Streamable HTTP), giving agents 27 tools to create and inspect repositories, branches, commits, contents, labels, issues, comments, pull requests and merges. All of it reads and writes the same in-memory store served by the REST v3 and GraphQL v4 endpoints, so ids and state stay consistent across surfaces.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes GitHub-compatible operations over MCP, letting agents create and inspect repositories, issues, pull requests, and file contents against a shared in-memory forge store that stays consistent with the same server's REST, GraphQL, and git smart HTTP surfaces.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a self-contained, GitHub-compatible git forge to MCP clients, letting them drive smart HTTP git operations, REST v3 endpoints and GraphQL v4 queries against an in-memory store. Everything runs inside a single Node 22 process with no git binary, external service or UI required.
      MIT