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.

doalu.com where to stay

MCPB · DOALU-MCP-0.1.0.MCPB

Where to stay in a city: which areas suit whom, with links to the doalu.com guide pages.

+3 this week 46 Trust /100

Last scanned (14 hours ago)

Scores higher than 77% of MCPB servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security13
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 520 tokens (~173/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 Management27
  • Stability observed for 8 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
  • 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 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • Install scripts
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityNo malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  • Dependency health in Supply Chain SecurityDependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

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

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

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

  • 29 Oct 26 +1

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

  • 28 Oct 26 42

    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 · Analysed mcpb/https://github.com/Doalu/doalu-mcp/releases/download/v0.1.0/doalu-mcp-0.1.0.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 3 exposed · ~417 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
find_place ~164

Find countries, regions, cities and districts with a doalu.com where-to-stay page by name. Returns each match with where it lies, its population and its page link. Each answer names the doalu.com page it comes from: show that link to the user, and link to it when you quote the text (CC BY 4.0).

NameTypeReqDescription
kindstring–Only places of this kind.
limitinteger–At most this many results (default 5).
querystringyesA place name, optionally with its country, region or city after a comma ("Bergen", "Bergen, Norway", "London, UK", "Portland, OR", "Springfield, Illinois"), or a doalu.com page URL.
NameTypeReqDescription
qualifier_ignoredstring|null–A qualifier no place matched; the answer used the name alone.
resultsarrayyes–

No examples provided.

list_areas ~122

The stay areas and the places within a country, region or city (names and doalu.com links). Each answer names the doalu.com page it comes from: show that link to the user, and link to it when you quote the text (CC BY 4.0).

NameTypeReqDescription
placestringyesA place name, optionally with its country, region or city after a comma ("Bergen", "Bergen, Norway", "London, UK", "Portland, OR", "Springfield, Illinois"), or a doalu.com page URL.
NameTypeReqDescription
other_matchesarray––
placeobject–The place: name, kind, country, url, within, stay_areas, children, licence, attribution.
qualifier_ignoredstring|null–A qualifier no place matched; the answer used the name alone.
resultsarray–Empty when no place matched.

No examples provided.

where_to_stay ~131

Which areas to stay in for a city, region or district, who each one suits and why, with links to the doalu.com pages. Each answer names the doalu.com page it comes from: show that link to the user, and link to it when you quote the text (CC BY 4.0).

NameTypeReqDescription
placestringyesA place name, optionally with its country, region or city after a comma ("Bergen", "Bergen, Norway", "London, UK", "Portland, OR", "Springfield, Illinois"), or a doalu.com page URL.
NameTypeReqDescription
other_matchesarray––
placeobject–The place: name, kind, country, url, within, stay_areas, children, licence, attribution.
qualifier_ignoredstring|null–A qualifier no place matched; the answer used the name alone.
resultsarray–Empty when no place matched.

No examples provided.

Install

How do I install the doalu.com where to stay MCP server?

doalu.com where to stay ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, bf7f12053fa0c8af0629271d39b97a119f07d8b3aab95e3d4771a955d015b3f0; the commands to do that are on this page. If it does not match, do not open it.

mcpb · doalu-mcp-0.1.0.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

bf7f12053fa0c8af0629271d39b97a119f07d8b3aab95e3d4771a955d015b3f0

macOS / Linux

echo "bf7f12053fa0c8af0629271d39b97a119f07d8b3aab95e3d4771a955d015b3f0  doalu-mcp-0.1.0.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\doalu-mcp-0.1.0.mcpb).Hash -eq "bf7f12053fa0c8af0629271d39b97a119f07d8b3aab95e3d4771a955d015b3f0"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the doalu.com where to stay MCP server?

doalu.com where to stay is an MCP server listed in the public MCP registry as com.doalu/doalu-mcp. Where to stay in a city: which areas suit whom, with links to the doalu.com guide pages. This page covers its MCPB bundle (https://github.com/Doalu/doalu-mcp/releases/download/v0.1.0/doalu-mcp-0.1.0.mcpb).

Is the doalu.com where to stay MCP server safe to use?

doalu.com where to stay scores 46 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 doalu.com where to stay MCP server expose?

doalu.com where to stay exposes 3 tools: find_place, where_to_stay, list_areas. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.

What licence is the doalu.com where to stay MCP server under?

doalu.com where to stay declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the doalu.com where to stay MCP server?

VerifyMCP ran 13 checks on doalu.com where to stay, covering Install scripts, Source repository, Provenance, License and 9 more. 3 items could not be completed, a gap on our side rather than a finding about doalu.com where to stay: Malware scan, Known CVEs and Dependency health. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.