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.

redAi Search: Polish web search engine for AI

REMOTE · SEARCH.REDAI.PL

Polish web search engine for AI and Claude (polska wyszukiwarka): .pl sites and companies.

Available components

67 Trust /100

Last scanned (19 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 590 tokens (~295/item across 2 items; 2 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 Management0
  • Stability check failed: schema churn in the 6 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.5.0 → 0.5.1 functional
    • Tool “search” changed its title: Wyszukiwarka stron .pl → Polska wyszukiwarka internetowa: strony .pl i firmy cosmetic
  • 16 Nov 26 0
    • Stability: unverified → fail ▼ security
    • Tool “search_firms” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_firm” rewrote its description, which is the text the model reads security
    • Tool “search” rewrote its description, which is the text the model reads security
    • Tool coverage: 75% → 67% ▼ functional
    • Schema quality: 775 → 540 ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.3.0 → 0.5.0 functional
    • “search” dropped the optional parameter “type” cosmetic
  • 15 Nov 26 67

    First indexed and scored.

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 21 Nov 2026 · Probed https://search.redai.pl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=search.redai.pl CN=YE2,O=Let's Encrypt,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA384 5adcbc0e154f4bb55e6d0f027f3958db58f
SANs: search.redai.pl
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of search.redai.pl. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
pl. DS published 2782 8 Verified
redai.pl. No DS 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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://search.redai.pl/mcp Verified 200
http (plaintext) http://search.redai.pl/mcp HTTPS enforced 301 https://search.redai.pl/mcp
MCP tools · 2 exposed · ~379 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_firm ~43

Pełne dane jednej firmy albo strony po id z wyniku search, ze wszystkimi podstronami i ich opisami.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

search ~336

Wyszukiwarka polskich stron .pl jak Google: dowolne zapytanie po polsku (usługa, produkt, lek, temat, pytanie). Sama rozpoznaje, czy szukasz firmy ("mechanik krakow"), czy informacji ("jak założyć działalność"), i zwraca firmy i strony z treścią w jednej kolejności trafności (pole kind: business albo site), każda z opisem, ofertą i listą podstron, na których jest to, czego szukasz (pages: url, opis, tematy). Indeks wie, GDZIE jest informacja; pełną treść daje extended=true albo pobranie wskazanej podstrony.

NameTypeReqDescription
citystring–Opcjonalnie miasto, gdy nie ma go w zapytaniu
extendedboolean–Tryb rozszerzony: dla 5 najlepszych wyników pobiera teraz podstrony wskazane przez indeks i zwraca pasujące zdania (pole live). Wolniej (2–8 s), liczy się jak 5 zapytań. Używaj, gdy potrzebny konkret…
limitinteger––
offsetinteger–Następna strona wyników: next_offset z poprzedniej odpowiedzi
querystringyesCokolwiek, po polsku, np. "ibuprofen 400 apteka", "wymiana rozrządu kraków", "jak założyć działalność"

No output schema declared.

No examples provided.

Install

How do I install the redAi Search: Polish web search engine for AI MCP server?

redAi Search: Polish web search engine for AI is a hosted endpoint at https://search.redai.pl/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 · search.redai.pl

# add to Claude Code
claude mcp add --transport http pl-redai-search 'https://search.redai.pl/mcp'
Common questions

What is the redAi Search: Polish web search engine for AI MCP server?

redAi Search: Polish web search engine for AI is an MCP server listed in the public MCP registry as pl.redai/search. Polish web search engine for AI and Claude (polska wyszukiwarka): .pl sites and companies. This page covers its hosted endpoint (https://search.redai.pl/mcp).

Is the redAi Search: Polish web search engine for AI MCP server safe to use?

redAi Search: Polish web search engine for AI scores 67 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 redAi Search: Polish web search engine for AI MCP server expose?

redAi Search: Polish web search engine for AI exposes 2 tools: search, get_firm. Their descriptions and schemas cost roughly 379 tokens of context every time the server is loaded.

Does the redAi Search: Polish web search engine for AI MCP server require authentication?

No. We connected to redAi Search: Polish web search engine for AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the redAi Search: Polish web search engine for AI MCP server still maintained?

redAi Search: Polish web search engine for AI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the redAi Search: Polish web search engine for AI MCP server?

VerifyMCP ran 13 checks on redAi Search: Polish web search engine for AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.