Nautilinks Backlinks
co.nautilinks/nautilinks-mcp · 1.0.0
Search, compare, order and track French backlink placements through the Nautilinks catalog.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://mcp.nautilinks.co/mcpstreamable-httpAuthorizationrequired, secret: Bearer token: 'Bearer sn_live_<your Nautilinks API key>'. Create the key in the Nautilinks member area under Mon compte -> Cles API (https://nautilinks.co/fr/inscription/). No OAuth in V1.
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 11 tools.
- Protocol
- 2025-06-18
- Calls itself
- nautilinks-mcp 1.0.0
- Handshake time
- 199 ms
- HTTP status
- 200
The tools it lists (11, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
aboutUse this when the user asks what Nautilinks does, how its backlink buying service works, or how an AI agent can use it. Explains the French owned backlink network sold direct, with no reseller, how a purchase flows (prepaid balance or human Stripe checkout -> article drafted & published), the three price shelves (Plancton 5 EUR, Corail 15 EUR, Nautilus 30 EUR), and how authentication works. Call this first if you're not sure what this service does.
search_sitesUse this when the user wants to find or compare websites where they can buy backlinks. Search the Nautilinks catalog by niche, language, minimum Trust Flow, maximum price per link, price shelf (Plancton 5 EUR / Corail 15 EUR / Nautilus 30 EUR), or run a free-text query. Returns domain, niche, authority metrics (TF/CF/RD/Moz DA), monthly traffic, ranked keywords, price per link and shelf for each match, plus each site's id (needed for get_site and create_order). Requires a Nautilinks API key.
get_siteUse this after search_sites when the user needs to evaluate one backlink placement before buying. Fetch the full catalog record for a single site by id: domain, niche, authority metrics, traffic, ranked keywords, price per link, price shelf, and any other published attributes. Requires a Nautilinks API key.
list_site_articlesList sold-once existing articles available on one catalog site. Returns article_id plus ranking queries, positions and impressions so you can choose a page, then pass that article_id to create_order with format=lien_insere. Requires a Nautilinks API key.
create_orderUse this only when the user has selected placements and wants to place a backlink order. This can spend the account's prepaid balance immediately. Place an order for 1 to 20 backlinks across catalog sites. Each item can request a new dedicated article or an existing-article insertion, 0/1/3/5 tier-2 links, and an optional project tag, alongside target URL, anchor and brief. Use list_site_articles first to obtain article_id for an insertion. The better of the optional promo and welcome offer is applied, then prepaid credit. Full credit settles immediately; partial credit is held and Stripe char
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
co.nautilinks/nautilinks-mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 46 days ago. The registry entry · nautilinks.co