Skip to content

Peskio MCP server

com.peskio/peskiopeskio.comstreamable-httpv1.0.1Scanned

Tides, sea conditions and fishing/diving day scores for 48,000+ coastal places. Read-only, no key.

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Peskio MCP server can do

The Peskio MCP server is published by peskio.com, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (tides_get_table).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Only reads 6Show 6 read-only tools
  • conditions_compare_daysRank up to 7 consecutive days at one place by fish activity score (`bite`, the default), verdict (overall or for one discipline) or water clarity, with tide coefficient, lowest low…No findings

    Why it is in this group

    • The name "conditions_compare_days" says "compare": a word for reading.
    Description, as the server wrote it
    Rank up to 7 consecutive days at one place by fish activity score (`bite`, the default), verdict (overall or for one discipline) or water clarity, with tide coefficient, lowest low, moon and a wind/wave headline per day. Use for "best day to fish this weekend", "today or Thursday?", "clearest day this week". Name the days with `dates` and let the server resolve them: "this weekend" -> dates: ["weekend"]; "today or Thursday" -> dates: ["today", "thursday"]; or use from + days for a run of days. Days with no weather forecast (beyond the ~14-day horizon, or not available) are marked astroOnly and rank last for verdict and clarity. Include a clickable link to place.url exactly as returned, including the query string. GO/marginal/NO are conditions ratings for planning, not safety; say so. The fish activity score estimates fish activity, not abundance, and is not a discipline conditions score.

    Annotations the server declares

    • title: Compare days at a place
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • conditions_get_dayOne place, one day: fish activity score (`bite`) and best windows, go/marginal/no verdict per discipline (shore, boat, rock, kayak, spearfishing) with reasons, tide, sun, moon and …No findings

    Why it is in this group

    • The name "conditions_get_day" says "get": a word for reading.
    Description, as the server wrote it
    One place, one day: fish activity score (`bite`) and best windows, go/marginal/no verdict per discipline (shore, boat, rock, kayak, spearfishing) with reasons, tide, sun, moon and solunar periods, wind and sea summary, water-clarity estimate, and how fresh the forecast is. Use for "is tomorrow good for…", "why is Saturday poor", "too rough today?", "water temperature now" (include hourly). Peskio has no current or slack-water data: never infer them from tide times. Thermocline and temperature at 5–30 m are in subsurface: a model estimate for some Mediterranean places in Spain and France, null elsewhere; when null, say Peskio does not have them and never infer them. Visibility at depth is unknown. Include a clickable link to the returned place.url with its query string unchanged. State the returned planning disclaimer when giving GO/marginal/NO; never assess whether a crossing, dive or trip is safe.

    Annotations the server declares

    • title: Fishing conditions for a day
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • places_get_profileWhat a place is: tide regime and range, coast exposure and which wind/swell directions it is sheltered from or exposed to, distance to the nearest river mouth, nearby places and la…No findings

    Why it is in this group

    • The name "places_get_profile" says "get": a word for reading.
    Description, as the server wrote it
    What a place is: tide regime and range, coast exposure and which wind/swell directions it is sheltered from or exposed to, distance to the nearest river mouth, nearby places and landmarks. Use for "is X sheltered from a north wind?", "big or small tides here?" and "near a river mouth?". Does not cover species, depth or dive sites.

    Annotations the server declares

    • title: Place profile
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • spots_find_bestRank up to 10 places within 5-25 km of a centre place for one day, on a given local hour or on each place's best daylight hour, by fish activity score (`bite`), verdict or water cl…No findings

    Why it is in this group

    • The name "spots_find_best" says "find": a word for reading.
    Description, as the server wrote it
    Rank up to 10 places within 5-25 km of a centre place for one day, on a given local hour or on each place's best daylight hour, by fish activity score (`bite`), verdict or water clarity. Use for "where near X is best tomorrow", "best spot at 7 am", "clearest water near Y". For "near me" omit placeId; if that fails, ask the user for a town or beach name. For regions wider than 25 km call it at several named centres. Link every recommended spot using its returned url exactly, query string included. Returned place names can be ambiguous across regions. Exact coordinates are unavailable in these ranked results. GO/marginal/NO are conditions ratings for planning, not safety; say so.

    Annotations the server declares

    • title: Best spots nearby
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • tides_get_tableTide times, heights and Peskio coefficient estimates for one place over up to two weeks, with sunrise, sunset, daylight low tides and moon phase.Reads private dataNo findings

    Why it is in this group

    • The name "tides_get_table" says "get": a word for reading.

    What it can reach

    • private-dataThe name "tides_get_table" says "get" and "table": it reads databases.
    Description, as the server wrote it
    Tide times, heights and Peskio coefficient estimates for one place over up to two weeks, with sunrise, sunset, daylight low tides and moon phase. Use for tide times, spring/neap tides, grandes marées, pêche à pied, tidal islands and boat launching. Heights are in metres above the stated datum. Information only: for tidal crossings, tell the user to follow the official crossing schedule. Peskio has no tidal-current or slack-water data: never derive them from these times. Explicitly label coefficients as Peskio estimates in the user language (French: estimation Peskio). Include a clickable link to place.url exactly as returned, query string included.

    Annotations the server declares

    • title: Tide table
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:19 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http peskio https://peskio.com/mcp
claude mcp add --transport http peskio https://peskio.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__peskio__places_search",
      "mcp__peskio__places_get_profile",
      "mcp__peskio__tides_get_table",
      "mcp__peskio__conditions_get_day",
      "mcp__peskio__conditions_compare_days",
      "mcp__peskio__spots_find_best"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as peskio. Review it before you use it.

Capability tags behind 1 rule
  • mcp__peskio__tides_get_table private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.peskio/peskio/verify?hash=7d336720b4988ef9237348520ba20ee06d2f4326b4732aa15984db26fdff3af6" | jq -e '.changed == false'

Pinned hash 7d336720b498, from Nov 21, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.peskio/peskio/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.peskio/peskio
[![Anlyon Radar](https://radar.anlyon.com/badge/com.peskio/peskio.svg)](https://radar.anlyon.com/servers/com.peskio/peskio)

Source: MCP Registry. Synced Nov 21, 2026, 10:17 UTC.

Peskio MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Peskio MCP server safe?

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Peskio MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Peskio MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Peskio MCP server have?

6 tools: 6 read. places_search, places_get_profile, tides_get_table, conditions_get_day, conditions_compare_days and spots_find_best.

Does the Peskio MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Peskio MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Peskio MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.