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.

Pavels Web Solutions

REMOTE · PAVELS.DEV

Read-only access to pavels.dev: services, case studies, articles and team of a web dev studio.

Available components

67 Trust /100

Last scanned (5 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Developer Tools

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 309 tokens (~44/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 17 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 13 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 65

    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 17 Oct 2026 · Probed https://pavels.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pavels.dev CN=YE2,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 6167ff5e9997d47332a959cd7482d670936
SANs: *.pavels.dev, pavels.dev
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 pavels.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
pavels.dev. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; worker-src 'self' blob:; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; frame-src https://www.youtube.com https://www.youtube-nocookie.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pavels.dev/mcp Verified 200
http (plaintext) http://pavels.dev/mcp HTTPS enforced 301 https://pavels.dev/mcp
MCP tools · 7 exposed · ~272 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_contact_details ~33

Explain how a person can start a project with Pavels Web Solutions. There is no endpoint an agent can submit to.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_articles ~45

List articles published on the Pavels Web Solutions blog (web development, performance, SEO).

NameTypeReqDescription
limitinteger–How many to return (default 20, max 50).

No output schema declared.

No examples provided.

list_case_studies ~42

List client projects Pavels Web Solutions has delivered, newest first.

NameTypeReqDescription
limitinteger–How many to return (default 20, max 50).

No output schema declared.

No examples provided.

list_services ~28

List the services Pavels Web Solutions offers, each with a short summary and the page describing it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_team ~18

List the people working at Pavels Web Solutions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_page ~69

Return the full text of one public page of pavels.dev as Markdown. Use list_services, list_case_studies or list_articles first to get a valid path.

NameTypeReqDescription
pathstringyesThe site path, for example "/case-studies/retusescu" or "/services/web-apps".

No output schema declared.

No examples provided.

search_content ~37

Search the titles and summaries of every service, case study and article for a phrase.

NameTypeReqDescription
querystringyesThe phrase to look for.

No output schema declared.

No examples provided.

Install

How do I install the Pavels Web Solutions MCP server?

Pavels Web Solutions is a hosted endpoint at https://pavels.dev/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 · pavels.dev

# add to Claude Code
claude mcp add --transport http dev-pavels-pavels-web-solutions 'https://pavels.dev/mcp'
Common questions

What is the Pavels Web Solutions MCP server?

Pavels Web Solutions is an MCP server listed in the public MCP registry as dev.pavels/pavels-web-solutions. Read-only access to pavels.dev: services, case studies, articles and team of a web dev studio. This page covers its hosted endpoint (https://pavels.dev/mcp).

Is the Pavels Web Solutions MCP server safe to use?

Pavels Web Solutions 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 Pavels Web Solutions MCP server expose?

Pavels Web Solutions exposes 7 tools: list_services, list_case_studies, list_articles, list_team, search_content, and 2 more. Their descriptions and schemas cost roughly 272 tokens of context every time the server is loaded.

Does the Pavels Web Solutions MCP server require authentication?

No. We connected to Pavels Web Solutions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pavels Web Solutions MCP server still maintained?

Pavels Web Solutions is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.