com.gitbuyer/mcp
REMOTE · GITBUYER.COM
Find the repo to build from: search 100k+ repos by base-fitness, clone free or buy over x402.
Available components
Last scanned (6 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 22 Oct 2026.
Category Version Control
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 409, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 27 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Oct 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 77
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Oct 2026 · Probed https://gitbuyer.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gitbuyer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gitbuyer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gitbuyer.com/mcp | Unreachable | ||
| http (plaintext) | http://gitbuyer.com/mcp | Inconclusive | 409 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_payout_wallet Create a payout wallet ~78
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_store List a repo for sale ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| github_pat | string | – | fine-grained PAT for private repos |
| github_url | string | yes | – |
| preview_paths | array | – | globs buyers may read free before paying |
| price_usd | string | – | e.g. "25.00"; defaults to 20.00 |
| wallet_base | string | – | USDC payout wallet on Base (0x…) |
| wallet_solana | string | – | USDC payout wallet on Solana |
No output schema declared.
No examples provided.
delete_store Take a listing down ~37
Take a store down and void its checkout so old links stop being payable.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| repo | string | yes | – |
No output schema declared.
No examples provided.
find_base Find a base to build from ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| building | string | yes | what you are building, in task words, e.g. "a saas with stripe subscriptions and auth" |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | – |
| building | string | – | – |
| matched | string | – | – |
| note | string | – | – |
| pick | object|null | – | – |
No examples provided.
get_github get github ~38
The GitHub connection: installations, their repos (listed or not), and orphaned listings whose repo left the installation: the catalogue-management view.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_repo Read one repo in depth ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| repo | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| license | string|null | – | – |
| pushed_at | number|null | – | – |
| repo | string | – | – |
| repo_kind | string|null | – | – |
| stars | integer|null | – | – |
| starter | boolean|null | – | – |
No examples provided.
get_sales Sales for a store ~44
One store's settled payments, newest first: count and revenue (real money only), rehearsals flagged beside.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| repo | string | yes | – |
No output schema declared.
No examples provided.
get_stats get stats ~63
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | traffic window, default 30 |
No output schema declared.
No examples provided.
get_store Get one store ~45
One listing's full settings: price, payout wallets, preview paths, whether a GitHub key is on file.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| repo | string | yes | – |
No output schema declared.
No examples provided.
get_traffic Traffic for a store ~70
One store's audience: humans vs agents by day, unique visitors, countries and cities, referrers, the files buyers tried to open before paying.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | window, default 30, max 365 |
| owner | string | yes | – |
| repo | string | yes | – |
No output schema declared.
No examples provided.
list_stores List my stores ~25
Every listed repo in this account: repo, page, price, checkout URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_repos Search the marketplace ~318
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 a starter flag. Needs no account. Empty query browses.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | exact category filter |
| language | string | – | exact primary-language filter |
| license | string | – | SPDX id (MIT, Apache-2.0, ...) or 'permissive' for the whole build-on-it set |
| limit | integer | – | max results, default 30 |
| min_stars | integer | – | only repos with at least this many stars |
| query | string | – | e.g. "fastapi stripe starter" |
| repo_kind | string | – | 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 | – | relevance (default with a query), stars (default without), or updated |
| starters | boolean | – | only templates, boilerplates and starters — repos meant as a base |
| updated_within_days | integer | – | only repos pushed within this many days |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| note | string | – | – |
| results | array | – | – |
No examples provided.
seller_setup Set up selling ~88
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_payout_wallets Set payout wallets ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_base | string | – | USDC payout wallet on Base (0x…); empty string clears |
| wallet_solana | string | – | USDC payout wallet on Solana (base58); empty string clears |
No output schema declared.
No examples provided.
update_store Update a listing ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| github_pat | string | – | new key; empty string clears |
| owner | string | yes | – |
| preview_paths | array | – | – |
| price_usd | string | – | – |
| repo | string | yes | – |
| wallet_base | string | – | – |
| wallet_solana | string | – | – |
No output schema declared.
No examples provided.
whoami Who am I ~23
Who am I signed in as, how many listings, live or rehearsal.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.gitbuyer/mcp server?
com.gitbuyer/mcp is a hosted endpoint at https://gitbuyer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gitbuyer.com
claude mcp add --transport http com-gitbuyer-mcp 'https://gitbuyer.com/mcp'
What is the com.gitbuyer/mcp server?
com.gitbuyer/mcp is listed in the public MCP registry as com.gitbuyer/mcp. Find the repo to build from: search 100k+ repos by base-fitness, clone free or buy over x402. This page covers its hosted endpoint (https://gitbuyer.com/mcp).
Is the com.gitbuyer/mcp server safe to use?
com.gitbuyer/mcp scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.gitbuyer/mcp server expose?
com.gitbuyer/mcp exposes 16 tools: whoami, seller_setup, list_stores, get_store, set_payout_wallets, and 11 more. Their descriptions and schemas cost roughly 1,440 tokens of context every time the server is loaded.
Does the com.gitbuyer/mcp server require authentication?
Its publisher declares no required credentials for com.gitbuyer/mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the com.gitbuyer/mcp server still maintained?
com.gitbuyer/mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.