Angling Lines
REMOTE · WWW.ANGLINGLINES.COM · SCANNED OCT 3
Carp fishing lakes in France: search venues, check availability, get week prices, book.
Available components
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
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3873 tokens (~484/item across 8 items; 8 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 Management53
- Stability observed for 16 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the Angling Lines MCP server?
Angling Lines is a hosted endpoint at https://www.anglinglines.com/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 · www.anglinglines.com
claude mcp add --transport http com-anglinglines-angling-lines 'https://www.anglinglines.com/mcp'
{
"mcpServers": {
"com-anglinglines-angling-lines": {
"url": "https://www.anglinglines.com/mcp"
}
}
} {
"servers": {
"com-anglinglines-angling-lines": {
"type": "http",
"url": "https://www.anglinglines.com/mcp"
}
}
} [mcp_servers.com-anglinglines-angling-lines] url = "https://www.anglinglines.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-anglinglines-angling-lines": {
"type": "remote",
"url": "https://www.anglinglines.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-anglinglines-angling-lines --url 'https://www.anglinglines.com/mcp' --transport streamable-http
mcp_servers:
com-anglinglines-angling-lines:
url: "https://www.anglinglines.com/mcp" {
"McpServers": {
"com-anglinglines-angling-lines": {
"Transport": "http",
"Url": "https://www.anglinglines.com/mcp"
}
}
} assistant mcp add com-anglinglines-angling-lines -t streamable-http -u 'https://www.anglinglines.com/mcp'
{
"mcpServers": {
"com-anglinglines-angling-lines": {
"type": "http",
"url": "https://www.anglinglines.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ 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 3 Oct 2026 · Probed https://www.anglinglines.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anglinglines.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 28341a491fff367713ed87e20d71fb13 |
| SANs: anglinglines.com, *.anglinglines.com | ||||||
| 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 www.anglinglines.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| anglinglines.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=15768000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.anglinglines.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.anglinglines.com/mcp | HTTPS enforced | 301 | https://www.anglinglines.com/mcp |
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 →
get_quote Get Quote ~489
Quote one Angling Lines venue for one fixed 7-day week: give a venue name or slug, a Saturday arrival date (YYYY-MM-DD) and the party, and get the total price for the whole party for the whole week. Prices come from the live booking engine — the venue price plus the cheapest Channel crossing for the vehicles quoted — and are in GBP. Returns a structured "unavailable" result, not a price, when that week is not free for that party.
| Name | Type | Req | Description |
|---|---|---|---|
| accommodation_ids | array | – | Selected accommodation IDs returned by list_swims for this date. GCL booking_option includes the matching cabin automatically. |
| anglers | integer | yes | Actual number of fishing guests supplied by the customer, never a package or swim capacity. Keep 2 guests as 2 even for a package with capacity 5. |
| booking_option | integer | – | Golden Carp Lake whole package explicitly chosen by the customer after seeing available list_swims options: 1 cabin & swim 1; 2 all of swims 2,3,4; 3 exclusive without cabin; 4 exclusive with cabin.… |
| cars | integer | – | Number of cars travelling — crossing costs are per vehicle. Ask when unknown for a crossing quote; do not silently assume 1. Pass 0 for a van-only party. Defaults to 1 for older callers. |
| date | string | yes | The Saturday arrival date of the 7-day week, as YYYY-MM-DD. Every stay runs Saturday to Saturday. |
| exclusive | boolean | – | Quote the venue exclusively for this party. Some party sizes force exclusive use anyway. |
| include_crossing | boolean | – | True when the customer wants a crossing, including cheapest crossing at a crossing-optional venue. False for venue-only. Omit to use the venue default. |
| non_anglers | integer | – | Number of non-fishing guests. Defaults to 0. |
| swims | array | – | Chosen swim numbers from list_swims; omit for suitable available defaults. Requote after changing swims. |
| vans | integer | – | Number of vans travelling. Preserve the customer's count in all crossing and booking calls. Defaults to 0. |
| venue | string | yes | The venue to quote, by name or slug, e.g. "Beaurepaire". |
No output schema declared.
No examples provided.
list_crossings List Channel Crossings ~460
List the Channel crossing choices for one trip — venue, Saturday arrival date (YYYY-MM-DD) and party — cheapest first. Each option gives the route, operator, ferry/tunnel type, crossing time, an overnight flag and the TOTAL holiday price with that crossing, plus the outbound/inbound route ids to pass to prepare_booking when the customer picks one. The cheapest option matches the get_quote price. Crossing choice is subject to sailing availability at checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| accommodation_ids | array | – | Selected accommodation IDs returned by list_swims for this date. GCL booking_option includes the matching cabin automatically. |
| anglers | integer | yes | Actual number of fishing guests supplied by the customer, never a package or swim capacity. Keep 2 guests as 2 even for a package with capacity 5. |
| booking_option | integer | – | Golden Carp Lake whole package explicitly chosen by the customer after seeing available list_swims options: 1 cabin & swim 1; 2 all of swims 2,3,4; 3 exclusive without cabin; 4 exclusive with cabin.… |
| cars | integer | – | Number of cars travelling. Use the same confirmed count as get_quote; crossing costs are per vehicle. Pass 0 for a van-only party. Defaults to 1 for older callers. |
| date | string | yes | The Saturday arrival date of the 7-day week, as YYYY-MM-DD. |
| exclusive | boolean | – | Whether the venue is being booked exclusively. |
| include_crossing | boolean | – | True when the customer wants a crossing, including cheapest crossing at a crossing-optional venue. False for venue-only. Omit to use the venue default. |
| non_anglers | integer | – | Number of non-fishing guests. Defaults to 0. |
| swims | array | – | Chosen swim numbers from list_swims; omit for suitable available defaults. Requote after changing swims. |
| vans | integer | – | Number of vans travelling. Use the same confirmed count as get_quote. Defaults to 0. |
| venue | string | yes | The venue being booked, by name or slug, e.g. "Beaurepaire". |
No output schema declared.
No examples provided.
list_swims List Swim Availability ~238
Check swim and accommodation availability for a venue on a specific Saturday date and actual party. Returns free/taken swim numbers, capacities, venue-specific rules and map URL. Golden Carp Lake sells four fixed booking_options, never individual swims: if asked for one swim, explain the full package and obtain customer acceptance before passing booking_option to get_quote, list_crossings or prepare_booking. Never silently expand a single-swim request or increase the party to package capacity. At other swim venues pass chosen swims and accommodation_ids, or allow suitable free defaults. Choices can affect price, so quote the final selection before confirming.
| Name | Type | Req | Description |
|---|---|---|---|
| anglers | integer | – | Actual number of anglers, not package or swim capacity. Pass it so the tool can check which choices fit the party. |
| date | string | yes | The Saturday arrival date of the 7-day week, as YYYY-MM-DD. |
| exclusive | boolean | – | Whether the customer wants the venue exclusively. |
| non_anglers | integer | – | Number of non-fishing guests. Defaults to 0. |
| venue | string | yes | The venue, by name or slug, e.g. "Fullys Lake". |
No output schema declared.
No examples provided.
list_venues List Venues ~97
List every bookable Angling Lines carp fishing venue in France, with its headline facts (lake size, swims, capacity, lake record, accommodation), boolean feature flags (dogs_allowed, catfish, pool_or_hot_tub, …) and canonical URLs. The feature keys match the search_venues filter names, so prefer search_venues to filter server-side. Takes no arguments. This is the full catalogue, not an availability check.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_booking Prepare Booking ~644
Prepare a confirmed trip, including selected swims, accommodation, Golden Carp Lake booking_option and crossing, for the Angling Lines review page. Returns a live total and signed prefill link; creates nothing until the customer opens it. Call after the customer confirms the venue, Saturday date, party and choices. Missing or unavailable choices return a reason to resolve IN CHAT with list_swims/list_crossings; GCL can be booked through chat. Nothing is held or booked until checkout is completed.
| Name | Type | Req | Description |
|---|---|---|---|
| accommodation_ids | array | – | Selected accommodation IDs returned by list_swims for this date. GCL booking_option includes the matching cabin automatically. |
| anglers | integer | yes | Actual number of fishing guests supplied by the customer, never a package or swim capacity. Keep 2 guests as 2 even for a package with capacity 5. |
| booking_option | integer | – | Golden Carp Lake whole package explicitly chosen by the customer after seeing available list_swims options: 1 cabin & swim 1; 2 all of swims 2,3,4; 3 exclusive without cabin; 4 exclusive with cabin.… |
| cars | integer | – | Number of cars travelling. Pass the customer's confirmed count from get_quote/list_crossings unchanged, including 0 for a van-only party. Defaults to 1 for older callers. |
| date | string | yes | The Saturday arrival date of the 7-day week, as YYYY-MM-DD. Every stay runs Saturday to Saturday. |
| dog_info | string | – | Dog count and breed(s) supplied by the customer, e.g. "2 dogs: Labrador and Spaniel". Ask for missing count/breeds; do not invent them. Only for dog-friendly venues. Saved on the booking and review/e… |
| exclusive | boolean | – | Book the venue exclusively for this party. Some party sizes force exclusive use anyway. |
| inbound_route_id | integer | – | Inbound crossing route id from list_crossings. Must be given together with outbound_route_id. |
| include_crossing | boolean | – | True when the customer wants a crossing, including cheapest crossing at a crossing-optional venue. False for venue-only. Omit to use the venue default. |
| non_anglers | integer | – | Number of non-fishing guests. Defaults to 0. |
| outbound_route_id | integer | – | Outbound crossing route id from list_crossings. Omit (with inbound_route_id) to book the cheapest crossing. |
| swims | array | – | Swim NUMBERS the customer chose (from list_swims), e.g. [1, 4]. Omit to auto-pick good free swims — the customer can change them on the review page. Ignored at venues without designated swims. |
| vans | integer | – | Number of vans travelling. Pass the customer's confirmed count from get_quote/list_crossings unchanged. Defaults to 0. |
| venue | string | yes | The venue to book, by name or slug, e.g. "Beaurepaire". |
No output schema declared.
No examples provided.
search_categories Search Categories ~123
Browse the curated venue categories Angling Lines maintains — themed collections such as big carp lakes, family-friendly lakes, lakes with a swimming pool, or lakes close to Calais. Called with no arguments it lists every category with its description and venue count; pass a category slug to get the bookable venues in that category. These lists are hand-picked by Angling Lines, so they cannot be reproduced by filtering on venue attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | The category slug to open, e.g. "big-carp-lakes". Omit it to list every category. |
No output schema declared.
No examples provided.
search_venues Search Venues ~701
The tool for "find me a lake": search the Angling Lines catalogue by party size, features and availability, exactly the way the website search does. Every filter is optional — call it with nothing for the whole catalogue, or combine party size ("anglers", "non_anglers"), lake facts ("min_carp_lb", "min_lake_acres") and facilities ("accommodation", "all_inclusive", "meals", "pool_or_hot_tub", "tackle_hire", "catfish", "dogs_allowed", "campervans", "rowing_boats", "bait_boats", "bait_on_site"). Add a Saturday "date" (YYYY-MM-DD) to get real availability plus "alternatives" — venues that match everything but that week, each with the nearest earlier and later free Saturday — or "months" (["YYYY-MM"]) to scan whole months. Narrow to a curated theme with "category", whose slugs come from search_categories.
| Name | Type | Req | Description |
|---|---|---|---|
| accommodation | boolean | – | Only lakes with on-site accommodation, rather than bivvy fishing. |
| all_inclusive | boolean | – | Only all-inclusive venues. |
| anglers | integer | – | Number of anglers (fishing guests) in the party. Defaults to 1. |
| bait_boats | boolean | – | Only venues where bait boats are allowed. |
| bait_on_site | boolean | – | Only venues selling bait on site. |
| campervans | boolean | – | Only venues that take campervans and motorhomes. |
| category | string | – | Narrow to a curated search category by slug, e.g. "big-carp-lakes". Call search_categories for the slugs that exist. |
| catfish | boolean | – | Only venues stocked with catfish. |
| crossing_optional | boolean | – | Only venues bookable WITHOUT a Channel crossing — the holiday is priced venue-only and the customer arranges their own travel. |
| date | string | – | A single Saturday arrival date as "YYYY-MM-DD", e.g. "2026-09-05". Give this to get real availability plus earlier/later alternatives. Stays run Saturday to Saturday, so any other weekday is rejected. |
| dogs_allowed | boolean | – | Only venues that accept dogs and other pets. |
| fish_from_accommodation | boolean | – | Only lakes where you can fish from the accommodation. Applies with "accommodation". |
| meals | boolean | – | Only venues where meals are available. |
| min_carp_lb | integer | – | Only lakes whose carp record is at least this many pounds, e.g. 60. |
| min_lake_acres | number | – | Only lakes of at least this many acres, e.g. 10. |
| months | array | – | Whole months to scan, each as "YYYY-MM", e.g. ["2026-09", "2026-10"]. Use this OR "date". Returns venues with at least one free week in those months. |
| non_anglers | integer | – | Number of non-fishing guests travelling with the party. Defaults to 0. |
| pool_or_hot_tub | boolean | – | Only venues with a swimming pool or a hot tub. |
| rowing_boats | boolean | – | Only venues with rowing boats. |
| sleeps | integer | – | Only lakes whose accommodation sleeps at least this many. Applies with "accommodation". |
| tackle_hire | boolean | – | Only venues where tackle can be hired. |
No output schema declared.
No examples provided.
venues_available_on_date Venues Available On Date ~248
Check which Angling Lines venues genuinely have space for a party, either on one specific Saturday or across a whole month. Stays are fixed 7-day weeks, so an arrival date must be a Saturday in "YYYY-MM-DD" form; pass "month" as "YYYY-MM" instead to scan a whole month (defaults to the current month). Returns only venues with real availability, each with its free arrival dates and remaining capacity. Use this — not list_venues — whenever the question is about what is free or bookable.
| Name | Type | Req | Description |
|---|---|---|---|
| anglers | integer | yes | Number of anglers (fishers) in the party. |
| date | string | – | A single Saturday arrival date as "YYYY-MM-DD", e.g. "2026-09-05". Use this OR "month". Stays run Saturday to Saturday, so any other weekday is rejected. |
| month | string | – | A whole month to scan as "YYYY-MM", e.g. "2026-09". Use this OR "date". Defaults to the current month when neither is given. |
| non_anglers | integer | – | Number of non-fishing guests travelling with the party. Defaults to 0. |
No output schema declared.
No examples provided.
What is the Angling Lines MCP server?
Angling Lines is an MCP server listed in the public MCP registry as com.anglinglines/angling-lines. Carp fishing lakes in France: search venues, check availability, get week prices, book. This page covers its hosted endpoint (https://www.anglinglines.com/mcp).
Is the Angling Lines MCP server safe to use?
Angling Lines scores 79 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 Angling Lines MCP server expose?
Angling Lines exposes 8 tools: list_venues, get_quote, venues_available_on_date, search_categories, search_venues, and 3 more. Their descriptions and schemas cost roughly 3,000 tokens of context every time the server is loaded.
Does the Angling Lines MCP server require authentication?
No. We connected to Angling Lines without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Angling Lines MCP server still maintained?
Angling Lines 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.