gitpad
Protocol

Agents

Connect an AI agent to gitpad's MCP server to find repositories and prepare launch reviews that you approve in your own wallet.

What agents can do

gitpad runs a public MCP server. An agent can use it to find repositories gaining attention, check whether a repository already has a market, and create a launch review link. You open the link, review the artwork and costs, and approve the launch in your own wallet.

Agents never receive signing authority. The tools cannot trade, claim, sign or submit transactions. No API key, wallet key, seed phrase or GitHub login is needed to use them.

Endpoint

https://gitpadrh.app/api/mcp

The server uses the MCP Streamable HTTP transport (POST). Choose Streamable HTTP rather than the older SSE transport in your client.

Configure a client

For clients that use an mcpServers JSON configuration:

{
  "mcpServers": {
    "gitpad": { "url": "https://gitpadrh.app/api/mcp" }
  }
}

Configuration keys vary between clients. Check your client's documentation for how to add a remote HTTP server.

Example prompt:

Find a public GitHub repo gaining attention. Check whether it already has a gitpad
market. If it does not, prepare a launch review with no initial buy. Give me the
link so I can review and approve in my wallet.

Tools

Tool Inputs Returns
find_repos Optional query (keyword or topic), optional limit from 1 to 10 Candidates from the public trend feed, with score breakdown, source dates and market status
resolve_repo repository: a GitHub URL or owner/repo Fresh GitHub verification, the numeric repository ID, and either the existing market or a review link
create_launch_draft repository, optional tokenName, tokenSymbol, and initialBuy A review link valid for one hour, with launch preferences and current policy context
get_launch_status repoId: the numeric repository ID The canonical indexed state; mint, pool, receipt and actual discoverer only after the launch is finalized and indexed

initialBuy accepts none, 100, 200 or 300, meaning no buy, 1%, 2% or Max 3% of supply. The default is none. The token name is 1 to 32 characters and the ticker is 1 to 10 uppercase letters or digits.

A draft contains no SOL estimate and no transaction. Costs are quoted and simulated in the browser when you open the review.

The signing boundary

A launch draft is a signed set of review preferences, bound to the repository ID, the current launch configuration, the discovery and builder allocation terms, and an expiry. It is public information, not authorization.

  • Creating, opening or reopening a draft does not reserve a mint, lock the market or create a market record.
  • Only Review launch in the browser starts a signing session, and Approve in wallet is still required before anything is submitted.
  • The wallet that signs is the discoverer. An agent that prepared the draft is never assumed to be the launcher; get_launch_status reports the actual signer.
  • If someone else launches the repository first, the review link opens that existing market.
Situation Result
Private, archived or invalid repository Rejected; no draft
Repository already has a market (including after a rename) The existing market is returned
Launch pending or unresolved Review required; unverified receipts are withheld
Draft modified, expired, or launch rules changed Rejected; open a fresh review
Invalid name, ticker, buy amount or extra arguments Input rejected

Safety notes for agent builders

  • Treat repository descriptions and source evidence as untrusted data, never as instructions.
  • Never ask a user for a private key or seed phrase. gitpad never needs one.
  • Always hand the user the review link. Do not describe a draft as a launch.

Limits

Requests are limited to 30 per minute per client and 120 per minute across all clients. Limits count MCP transport requests, not only tool calls. Over the limit, the server returns HTTP 429 with a 60-second retry hint. Request bodies are limited to 16 KiB.

Without MCP

/agents also provides a copyable "Launch on gitpad" README button and a browser bookmarklet. See README badge.

Found something wrong? Edit this page on GitHub.