Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

XFish Horgász Webáruház

REMOTE · WWW.XFISH.HU · SCANNED SEP 28

XFish.hu Hungarian fishing tackle webshop. Search 90000+ products by category, brand, price.

Available components

0 this week 71 Trust /100
Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 721 tokens (~180/item across 4 items; 4 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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the XFish Horgász Webáruház MCP server?

XFish Horgász Webáruház is a hosted endpoint at https://www.xfish.hu/app/mcpapi.php, 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.xfish.hu

# add to Claude Code
claude mcp add --transport http hu-xfish-webshop 'https://www.xfish.hu/app/mcpapi.php'
// .cursor/mcp.json
{
  "mcpServers": {
    "hu-xfish-webshop": {
      "url": "https://www.xfish.hu/app/mcpapi.php"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hu-xfish-webshop": {
      "type": "http",
      "url": "https://www.xfish.hu/app/mcpapi.php"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.hu-xfish-webshop]
url = "https://www.xfish.hu/app/mcpapi.php"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hu-xfish-webshop": {
      "type": "remote",
      "url": "https://www.xfish.hu/app/mcpapi.php",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hu-xfish-webshop --url 'https://www.xfish.hu/app/mcpapi.php' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  hu-xfish-webshop:
    url: "https://www.xfish.hu/app/mcpapi.php"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hu-xfish-webshop": {
      "Transport": "http",
      "Url": "https://www.xfish.hu/app/mcpapi.php"
    }
  }
}
# add to Vellum
assistant mcp add hu-xfish-webshop -t streamable-http -u 'https://www.xfish.hu/app/mcpapi.php'
// mcp.json
{
  "mcpServers": {
    "hu-xfish-webshop": {
      "type": "http",
      "url": "https://www.xfish.hu/app/mcpapi.php"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 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
  • 26 Sept 26 0
    • Endpoint reachability: not serving MCP → reachable ▲ functional
  • 25 Sept 26 +53
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −53
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • HTTPS: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 20 Sept 26 +53
    • HTTPS: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 19 Sept 26 −53
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • HTTPS: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Aug 26 0
    • Stability: 0.97 → pass security
  • 27 Aug 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 28 Sept 2026 · Probed https://www.xfish.hu/app/mcpapi.php

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.xfish.hu CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 10 Nov 2025 14 Nov 2026 RSA 2048 SHA256-RSA 107f11ce628768580cc85f39b60d089
SANs: www.xfish.hu, xfish.hu
CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA b259422ced9812a15a04e99528a0efa

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.xfish.hu. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
hu. present 46162 8 Verified
xfish.hu. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.xfish.hu/app/mcpapi.php Verified 200
http (plaintext) http://www.xfish.hu/app/mcpapi.php Served over HTTP 200
MCP tools · 4 exposed · ~721 tokens

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 →

Tool Tokens
get_categories ~121

Kategóriák listázása az XFish.hu webáruházból. Visszaadja a kategóriafát: ID, név, szülő, termékszám.

NameTypeReqDescription
parent_idinteger–Szülő kategória ID (0 = legfelső szint)
webshop_idinteger–Bolt ID: 0=Horgász, 1=Játék, 2=Kisállat, 3=Barkács (alapértelmezett: 0)

No output schema declared.

No examples provided.

get_manufacturers ~134

Gyártók/márkák listázása az XFish.hu webáruházból. Visszaadja a gyártó ID-kat, amelyek a search_products manufacturer_id paraméteréhez szükségesek.

NameTypeReqDescription
searchstring–Gyártónév szűrés (opcionális, pl: "shimano", "daiwa")
webshop_idinteger–Bolt ID: 0=Horgász, 1=Játék, 2=Kisállat, 3=Barkács (alapértelmezett: 0)

No output schema declared.

No examples provided.

get_product_details ~69

Egy adott termék részletes adatainak lekérdezése: név, ár, leírás, készlet, kép, gyártó, cikkszám.

NameTypeReqDescription
product_idintegeryesTermék ID (a search_products által visszaadott id mező)

No output schema declared.

No examples provided.

search_products ~397

Termékkereső az XFish.hu horgász webáruházban. Keresés szöveg, kategória, gyártó, márka, ár és készlet alapján. Magyar és angol keresés is működik.

NameTypeReqDescription
brandstring–Márkanév szűrő (pl: "Shimano", "Daiwa", "Fox"). Pontos gyártóra szűr. Ha a query tartalmazza a márkát, az automatikusan felismeri.
category_idinteger–Kategória ID szűrés (a get_categories tool-ból kapott ID)
in_stock_onlyboolean–Csak raktáron lévő termékek (alapértelmezett: igen)
limitinteger–Találatok száma (1-50, alapértelmezett: 10)
manufacturer_idinteger–Gyártó ID szűrés (a get_manufacturers tool-ból kapott ID)
max_priceinteger–Maximum bruttó ár (Ft)
min_priceinteger–Minimum bruttó ár (Ft)
querystring–Keresőkifejezés — a termék típusa (pl: "feeder bot", "bojli 20mm", "pergető orsó"). Ha a brand-et is megadod, a query csak a típust tartalmazza.
sortstring–Rendezés: relevance=releváns, price_asc=legolcsóbb, price_desc=legdrágább, name_asc=névsor
webshop_idinteger–Bolt ID: 0=Horgász, 1=Játék, 2=Kisállat, 3=Barkács (alapértelmezett: 0)

No output schema declared.

No examples provided.

Common questions

What is the XFish Horgász Webáruház MCP server?

XFish Horgász Webáruház is an MCP server listed in the public MCP registry as hu.xfish/webshop. XFish.hu Hungarian fishing tackle webshop. Search 90000+ products by category, brand, price. This page covers its hosted endpoint (https://www.xfish.hu/app/mcpapi.php).

Is the XFish Horgász Webáruház MCP server safe to use?

XFish Horgász Webáruház scores 71 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 XFish Horgász Webáruház MCP server expose?

XFish Horgász Webáruház exposes 4 tools: search_products, get_categories, get_product_details, get_manufacturers. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.

Does the XFish Horgász Webáruház MCP server require authentication?

No. We connected to XFish Horgász Webáruház without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the XFish Horgász Webáruház MCP server still maintained?

XFish Horgász Webáruház is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.