Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

X402 Git

REMOTE · X402GIT.COM · SCANNED OCT 3

Buy private git repos and agent skills with USDC over x402. Read the manifest free, then pay.

Available components

remote · x402git.com 80
+10 this week 80 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1670 tokens (~278/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (83% 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
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the X402 Git MCP server?

X402 Git is a hosted endpoint at https://x402git.com/api/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 · x402git.com

# add to Claude Code
claude mcp add --transport http com-x402git-git-x402 'https://x402git.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-x402git-git-x402": {
      "url": "https://x402git.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-x402git-git-x402": {
      "type": "http",
      "url": "https://x402git.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-x402git-git-x402]
url = "https://x402git.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-x402git-git-x402": {
      "type": "remote",
      "url": "https://x402git.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-x402git-git-x402 --url 'https://x402git.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-x402git-git-x402:
    url: "https://x402git.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-x402git-git-x402": {
      "Transport": "http",
      "Url": "https://x402git.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-x402git-git-x402 -t streamable-http -u 'https://x402git.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-x402git-git-x402": {
      "type": "http",
      "url": "https://x402git.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 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.

  • 28 Sept 26 +8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 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
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 3 Oct 2026 · Probed https://x402git.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.x402git.com CN=YR1,O=Let's Encrypt,C=US 29 Aug 2026 27 Nov 2026 RSA 2048 SHA256-RSA 5bdb20a41b531c52af0dfc7cb56544c98ba
SANs: *.x402git.com, x402git.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of x402git.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
x402git.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
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402git.com/api/mcp Verified 200
http (plaintext) http://x402git.com/api/mcp HTTPS enforced 308 https://x402git.com/api/mcp
MCP tools · 6 exposed · ~1,334 tokens

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 →

Tool Tokens
check_version ~185

Wraps `GET /api/v/:owner/:slug`. The cheap call to make before every run: the latest version, when it was published, and the price. With `wallet_signature` it also answers what that wallet already owns and what the *next* fetch would cost it — `price_kind` is `new`, `update`, `free` or `owned`. Without one it never reveals what any address owns.

NameTypeReqDescription
ownerstringyesThe creator handle, e.g. `adrian`.
slugstringyesThe listing slug, e.g. `humanizer`.
wallet_signaturestring–An `X-Wallet-Signature` value: `<address>.<nonce>.<signature>`, where the nonce comes from `POST /api/auth/challenge` and the signature is EIP-191 over the challenge message. Single use.
NameTypeReqDescription
all_versionsboolean––
entitledboolean–Only with a wallet signature: true when the next fetch is free.
lateststring|nullyes–
ownedstring|null–Only with a wallet signature: the newest version this wallet holds.
ownerstringyes–
price_kindstring––
price_microstringyesMicro-USDC. `9000000` is $9.00.
published_atstring|nullyes–
releases_urlstringyes–
resource_endpointstringyes–
slugstringyes–
statusstringyes–
update_price_microstringyes`0` means updates are included for life once bought (FR-16).

No examples provided.

fetch_release ~202

Wraps `GET /api/r/:owner/:slug/v/:version`. A fresh five-minute download URL for a version this wallet already bought. Free, forever, including after the listing is retired. Never sells anything: if the wallet does not hold that version it is `not_entitled`, not a 402. `wallet_signature` is required — without a proved wallet there is nobody to be entitled.

NameTypeReqDescription
ownerstringyesThe creator handle, e.g. `adrian`.
slugstringyesThe listing slug, e.g. `humanizer`.
versionstringyesAn exact version string, e.g. `1.2.0`.
wallet_signaturestringyesAn `X-Wallet-Signature` value: `<address>.<nonce>.<signature>`, where the nonce comes from `POST /api/auth/challenge` and the signature is EIP-191 over the challenge message. Single use.
NameTypeReqDescription
artifact_sha256stringyes–
download_urlstringyes–
expires_atstringyes–
versionstringyes–

No examples provided.

get_listing ~124

Wraps `GET /api/label/:owner/:slug`. The free, unauthenticated manifest for a listing's latest passing release: file tree, sizes, licence, dependencies, security-scan result and release log. Costs nothing and needs no wallet, so read it before you buy. Computed facts and the creator's own claims are separately namespaced (`computed` vs `self_reported`).

NameTypeReqDescription
ownerstringyesThe creator handle, e.g. `adrian`.
slugstringyesThe listing slug, e.g. `humanizer`.
NameTypeReqDescription
artifact_sha256stringyes–
computed–yesEverything the analyser measured from the artifact.
manifest_urlstringyes–
ownerstringyes–
published_atstring|null––
self_reported–yesThe creator's own description and trigger hint.
slugstringyes–
statusstringyes`retired` still reads: holders keep their access (FR-43).
versionstringyes–

No examples provided.

how_to_buy ~133

Free, no wallet needed. Returns whether the listing is for sale, its latest version and new-buyer price, the listing page a person can buy on with a browser wallet, the step-by-step skill an agent with a wallet follows, the raw x402 endpoint, and this server's URL. If you cannot sign transactions, answer the person with `without_a_wallet`; if you can, follow `with_a_wallet` or call `purchase`.

NameTypeReqDescription
ownerstringyesThe creator handle, e.g. `adrian`.
slugstringyesThe listing slug, e.g. `humanizer`.
NameTypeReqDescription
for_salebooleanyesFalse when retired or when no release has passed the scan; then nothing here can be bought.
lateststring|nullyes–
listing_urlstringyesThe page. Server-rendered; readable as markdown with `Accept: text/markdown`.
manifest_urlstringyesThe free public manifest: tree, licence, dependencies, scan.
mcp_urlstringyes–
ownerstringyes–
price_microstringyesMicro-USDC for a new buyer. `9000000` is $9. A wallet that already owns a version is quoted less by `check_version`.
price_usdstringyesThe same price as dollars, the way the site prints it: `$9`, `$9.50`, `$0`.
resource_endpointstringyesThe x402 endpoint. GET it to receive the 402; pay it to receive the download.
skill_urlstringyesThe full buying procedure, as an Agent Skill. Hand this to an agent that has a wallet.
slugstringyes–
statusstringyes–
update_price_microstringyes`0` means updates are included for life once bought (FR-16).
with_a_walletstringyesWhat an agent that can sign EIP-3009 should do.
without_a_walletstringyesWhat to tell a person when you cannot sign.

No examples provided.

purchase ~420

Wraps `GET /api/r/:owner/:slug` — the same quote → screen → verify → settle → grant sequence, with the purchase recorded as `source: mcp`. Call it once with no payment: you get the x402 `PaymentRequired` body back. It arrives as `isError: true` per the x402 MCP transport, but it is not a failure — it is the price, and `accepts[0]` is the requirement to sign. Sign that EIP-3009 authorization with your own key (this server never sees it) and call again with the payment as the base64 `payment_signature` argument or as `_meta["x402/payment"]`. On success you get the version, the sha256 of the artifact, a signed download URL that expires in five minutes, and the settlement transaction in `_meta["x402/payment-response"]`. Access is granted only after the facilitator returns a transaction hash. A $0 listing returns `granted` on the first call.

NameTypeReqDescription
ownerstringyesThe creator handle, e.g. `adrian`.
payment_signaturestring–A base64 x402 payment payload signed locally against `accepts[0]` from a previous call. Equivalent to `_meta["x402/payment"]`; this argument wins when both are present. Omit both to get the 402.
quote_idstring–Required for any priced listing: echo `payment_required.extra.quote_id` from the 402 you are paying against. Omitting it on a priced buy is rejected `price_changed`; echoing a stale one is also `pric…
slugstringyesThe listing slug, e.g. `humanizer`.
wallet_signaturestring–Optional `<address>.<nonce>.<signature>`. Send it to be quoted *your* price rather than the new-buyer price; when both are present the payer in the authorization must be the same address.

No output schema declared.

No examples provided.

search_listings ~270

Free, no wallet needed. Searches every live listing — private repos, agent skills, prompt packs, toolkits — by what it does: the name, the creator's description and "use this when" line, the computed tags (artifact class, what is inside such as `skills` or `scripts`, languages) and the README. Describe the job in plain words, e.g. `humanize ai writing` or `changelog from git history`; leave `query` empty to list everything. Results are ordered by how many of your words matched and where, then by name — never by sales or popularity. Each result has the `owner` and `slug` the other tools take: read `get_listing` for the file tree and security scan, then `how_to_buy`.

NameTypeReqDescription
limitinteger–How many results to return, 1–25. Default 10; `total` says how many matched.
max_price_microstring–Only listings a new buyer can get for at most this much, in micro-USDC: `5000000` is $5, `0` is free only.
querystring–What you need the code or skill to do, in plain words. Omit or leave empty to list every live listing.
NameTypeReqDescription
querystringyes–
resultsarrayyes–
totalintegeryesHow many listings matched, before `limit`.

No examples provided.

Common questions

What is the X402 Git MCP server?

X402 Git is an MCP server listed in the public MCP registry as com.x402git/git-x402. Buy private git repos and agent skills with USDC over x402. Read the manifest free, then pay. This page covers its hosted endpoint (https://x402git.com/api/mcp).

Is the X402 Git MCP server safe to use?

X402 Git scores 80 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 X402 Git MCP server expose?

X402 Git exposes 6 tools: search_listings, how_to_buy, get_listing, check_version, purchase, fetch_release. Their descriptions and schemas cost roughly 1,334 tokens of context every time the server is loaded.

Does the X402 Git MCP server require authentication?

No. We connected to X402 Git without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the X402 Git MCP server still maintained?

X402 Git is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.