Coding-agent link exchange reports 58 builders across 56 sites

• Builders Backlinks reported 58 builders across 56 sites in nicklaunches’ category update; nicklaunches’ rollout post says one command connects it to Claude Code, Cursor, Codex, or Gemini CLI.
• Instead of asking both parties to place a reciprocal link later, the agent receives a partner brief and writes contextual copy in its owner’s repo, then calls mark_link_placed, as nicklaunches’ verification description explains.
• Category and DR-band matching can widen by one adjacent category when a niche is thin, nicklaunches’ exchange outline says, while a reply from nicklaunches adds that sites are vetted before matching.
• The project is free and MIT licensed. nicklaunches’ post labels it “Free, MIT,” and the public repository lists an MIT license.
• The creator positions the exchange as an “earned” backlink trade: nicklaunches’ prompt describes a one-line terminal workflow, while he calls it an MCP backlink exchange in a reply from nicklaunches.

On the product page, the MCP server exposes five literal tools, including get_link_brief and mark_link_placed, then checks placed URLs again on day 7, day 30, and monthly. Google’s link-spam policy explicitly names excessive link exchanges as an example of link spam.

The creator says discovery was never the difficult step in nicklaunches’ exchange outline. The system turns the rest of the trade into five agent calls:

1. submit_site drafts the listing from a URL.
2. list_matches returns candidate partners.
3. respond_to_match accepts or declines a trade.
4. get_link_brief supplies the partner URL, anchor options, and context.
5. mark_link_placed starts the live-page check.

The service does not crawl the user’s repo, according to nicklaunches’ verification description. It hands the repo-owning agent a brief, then lets that agent choose the page and put the link into a real sentence rather than a links dump.

The reported pool is small: nicklaunches’ category chart puts it at 56 sites, represented by 58 builders, in 19 populated categories, with 18 categories still empty. The post specifically names CMS, DevOps, Security, Writing, and Web3 among the unclaimed categories.

The service’s matching rules are deliberately narrow:

• Same category, with DR-banded partners.
• One adjacent-category expansion when the category is too thin.
• An identity-scrubbed listing and hidden URL until both parties accept.
• Weekly matching, or an immediate match when a partner is waiting.

Nicklaunches claims early registrants will be matched with later builders in their category in a reply from nicklaunches. He also says positions can reopen in another reply.

The only published operating tally is also the creator’s own: nicklaunches’ trade report logged five sites and seven links given, seven received.

The product’s premise is that agreement does not equal placement. Nicklaunches says roughly half of accepted link trades never become published links in his exchange outline.

After an agent reports a URL, the service fetches the page and checks the anchor text, rel value, and placement, according to nicklaunches’ description. The official workflow says it then repeats those checks at day 7, day 30, and monthly, notifying the other party if a link disappears.

It also classifies location, including content, footer, navigation, and sidebar, alongside dofollow, nofollow, and sponsored attributes. The service says participants, rather than the platform, decide whether a placement was fair.

Google defines link spam as creating links to or from a site primarily to manipulate rankings, and its policy lists “excessive link exchanges” as an example. Builders Backlinks bans PBNs, link farms, paid queues, and non-reciprocal credits on its house-rules page, while making one-for-one reciprocal trades its core mechanic.

The product developer separately distinguishes dofollow and nofollow links in nicklaunches’ link-attribute explainer, and the exchange records those attributes for both sides after publication.