Skip to content

MCP servers › sk.rybarstvo › portal

MCP server · registry snapshot 2026-11-15 · last tested 2026-11-15

portal MCP server

Registry name sk.rybarstvo/portal

Rybárstvo.sk — the publisher's title

by rybarstvo.sk · domain (the registry's namespace rule)Website ↗

Slovak fishing waters, fish species, rules, catches, bed models and competitions. Read-only. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-15version 1.141.31streamable HTTP12 tools

Summary

sk.rybarstvo/portal is a remote MCP server listed in the official MCP registry at version 1.141.31, under the namespace of the domain rybarstvo.sk. On 2026-11-15 ProtocolProbe connected to it in read-only mode and read its inventory: 12 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
12
Last tested
2026-11-15

Tool list size

4,220 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (12 tools). Counted with Anthropic's token counter on 2026-11-15, from the tool list we read on 2026-11-15. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-15 (rybarstvo.sk), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.141.31).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-15
Mode
read-only (no tool calls)
Latest version
1.141.31, published 2026-11-15 (registry, as of the 2026-11-15 snapshot)
First listed version
2026-11-15 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-15
Package and repository
checked 2026-11-15
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-14, listed on 2026-11-15 with version 1.141.31 (published 2026-11-15).

Source: the official MCP Registry list on 2026-11-14 and on 2026-11-15.

What it is

What does this server offer?

Observed inventory
12tools
0resources
0prompts

None of its 12 tools are described as changing anything. For 12 the reading was uncertain, so no mark is shown.

  • “Full-text search over the Slovak fishing portal: fishing waters ("revír"), rivers and lakes ("tok"), river basins ("povodie"), fish species, wildlife, guides, local SRZ organisations and competitions.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • querystringrequired“Search text, e.g.”
    • typestring“Optional result type filter: rev = fishing water, tok = river/lake, pov = river basin, fish = fish species, bio = wildlife and plants, guide = guide, mo = SRZ …”
    • limitinteger“Maximum number of results (default 8).”
  • “Details of one fishing water (revír), river/lake (tok) or river basin (povodie): code, water type, river, region and district, SRZ organisation, length, coordinates, key properties and page URL.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • idinteger“Page id of the water, as returned in the id field of other tools.”
    • urlstring“Alternatively, the full page URL of the water on this site.”
  • waters_near

    “Lists fishing waters (revíry) within a radius of a Slovak district town or of given coordinates, nearest first, with distance, water type, river, district and SRZ organisation.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • citystring“Name of a Slovak district town, e.g.”
    • latnumber“Latitude in degrees (WGS84).”
    • lonnumber“Longitude in degrees (WGS84).”
    • radius_kmnumber“Search radius in kilometres (default 25).”
    • water_typestring“Optional water type: carp = carp waters, trout = trout waters, grayling = grayling waters, other = other.”
    • limitinteger“Maximum number of results (default 10).”
  • get_water_conditions

    “Current weather at the water, a modelled fishing-activity score (0-100), estimated water temperature and the best time window of the day.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • idintegerrequired“Page id of the water (from search_site or waters_near).”
  • get_fish_species

    “Looks up a fish species by Slovak or Latin name and returns what the Slovak decree says about it: year-round protection, minimum size, closed season, water types, plus the page URL.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • namestringrequired“Slovak or Latin species name, e.g.”
  • “Businesses listed in the portal catalogue near a fishing water or place: accommodation, restaurants, fishing tackle shops, e-shops (by region), guides and boat rental, and fish sales.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • kindstring“Optional type: ubytovanie = accommodation, restauracia = restaurant, predajna = tackle shop, eshop = online shop, sluzba = guide/course/boat rental/service, ry…”
    • water_idinteger“Page id of a fishing water (from search_site or waters_near); its position is used.”
    • citystring“Name of a Slovak district town, e.g.”
    • latnumber“Latitude in degrees (WGS84).”
    • lonnumber“Longitude in degrees (WGS84).”
    • limitinteger“Maximum number of results (default 10).”
  • fishing_rules_today

    “What the Slovak fishing act and decree say for a given day: whether all fishing is closed on trout, grayling and carp waters, the legal daily fishing hours, and which species are in their protection …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • water_idinteger“Optional page id of a fishing water.”
    • datestring“Optional date YYYY-MM-DD (default today, Europe/Bratislava).”
  • list_catches

    “Catches recorded by anglers on the portal (species, length, weight, date, water, whether released, angler's public name, page URL), optionally for one water or river and one species, ordered by lengt…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • water_idinteger“Optional page id of a fishing water, river or basin.”
    • speciesstring“Optional Slovak or Latin species name, e.g.”
    • orderstring“length = longest first (default), weight = heaviest first, recent = newest first.”
    • limitinteger“Maximum number of results (default 10).”
  • get_bed_model

    “Summary of the portal's 3D bed model of a reservoir, lake or river section: maximum and mean depth, water volume, surface area, water level, where the depth comes from (pre-flooding maps, literature,…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • water_idintegerrequired“Page id of the water (from search_site or waters_near).”
  • get_srz_organisation

    “A local or town organisation of the Slovak Anglers' Union (MO/MsO SRZ) by name: registered address, website, portal page and the fishing waters it manages (with ids for get_water).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • namestringrequired“Organisation or town name, e.g.”
    • limitinteger“Maximum number of waters listed (default 30).”
  • list_articleson 70 other servers

    “Articles from the portal blog (portal news, how-tos and tips, waters, fish and nature, readers' stories): title, date, category, short excerpt and URL, newest first, optionally filtered by text or ca…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • querystring“Optional search text.”
    • categorystring“Optional category: novinky-portalu = portal news, navody-a-tipy = how-tos and tips, revire-a-vody = waters, ryby-a-priroda = fish and nature, pribehy-od-vody =…”
    • limitinteger“Maximum number of results (default 8).”
  • list_competitionson 8 other servers

    “Upcoming angling competitions and events published on the portal (date, place, organiser, kind, page URL).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • kindstring“Optional kind: kapor = carp, feeder = feeder/float, privlac = spinning, muska = fly fishing and catch & release, deti = children and youth, spolocenske = socia…”
    • limitinteger“Maximum number of results (default 10).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-15.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 33
Tools with a description
100% of 12
Typical description length
269 characters

The tool set

Counted from the listing

Tools
12
Size of the list
about 2,864 tokens for an agent to load (characters ÷ 4)
Naming
12 of 12 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 12 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-15 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://rybarstvo.sk/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "portal": {
      "url": "https://rybarstvo.sk/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "portal": {
      "type": "http",
      "url": "https://rybarstvo.sk/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"portal","type":"http","url":"https://rybarstvo.sk/mcp"}'
Claude Code
claude mcp add --transport http portal https://rybarstvo.sk/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "portal": {
      "type": "streamableHttp",
      "url": "https://rybarstvo.sk/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "portal": {
      "httpUrl": "https://rybarstvo.sk/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.portal]
url = "https://rybarstvo.sk/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "portal": {
      "url": "https://rybarstvo.sk/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://rybarstvo.sk/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-15. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-15. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-15. Source: read 2026-11-15.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-15. Source: read 2026-11-15.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint rybarstvo.sk/mcpSession openedmatchesour test · 2026-11-15
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-15

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-15. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about sk.rybarstvo/portal

Answered from the data above

Who publishes sk.rybarstvo/portal?

The registry ties the namespace sk.rybarstvo to the domain rybarstvo.sk; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does sk.rybarstvo/portal need an API key or sign-in?

It opened a session without any credential on 2026-11-15. The registry entry declares no required credential; no declaration is not a guarantee.

Has sk.rybarstvo/portal been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-15
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-15, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,697 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 12 tools, 0 resources, 0 prompts.
  4. 6,057 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-15; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-15
MCP capability
tools
our test · 2026-11-15
Transport
streamable HTTP
registry · 2026-11-15
Required credentials
none declared
registry · 2026-11-15 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-15
Lifecycle status
registry · 2026-11-15
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-15

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “sk.rybarstvo/portal: MCP server record.” Data checked 2026-11-15. https://protocolprobe.com/mcp/servers/sk.rybarstvo/portal

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/sk.rybarstvo/portal)](https://protocolprobe.com/mcp/servers/sk.rybarstvo/portal)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology