Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Gitbuyer 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.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Find the repo to build from: search 100k+ repos by base-fitness, clone free or buy over x402.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http gitbuyer-mcp https://gitbuyer.com/mcp
# 2 — ask your agent for something these tools do
# whoami, seller_setup, list_stores and 13 more
Gitbuyer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GIAll 1 server
gitbuyer1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http gitbuyer-mcp https://gitbuyer.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Who am I signed in as, how many listings, live or rehearsal.
No parameter schema on file.
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 the first repo. Call this when the user wants to start selling, has no wallet, or asks to finish setup; offer wizard_url.
No parameter schema on file.
Every listed repo in this account: repo, page, price, checkout URLs.
No parameter schema on file.
One listing's full settings: price, payout wallets, preview paths, whether a GitHub key is on file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | — |
| repo | string | yes | — |
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 inventory offers it. An empty string clears a wallet.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| wallet_base | string | no | USDC payout wallet on Base (0x…); empty string clears |
| wallet_solana | string | no | USDC payout wallet on Solana (base58); empty string clears |
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 user asks to create, make or generate a wallet, or says they have none.
No parameter schema on file.
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 GitHub App installed on the repo, in which case no key is needed at all. The listing is live at page immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| github_url | string | yes | — |
| price_usd | string | no | e.g. "25.00"; defaults to 20.00 |
| wallet_base | string | no | USDC payout wallet on Base (0x…) |
| wallet_solana | string | no | USDC payout wallet on Solana |
| github_pat | string | no | fine-grained PAT for private repos |
| preview_paths | array | no | globs buyers may read free before paying |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | — |
| repo | string | yes | — |
| price_usd | string | no | — |
| wallet_base | string | no | — |
| wallet_solana | string | no | — |
| github_pat | string | no | new key; empty string clears |
| preview_paths | array | no | — |
Take a store down and void its checkout so old links stop being payable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | — |
| repo | string | yes | — |
One store's settled payments, newest first: count and revenue (real money only), rehearsals flagged beside.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | — |
| repo | string | yes | — |
One store's audience: humans vs agents by day, unique visitors, countries and cities, referrers, the files buyers tried to open before paying.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | — |
| repo | string | yes | — |
| days | integer | no | window, default 30, max 365 |
The GitHub connection: installations, their repos (listed or not), and orphaned listings whose repo left the installation: the catalogue-management view.
No parameter schema on file.
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?'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | traffic window, default 30 |
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 ships production-shaped code instead of a from-scratch demo. Needs no account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| building | string | yes | what you are building, in task words, e.g. "a saas with stripe subscriptions and auth" |
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 paid listings). Needs no account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner | string | yes | — |
| repo | string | yes | — |
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 paid listings (buy at page, x402) and free indexed repos (clone from github) together, listed first, each with stars, forks, pushed_at, releases, license and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | e.g. "fastapi stripe starter" |
| category | string | no | exact category filter |
| language | string | no | exact primary-language filter |
| min_stars | integer | no | only repos with at least this many stars |
| license | string | no | SPDX id (MIT, Apache-2.0, ...) or 'permissive' for the whole build-on-it set |
| updated_within_days | integer | no | only repos pushed within this many days |
| starters | boolean | no | only templates, boilerplates and starters — repos meant as a base |
| repo_kind | string | no | what the repo IS: starter | app | library | tool | generator. Use 'starter' or 'app' when you want a base to ADAPT; results also carry repo_kind so you can reject mismatches before cloning. |
| sort | string | no | relevance (default with a query), stars (default without), or updated |
| limit | integer | no | max results, default 30 |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Gitbuyer 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.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 Gitbuyer 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.