Skip to content
gitbuyer logo

gitbuyer MCP server

Which servers in the official MCP registry are gitbuyer's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to gitbuyer

Whose server it is
  • Registry namecom.gitbuyer/mcpverified in the MCP registry

The registry name sits under gitbuyer.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools16
  • Server calls itselfgitbuyer
  • Server version1.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 166 ms.

Should an agent connect itNot proven either way yet
  • Its tools do sell clone access to a private GitHub repo, but not pay in USDC to clone a repository.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "sell clone access to a private GitHub repo", the likely first call is whoami.
  • set_payout_wallets, create_payout_wallet, create_store, update_store, delete_store change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 7 of 16 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-20
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer524 ms
  • Space in an agent's context≈ 1,921 tokensthe definitions of all its tools (16), which an agent carries on every turn
  • Tool definitionsA · 93 of 100
  • Typed results3 of 16 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 7 of 16

What an agent can do with it

  • can do · sell clone access to a private GitHub repo
  • not sure · preview a repo's tree and readme before buying
  • cannot · pay in USDC to clone a repository

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: set_payout_wallets, create_payout_wallet, create_store, update_store, delete_store

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers16 tools · read 2026-10-20
  • whoami

    Who am I signed in as, how many listings, live or rehearsal.

  • seller_setup

    The seller setup wizard. Returns wizard_url: a one-time signed-in link to the full browser wizard — it can GENERATE a payout wallet safely (keys shown once in the browser, never stored, user must confirm saving them), connect GitHub, and…

  • list_stores

    Every listed repo in this account: repo, page, price, checkout URLs.

  • get_store

    One listing's full settings: price, payout wallets, preview paths, whether a GitHub key is on file.

  • set_payout_wallets

    Save the account's default payout wallets: USDC on Base (0x…) and/or Solana (base58). The onboarding wallet step: once saved, create_store needs only the repo URL, and a chain added here propagates to existing listings so the whole…

  • create_payout_wallet

    The seller needs a payout wallet and does not have one: returns wizard_url, a one-time signed-in link to gitbuyer's in-browser wallet generator (keys created in the browser, shown once, never stored, never in the chat). Call whenever a…

  • create_store

    List a GitHub repo for sale: URL, price, payout wallet(s); USDC on Base (0x…) and/or Solana (base58); both offers the buyer the choice. Private repos need a fine-grained PAT (Contents read-only, that one repo), unless the account has the…

  • update_store

    Edit a listing without re-listing it: reprice, rewallet, rekey, or change preview paths. Only the fields you send change; the old checkout is voided so stale links stop selling.

  • delete_store

    Take a store down and void its checkout so old links stop being payable.

  • get_sales

    One store's settled payments, newest first: count and revenue (real money only), rehearsals flagged beside.

  • get_traffic

    One store's audience: humans vs agents by day, unique visitors, countries and cities, referrers, the files buyers tried to open before paying.

  • get_github

    The GitHub connection: installations, their repos (listed or not), and orphaned listings whose repo left the installation: the catalogue-management view.

  • get_stats

    The whole account at a glance: every store with its sales, revenue, visits, human/agent split and buy-intent file views, plus account totals. Start here for 'how am I doing?'.

  • find_base

    Say what you are building; get ONE repo to build from. The verdict is chosen by kind (starters first), freshness, and relevance, and comes with a plain-words why, the clone command target, and two alternatives. Adapting a proven base…

  • get_repo

    Read one gitbuyer repo in depth before cloning or buying: facts (stars, forks, freshness, releases, license, repo_kind), topics, the README excerpt, and the exact next move (clone command for free repos; x402 checkout and test URL for…

  • search_repos

    Find the best repo to BUILD ON: terms match names, descriptions, topics, categories, licenses and READMEs, ranked by relevance (name beats topics beats description beats README) plus base fitness (stars band, freshness, releases). Returns…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "gitbuyer": {
      "type": "http",
      "url": "https://gitbuyer.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http gitbuyer https://gitbuyer.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://gitbuyer.com/mcp as a custom connector in the settings.

OpenAPI spec

68 paths, read 2026-10-20. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.