Nautilinks Backlinks
REMOTE · MCP.NAUTILINKS.CO
Search, compare, order and track French backlink placements through the Nautilinks catalog.
Available components
Last scanned (13 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1407 tokens (~117/item across 12 items; 11 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 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
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 21 Nov 2026 · Probed https://mcp.nautilinks.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nautilinks.co | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f11ef3404d884c920ed1f00c30d94a2a |
| SANs: nautilinks.co, *.nautilinks.co | ||||||
| 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 mcp.nautilinks.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| co. | DS published | 7786 | 8 | Verified |
| nautilinks.co. | No DS | 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://mcp.nautilinks.co/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.nautilinks.co/mcp | Inconclusive | 406 |
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 →
about About Nautilinks ~108
Use 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_balance Check the prepaid balance ~54
Use this before create_order to return the prepaid balance available to this API key. create_order applies this balance after discounts: full coverage settles immediately, partial coverage reduces the human-approved Stripe remainder. Requires a Nautilinks API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_order Order backlinks ~326
Use 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 charges only the remainder through a payment_url that a human has to open and pay before anything is fulfilled; surface that link and the total to your user and never imply the purchase is complete. Call check_balance first if you want to know which way it will go. A card is never charged without a human completing the checkout. Requires a Nautilinks API key with the 'order' scope.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Stable retry key. Reuse it after a timeout to get the same quote/session; a different body with the same key is rejected. |
| items | array | yes | 1 to 20 line items, one per backlink to purchase. |
| promo_code | string | – | Optional promotion or affiliate code. The API automatically compares it with the welcome offer and applies the better discount. |
| sandbox_credit_cents | integer | – | Sandbox keys only: simulated prepaid balance, in cents, for testing full-credit, mixed, and card-only outcomes. |
No output schema declared.
No examples provided.
get_ai_visibility_plan Build order-ready items from an AI-visibility project ~83
Turn the latest uncited fan-out opportunities of one owned AI-visibility project into configured backlink items. This is read-only: it creates no cart, quote, charge or order. Review the returned items, then pass them to create_order to purchase them.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | – | yes | AI-visibility project id. The returned items can be passed directly to create_order. |
No output schema declared.
No examples provided.
get_order_status Get per-link status for one order ~106
Use this when the user wants publication progress or the live URL for a specific order. Fetch the status of each backlink item as it moves through the fulfillment pipeline (to_assign -> assigned -> drafted -> in_review -> approved -> published -> verified), along with its anchor_text, target_url, and published_url once live. Requires a Nautilinks API key.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | – | yes | The order id, e.g. from list_orders or from a paid quote's get_quote_status result. |
No output schema declared.
No examples provided.
get_quote_status Check whether a quote has been paid ~80
Use this after create_order returned a payment_url to check whether the user completed payment. Check whether the quote has been paid and get the resulting order_id once it has been converted to an order. Poll this after handing the payment_url to your user. Requires a Nautilinks API key.
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | – | yes | The quote_id returned by create_order. |
No output schema declared.
No examples provided.
get_site Get full details for one catalog site ~86
Use 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.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | – | yes | The catalog site id, as returned by search_sites. |
No output schema declared.
No examples provided.
list_ai_visibility_projects List AI-visibility projects ~38
List the AI-visibility projects owned by this account. Use a returned project id with get_ai_visibility_plan to build order-ready backlink items.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_orders List past orders ~64
Use this when the user wants their Nautilinks order history or needs to find an order id. List orders placed with this API key, including overall status and totals. Use get_order_status on a specific order id for per-link detail. Requires a Nautilinks API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_site_articles List existing articles available for insertion ~97
List 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum articles to return (default 50, max 200). |
| site_id | – | yes | The catalog site id whose available existing articles should be listed. |
No output schema declared.
No examples provided.
search_sites Search the Nautilinks backlink catalog ~343
Use 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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Filter by site language code (e.g. 'fr', 'en', 'de'). |
| limit | integer | – | Max results to return (default 20, max 50). |
| max_price_eur | number | – | Maximum price per link, in EUR. |
| min_tf | integer | – | Minimum Majestic Trust Flow. |
| niche | string | – | Filter by niche/thematic label (e.g. 'finance', 'sante', 'voyage'). |
| offset | integer | – | Pagination offset (default 0). Use with the total count returned to page through results. |
| query | string | – | Free-text search across domain and niche label. |
| shelf | string | – | Filter by price shelf: 'Plancton' (5 EUR, entry-level sites), 'Corail' (15 EUR, established sites with a real audience and a worked link profile), or 'Nautilus' (30 EUR, the network's strongest sites… |
No output schema declared.
No examples provided.
How do I install the Nautilinks Backlinks MCP server?
Nautilinks Backlinks is a hosted endpoint at https://mcp.nautilinks.co/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 · mcp.nautilinks.co
claude mcp add --transport http co-nautilinks-nautilinks-mcp 'https://mcp.nautilinks.co/mcp'
What is the Nautilinks Backlinks MCP server?
Nautilinks Backlinks is an MCP server listed in the public MCP registry as co.nautilinks/nautilinks-mcp. Search, compare, order and track French backlink placements through the Nautilinks catalog. This page covers its hosted endpoint (https://mcp.nautilinks.co/mcp).
Is the Nautilinks Backlinks MCP server safe to use?
Nautilinks Backlinks scores 83 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 Nautilinks Backlinks MCP server expose?
Nautilinks Backlinks exposes 11 tools: about, search_sites, get_site, list_site_articles, create_order, and 6 more. Their descriptions and schemas cost roughly 1,385 tokens of context every time the server is loaded.
Does the Nautilinks Backlinks MCP server require authentication?
No. We connected to Nautilinks Backlinks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nautilinks Backlinks MCP server still maintained?
Nautilinks Backlinks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Nautilinks Backlinks MCP server?
VerifyMCP ran 12 checks on Nautilinks Backlinks, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Nautilinks Backlinks: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.