Atlas entry

whereboatsanchor.com

4 capabilities over MCP. First atlas observation.

Observed · passive: no tools called, no credentials sent · sha256:be994a…6cd6

Surfaces

5 protocols checked

ARDNot foundNo document retrieved
A2ANot found0 skills
MCPValid2026-07-28 · 4 tools · resources not advertised · prompts not advertised
OpenAPINot detected0 operations
WebMCPNot detected0 declarative form tools · experimental
Exact states and meaning
  • ARD
    absent

    Exact state: not found · No document retrieved

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • A2A
    absent

    Exact state: not found · 0 skills

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • MCP
    observed

    Exact state: valid · Revision 2026-07-28 · 4 tools · resources not advertised · prompts not advertised

    A usable protocol document was retrieved and validated.

    Directly observed

  • OpenAPI
    absent

    Exact state: not detected · 0 operations

    No endpoint was established from the evidence and scope that InterfaceDelta inspected.

    Not detected does not prove that no endpoint exists.

    Not observed / not fetched

  • WebMCP
    absent

    Exact state: not detected · 0 declarative form tools · experimental

    No named declarative WebMCP form tools were observed in the origin root HTML.

    Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.

    Not observed / not fetched

Capabilities

4 · inventory complete

Summary of the AI readings · beta

The service lists 4 capabilities, and 4 have AI readings.

4 capabilities are read as read-only, including get_bay_evidence, list_regions and find_anchorages.

Rows named: get_bay_evidence · list_regions · find_anchorages

Written by code from the AI readings on this page: it groups them and says nothing they do not.

The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.

MCP tools 4

  • find_anchorages

    inputs lat (required), limit, lon (required), radius_nm and 2 more

    AI Reads only 0.90

  • get_bay_evidence

    inputs bay_id, name, near

    AI Reads only 0.90

  • get_climatology

    inputs bay_id (required), month

    AI Reads only 0.80

  • list_regions

    inputs country

    AI Reads only 0.90

Not observed in this Passport: A2A skills, MCP resources, MCP prompts, OpenAPI operations.

Declared and observed

4 tools declare hints; the AI readings agree with all 4 that have a reading.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

Atlas history

1 observation

  • 4 capabilities · MCP 2026-07-28 · MCP endpoint validFirst observation
    Fingerprint and versions
    Fingerprint
    be994a841eb6da0e69eeb103793cf020beafe209afb9b07fde8d99dd27296cd6
    Passport schema
    0.5.0, passport-semantic-v4
    Consistency
    MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

About this entry

  • com.whereboatsanchor/anchorages
    Listed

    Official MCP Registry · first listed 3 Nov 2026 · last listed 3 Nov 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot
Target key
sha256:f9ddfe88026f985ee5f42b784658a84eff67c133ab0bf3cf267ba4d7f23a48e9
Locator SHA-256
79e4ccd106852eafab68f12042c4f2a0966760c2c9218ae0e7d46d0b48f26074
Snapshot generated
4 Nov 2026, 00:59 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.