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.

Bahdan Hal

REMOTE · BAHDANHAL.PL

Bahdan Hal software consulting: services, pricing, CV and skills, and contact requests.

Available components

+3 this week 82 Trust /100

Last scanned (22 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 4 Nov 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 Security74
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 208 tokens (~52/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management72
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 5 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
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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 65 to 69.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 55 to 59.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 49 to 52.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 42 to 45.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 35 to 39.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 29 to 32.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 22 to 25.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 15 to 19.

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 4 Nov 2026 · Probed https://bahdanhal.pl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bahdanhal.pl CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 c615ca1560ed54140e1d9e0f3bdde30b
SANs: bahdanhal.pl, *.bahdanhal.pl
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bahdanhal.pl. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pl. present 2782 8 Verified
bahdanhal.pl. 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
x-content-type-options nosniff
x-frame-options DENY
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://bahdanhal.pl/mcp Verified 200
http (plaintext) http://bahdanhal.pl/mcp HTTPS enforced 301 https://bahdanhal.pl/mcp
MCP tools · 4 exposed · ~162 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_cv_and_skills ~37

Get Bahdan Hal's full curriculum vitae (CV), including professional experience, technical skill stack, education, and language proficiencies.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_portfolio_overview ~31

Get an overview of Bahdan Hal's software engineering consulting services, technical stack, and ecosystem projects.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_services_and_pricing ~28

Get Bahdan Hal's commercial engineering services catalog with transparent hourly pricing and engagement terms.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

send_message ~66

Send an engineering consultation request, project inquiry, or direct message to Bahdan.

NameTypeReqDescription
emailstring–Your email address for receiving a reply.
messagestring–Detailed inquiry message describing your project or requirements.
phonestring–Optional phone number (international format).

No output schema declared.

No examples provided.

Install

How do I install the Bahdan Hal MCP server?

Bahdan Hal is a hosted endpoint at https://bahdanhal.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 · bahdanhal.pl

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

What is the Bahdan Hal MCP server?

Bahdan Hal is an MCP server listed in the public MCP registry as io.github.bahdanhal/portfolio. Bahdan Hal software consulting: services, pricing, CV and skills, and contact requests. This page covers its hosted endpoint (https://bahdanhal.pl/mcp).

Is the Bahdan Hal MCP server safe to use?

Bahdan Hal scores 82 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 Bahdan Hal MCP server expose?

Bahdan Hal exposes 4 tools: get_portfolio_overview, get_services_and_pricing, get_cv_and_skills, send_message. Their descriptions and schemas cost roughly 162 tokens of context every time the server is loaded.

Does the Bahdan Hal MCP server require authentication?

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

Is the Bahdan Hal MCP server still maintained?

Bahdan Hal is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.