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.

Dojazdomat

REMOTE · DOJAZDOMAT.PL

Warsaw commute times and rent medians: rank neighborhoods for an office (transit, bike, walk, car).

Available components

+3 this week 68 Trust /100

Last scanned (8 minutes ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

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 Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1164 tokens (~232/item across 5 items; 5 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 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.

  • 30 Oct 26 0
    • Tool “rent_stats” rewrote its description, which is the text the model reads security
    • “rent_stats” reworded the description of “radius_m” cosmetic
  • 28 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.

  • 27 Oct 26 +7
    • HTTPS: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 57

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dojazdomat.pl CN=YE2,O=Let's Encrypt,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA384 65c4e80bd40fe57856a4c7f8de3ba0d036d
SANs: *.dojazdomat.pl, dojazdomat.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 dojazdomat.pl. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pl. present 2782 8 Verified
dojazdomat.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
strict-transport-security max-age=15552000
content-security-policy frame-ancestors 'self' https://mikolajpawelsapek.eu https://www.mikolajpawelsapek.eu
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), camera=(), microphone=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dojazdomat.pl/mcp Verified 200
http (plaintext) http://dojazdomat.pl/mcp HTTPS enforced 301 https://dojazdomat.pl/mcp
MCP tools · 5 exposed · ~913 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
commute_time ~201

Door-to-door minutes by public transport plus walking, weekday morning 7-9 average, same model as the Dojazdomat map (czas dojazdu komunikacja miejska + pieszo, usredniony dla dni roboczych 7-9). Also lists nearest stops at both ends. minutes is null when the destination is unreachable (over ~2 h).

NameTypeReqDescription
from_latnumberyesLatitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
from_lonnumberyesLongitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
to_latnumberyesLatitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
to_lonnumberyesLongitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)

Structured output declared, but exposes no named fields.

No examples provided.

dataset_info ~35

Data dates, sources, listing counts per portal, method notes and caveats (zrodla, daty, ograniczenia danych).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

find_place ~86

Find transit stop groups and neighborhoods by name and get their lat/lon (znajdz przystanek lub osiedle po nazwie). Use the coordinates as input for the other tools.

NameTypeReqDescription
limitinteger––
querystringyesName fragment, e.g. 'Kabaty', 'Rondo ONZ', 'Mokotow'. Diacritics optional.

Structured output declared, but exposes no named fields.

No examples provided.

rank_neighborhoods ~321

Rank Warsaw neighborhoods for a workplace: median rent, commute minutes, value score (rent vs typical rent in the same commute band, like the map), monthly_cost (rent + commute valued at the minimum wage) and Pareto flag (no neighborhood both faster and cheaper) (ranking osiedli: czynsz, dojazd, wartosc, front Pareto). Same data and rules as the map: neighborhoods with fewer than 20 ads are skipped. Sorted by best (rent + commute cost, the map's order) unless sort is given.

NameTypeReqDescription
limitinteger––
max_commute_min––Max commute minutes
max_rent––Max neighborhood median rent (PLN, or PLN/m2 if measure=per_m2)
measurestring–'total' PLN/month or 'per_m2' PLN/m2/month
office_latnumberyesLatitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
office_lonnumberyesLongitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
rooms––Rooms 1-4 (4 = 4+); omit for any / liczba pokoi
sortstring–best = rent + commute valued at the minimum wage (default, the map's order, total measure only); value = score vs typical rent in the same commute band; commute = fastest first; rent = cheapest first

Structured output declared, but exposes no named fields.

No examples provided.

rent_stats ~270

Asking-rent statistics (n, median, p25, p75) of rental ads within radius_m of a point (statystyki cen najmu w promieniu). Aggregates only; if fewer than 20 ads match, the result is suppressed (widen radius or relax filters). Radius is snapped to a fixed step (see radius_m) so queries cannot be differenced to single ads.

NameTypeReqDescription
latnumberyesLatitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
lonnumberyesLongitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
max_area––Max area m2
measurestring–'total' PLN/month or 'per_m2' PLN/m2/month
min_area––Min area m2
radius_minteger–Radius in metres, 200-5000; snapped to the nearest of 300, 500, 750, 1000, 1500, 2000, 3000, 5000 (the answer states the radius used)
rooms––Rooms 1-4 (4 = 4+); omit for any / liczba pokoi

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Dojazdomat MCP server?

Dojazdomat is a hosted endpoint at https://dojazdomat.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 · dojazdomat.pl

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

What is the Dojazdomat MCP server?

Dojazdomat is an MCP server listed in the public MCP registry as io.github.MikolajSapek/dojazdomat. Warsaw commute times and rent medians: rank neighborhoods for an office (transit, bike, walk, car). This page covers its hosted endpoint (https://dojazdomat.pl/mcp).

Is the Dojazdomat MCP server safe to use?

Dojazdomat scores 68 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 Dojazdomat MCP server expose?

Dojazdomat exposes 5 tools: find_place, commute_time, rent_stats, rank_neighborhoods, dataset_info. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.

Does the Dojazdomat MCP server require authentication?

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

Is the Dojazdomat MCP server still maintained?

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