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.

Journeyed: Los Angeles hotel facts

REMOTE · JOURNEYED.ORG

Los Angeles hotel facts with sources: parking prices, fees, pets, check-in, pools, distances.

Available components

+3 this week 82 Trust /100

Last scanned (19 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 4 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 Security80
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1612 tokens (~230/item across 7 items; 7 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 Management73
  • Stability observed for 22 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 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
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.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

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

  • 25 Oct 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.

  • 23 Oct 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.

  • 21 Oct 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.

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

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://journeyed.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=journeyed.org CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 fe6ad907152a294f138da1782d1496ca
SANs: journeyed.org, www.journeyed.org, *.www.journeyed.org
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 journeyed.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
journeyed.org. 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 'none'; img-src 'self' data: https://i.ytimg.com https://*.cdninstagram.com https://*.fbcdn.net; style-src 'self' 'unsafe-inline'; font-src 'self'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://journeyed.org/mcp Verified 200
http (plaintext) http://journeyed.org/mcp HTTPS enforced 301 https://journeyed.org/mcp
MCP tools · 7 exposed · ~1,319 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
answer_question ~174

Route a plain-language question about Los Angeles area hotels to the Journeyed page that answers it, with the same matcher journeyed.org/ask uses. For a question about one named hotel ("What time is check-in at Santa Monica Proper Hotel?") it returns the hotel's sourced answer with the source URL and checked date. For a question about a place ("Which hotels near LAX have a free shuttle?") it returns the page's direct answer, its top hotels and the page URL. It only returns what a published page states. When nothing matches, matched is false, no answer is returned and the closest pages are listed. It cannot answer about room prices, availability or guest reviews.

NameTypeReqDescription
questionstringyesThe question in plain words, naming the hotel or the place. Example: "Does The Anthem have parking?"
NameTypeReqDescription
alsoAnsweredarray–Other close published answers about the same hotel.
answerstring|null––
asOfstring|null––
closestarray–When matched is false: the nearest published pages. They may not answer the question.
hotel–––
kindstringyes–
matchedbooleanyesTrue only when a published page answers the question.
notestring|null––
noticesarrayyesLimits that apply to this question (for example: no room prices).
questionstring|null–The published question that matched (compare it with what was asked).
source–––
toparray––
totalnumber|null––
urlstring|null–The journeyed.org page to cite.

No examples provided.

best_hotels ~226

The published Journeyed best-of list for a Los Angeles place ("best hotels near SoFi Stadium", "best hotels in Santa Monica") or for a need across Los Angeles (pet friendly, pool, kitchen). Returns the ranked hotels with the points each earned and the sourced reasons why (awards, hotel class, verified facts, distance), plus the published formula. "Best" means first by that formula, built from checkable facts: no guest reviews, no prices, and no hotel can pay to be listed. Give place or need (at least one).

NameTypeReqDescription
limitinteger–How many hotels to return (1 to 10, default 5). The result gives the URL of the full list.
needstring–Optional. A need with a market-wide best-of list: pet friendly, pool, kitchen.
placestring–Optional. A Los Angeles area landmark, venue, airport or neighborhood by name, for example "SoFi Stadium", "LAX", "Disneyland", "Santa Monica". list_places gives every place covered.
NameTypeReqDescription
availablearray–When found is false: the best-of lists that exist.
considerednumber|null––
eligibilitystring|null––
eligiblenumber|null––
foundbooleanyes–
hotelsarray––
methodobject–The published formula behind the ranking.
notestring|null––
pageobject–The published journeyed.org page the rows come from. Cite url.
sourcesarray––
suggestionsarray––
totalinteger––

No examples provided.

get_hotel ~173

The fact sheet Journeyed holds for one Los Angeles area hotel: every verified fact (parking and its price, fees, pet rules, check-in and checkout times, pool, breakfast, accessibility and more) with its source URL and checked date, the Journeyed Score and what backs it, hotel class and awards, former names, straight-line, walking and driving distances to nearby landmarks, and the list of facts Journeyed does not know. Use it for any question about a named hotel. A fact listed under unknown is not on record at Journeyed, which is different from the hotel not offering it. It holds no reviews, room prices or availability.

NameTypeReqDescription
hotelstringyesHotel name (current or former), or its journeyed.org page URL. Examples: "The Anthem", "Santa Monica Proper Hotel".
NameTypeReqDescription
addressstring|null––
asOfstring––
bestOfarray––
candidatesarray–When found is false: the closest hotel names. Call again with one of them.
contactSource–––
distanceNotestring|null––
distanceSource–––
factsarray––
factsTotalinteger––
formerNamesarray––
foundbooleanyes–
marketstring|null––
namestring––
nameSource–––
nearbyarray––
notestring|null––
phonestring|null––
questionsarray––
recognitionarray–Hotel class and recognized awards (AAA, Forbes Travel Guide, MICHELIN Keys), each with its source.
scoreobject–The Journeyed Score (0 to 100) measures how much about the hotel is verified, not how good it is. backedBy says what it rests on.
sourcesarray––
unknownarray–Fact keys Journeyed has no verified value for at this hotel. Unknown, not "no".
unknownTotalinteger––
urlstring–The journeyed.org page to cite.
websitestring|null––

No examples provided.

get_report ~156

A Journeyed data report about Los Angeles area hotels as a whole: parking (how many hotels state a price, how many are free, typical charges by area), resort fees, pet policies, check-in and checkout times, hotels near stadiums and arenas, and what hotel websites leave out. Returns the headline numbers with their sample sizes, the main findings, the first rows of each table, the method caveats, the page URL and the CSV link. Use it for market-wide statistics, not for one hotel. Call it with no topic to list the reports.

NameTypeReqDescription
topicstring–Report topic: parking, resort fees, pets, check-in times, venues, what websites leave out. Leave out to list the reports.
NameTypeReqDescription
availablearray––
citestring|null––
csvUrlstring|null––
dataCheckedOnstring|null––
findingsarray––
foundbooleanyes–
headlinestring|null––
licensestring|null––
methodarray–Method and caveats. Read them before quoting a number.
methodologyUrlstring|null––
notestring|null––
publishedstring|null––
sampleobject|null–Sample sizes: hotels in the market, hotels with a website, sites read, hotels stating the fact.
statsarray––
summarystring|null––
tablesarray––
titlestring––
urlstring–The report page to cite.

No examples provided.

hotels_near ~255

Ranked hotels near a Los Angeles landmark, venue, airport or neighborhood, optionally for one need (parking, free parking, pets, pool, airport shuttle, breakfast, accessible rooms, EV charging, kitchens, an early flight, or walking distance). Each hotel comes with its straight-line distance, walking minutes and driving distance where held, and the sourced facts that answer the need (for example the stated parking price) with source URL and checked date. The list is the published journeyed.org page for that place and need. If no page covers the need there, the result says so and lists the needs that are covered.

NameTypeReqDescription
limitinteger–How many hotels to return (1 to 10, default 5). The result gives the URL of the full list.
needstring–Optional. What the traveler needs, in plain words: parking, free parking, pets, pool, airport shuttle, breakfast, accessible rooms, EV charging, kitchen, early flight, walking distance.
placestringyesA Los Angeles area landmark, venue, airport or neighborhood by name, for example "SoFi Stadium", "LAX", "Disneyland", "Santa Monica". list_places gives every place covered.
NameTypeReqDescription
foundbooleanyes–
hotelsarray––
methodobject––
needobject|null––
needsCoveredarray–Needs that have a published page at this place.
notestring|null––
pageobject–The published journeyed.org page the rows come from. Cite url.
placeobject––
relatedarray––
sourcesarray––
suggestionsarray––
totalinteger–Hotels on the full list at page.url.

No examples provided.

list_places ~118

The Los Angeles area landmarks, venues, airports, attractions and neighborhoods Journeyed has hotel lists for, with each one's page URL, and the needs (parking, pets, pool and so on) it can filter by. Use it to check that a place is covered, or to find the exact name to pass to hotels_near or best_hotels. Optionally filter by kind.

NameTypeReqDescription
kindstring–Optional. One kind of place: airport, venue, convention, attraction, beach, campus, hospital, transit, employer, area.
NameTypeReqDescription
asOfstringyes–
kindsarray––
marketstringyes–
needsarrayyes–
placesarrayyes–
sourceobjectyes–
totalintegeryes–

No examples provided.

search_hotels ~217

Find hotels in the Los Angeles area by name, former name, brand or city, optionally only those within a few miles of a place. Returns each hotel's name, city and journeyed.org page URL. Use it to get the exact hotel before get_hotel, or to list a brand's hotels near a place. It matches names only: for a need such as parking or pets use hotels_near.

NameTypeReqDescription
limitinteger–How many hotels to return (1 to 10, default 5). The result gives the URL of the full list.
nearstring–Optional. Only hotels within a few miles of this place. A Los Angeles area landmark, venue, airport or neighborhood by name, for example "SoFi Stadium", "LAX", "Disneyland", "Santa Monica". list_plac…
querystringyesHotel name, former name or brand, with a city if you have one. Examples: "The Anthem", "Marriott", "Hilton Anaheim".
NameTypeReqDescription
asOfstringyes–
hotelsarrayyes–
nearobject|nullyes–
notestring|null––
querystringyes–
sourceobjectyes–
totalintegeryesHow many hotels matched; hotels[] holds the first `limit`.

No examples provided.

Install

How do I install the Journeyed: Los Angeles hotel facts MCP server?

Journeyed: Los Angeles hotel facts is a hosted endpoint at https://journeyed.org/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 · journeyed.org

# add to Claude Code
claude mcp add --transport http org-journeyed-hotels 'https://journeyed.org/mcp'
Common questions

What is the Journeyed: Los Angeles hotel facts MCP server?

Journeyed: Los Angeles hotel facts is an MCP server listed in the public MCP registry as org.journeyed/hotels. Los Angeles hotel facts with sources: parking prices, fees, pets, check-in, pools, distances. This page covers its hosted endpoint (https://journeyed.org/mcp).

Is the Journeyed: Los Angeles hotel facts MCP server safe to use?

Journeyed: Los Angeles hotel facts 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 Journeyed: Los Angeles hotel facts MCP server expose?

Journeyed: Los Angeles hotel facts exposes 7 tools: answer_question, get_hotel, search_hotels, hotels_near, best_hotels, and 2 more. Their descriptions and schemas cost roughly 1,319 tokens of context every time the server is loaded.

Does the Journeyed: Los Angeles hotel facts MCP server require authentication?

No. We connected to Journeyed: Los Angeles hotel facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Journeyed: Los Angeles hotel facts MCP server still maintained?

Journeyed: Los Angeles hotel facts 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.