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.

Padel Expert Lab

REMOTE · PADELEXPERTLAB.COM

Padel racket comparator for France and Belgium, in French: search, brand specs, profile-based picks.

+4 this week 77 Trust /100

Last scanned (17 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security83
  • 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
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 665 tokens (~221/item across 3 items; 3 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% 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 3 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
Capabilities100
  • Implements a current MCP spec version (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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • “chercher_raquettes” reworded the description of “prix” cosmetic
    • “recommander_raquettes” reworded the description of “budget” cosmetic
  • 9 Nov 26 71

    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://padelexpertlab.com/api/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=padelexpertlab.com CN=YR1,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 RSA 2048 SHA256-RSA 5e498dbc0712ac14a2ffa360f0954f0a727
SANs: padelexpertlab.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of padelexpertlab.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
padelexpertlab.com. DS published 5831 8 Verified
padelexpertlab.com. Verified address RRset verified with the apex keys
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
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://padelexpertlab.com/api/mcp/ Verified 200
http (plaintext) http://padelexpertlab.com/api/mcp/ HTTPS enforced 308 https://padelexpertlab.com/api/mcp/
MCP tools · 3 exposed · ~604 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
chercher_raquettes ~255

Liste les raquettes de padel par nom (marque, modèle, joueur) ou par critères : marque, niveau, forme, tranche de prix, poids, gamme femme ou junior. 10 résultats par page avec un identifiant « marque/modele-annee » pour voir_raquettes.

NameTypeReqDescription
formestring––
gammestring–Gamme femme ou junior ; sans cette valeur, les raquettes adultes mixtes.
marquestring–Slug de la marque (ex. « nox », « bullpadel », « head »).
niveaustring–Niveau annoncé par la marque.
nomstring–Nom ou début de nom : marque, modèle, joueur (ex. « vertex 05 », « at10 »).
pageinteger––
poidsstring–Légère : moins de 355 g. Standard : 355 à 364 g. Lourde : 365 g et plus.
prixstring–Tranche de prix, en euros, sur la boutique officielle de la marque (borne haute comprise : 100 € est dans « jusqu-a-100 »).
tristring––

No output schema declared.

No examples provided.

recommander_raquettes ~229

Donne jusqu'à 3 raquettes de padel classées par adéquation à un profil : niveau, style, poids, fréquence de jeu, budget. Même moteur que le quiz du site. Chaque raquette vient avec ses caractéristiques, le dernier prix relevé sur la boutique officielle de la marque quand il existe, et les raisons du choix.

NameTypeReqDescription
budgetstring–Budget maximum en euros, sur le prix de la boutique officielle de la marque. Les raquettes dans le budget passent d'abord ; une raquette plus chère ou sans prix ne complète la liste que s'il en manqu…
frequencestring–Parties par semaine.
niveaustringyesNiveau du joueur : débutant (moins d'un an), joue régulièrement, ou bon niveau (souvent, en tournoi).
poidsstring–Poids souhaité : léger (moins de 355 g), standard (355 à 365 g), lourd (365 g et plus).
stylestring–Style préféré : défendre et placer, un peu de tout, attaquer et finir.

No output schema declared.

No examples provided.

voir_raquettes ~120

Donne les caractéristiques annoncées par la marque (forme, niveau, poids, équilibre, noyau, face), le dernier prix relevé sur la boutique officielle quand il existe, les autres versions et des alternatives pour une raquette ; un tableau côte à côte pour 2 à 4 raquettes.

NameTypeReqDescription
raquettesarrayyesDe 1 à 4 identifiants « marque/modele-annee » donnés par chercher_raquettes (ex. « nox/at10-genius-18k-2026 »).

No output schema declared.

No examples provided.

Install

How do I install the Padel Expert Lab MCP server?

Padel Expert Lab is a hosted endpoint at https://padelexpertlab.com/api/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 · padelexpertlab.com

# add to Claude Code
claude mcp add --transport http com-padelexpertlab-raquettes 'https://padelexpertlab.com/api/mcp/'
Common questions

What is the Padel Expert Lab MCP server?

Padel Expert Lab is an MCP server listed in the public MCP registry as com.padelexpertlab/raquettes. Padel racket comparator for France and Belgium, in French: search, brand specs, profile-based picks. This page covers its hosted endpoint (https://padelexpertlab.com/api/mcp/).

Is the Padel Expert Lab MCP server safe to use?

Padel Expert Lab scores 77 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 Padel Expert Lab MCP server expose?

Padel Expert Lab exposes 3 tools: recommander_raquettes, chercher_raquettes, voir_raquettes. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.

Does the Padel Expert Lab MCP server require authentication?

No. We connected to Padel Expert Lab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Padel Expert Lab MCP server still maintained?

Padel Expert Lab 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 Padel Expert Lab MCP server?

VerifyMCP ran 13 checks on Padel Expert Lab, 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.