com.gitbuyer/mcp
REMOTE · GITBUYER.COM · SCANNED SEP 20
Find the repo to build from: search 100k+ repos by base-fitness, clone free or buy over x402.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_store). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1675 tokens (~98/item across 17 items; 16 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
- Structured output schemas are declared (19% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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'
{
"mcpServers": {
"com-gitbuyer-mcp": {
"url": "https://gitbuyer.com/mcp"
}
}
} {
"servers": {
"com-gitbuyer-mcp": {
"type": "http",
"url": "https://gitbuyer.com/mcp"
}
}
} [mcp_servers.com-gitbuyer-mcp] url = "https://gitbuyer.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gitbuyer-mcp": {
"type": "remote",
"url": "https://gitbuyer.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-gitbuyer-mcp --url 'https://gitbuyer.com/mcp' --transport streamable-http
mcp_servers:
com-gitbuyer-mcp:
url: "https://gitbuyer.com/mcp" {
"McpServers": {
"com-gitbuyer-mcp": {
"Transport": "http",
"Url": "https://gitbuyer.com/mcp"
}
}
} assistant mcp add com-gitbuyer-mcp -t streamable-http -u 'https://gitbuyer.com/mcp'
{
"mcpServers": {
"com-gitbuyer-mcp": {
"type": "http",
"url": "https://gitbuyer.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://gitbuyer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gitbuyer.com | CN=WE1,O=Google Trust Services,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f01babc3a01935171393ec8a5bcabbaf |
| SANs: gitbuyer.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
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 | Verified | 200 | |
| http (plaintext) | http://gitbuyer.com/mcp | HTTPS enforced | 301 | https://gitbuyer.com/mcp |
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.
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 77 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?
No. We connected to com.gitbuyer/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.gitbuyer/mcp server still maintained?
com.gitbuyer/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.