Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Doorfarer is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Door-to-door trips: every airport within reach of your home, with the train or bus there.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http doorfarer-mcp https://doorfarer.com/mcp
# 2 — ask your agent for something these tools do
# find_trips, price_calendar, trip_details and 1 more
Doorfarer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http doorfarer-mcp https://doorfarer.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Finds the best round trips from where someone lives, not just from one airport: it adds the train or bus to every airport they can reach and ranks all options door to door, by price, by total travel time, or balanced. Use it when someone wants flights from their home town, could fly from several airports, or asks for the cheapest or fastest way to get somewhere, e.g. "I live in New Haven: should I
| Parameter | Type | Required | Notes |
|---|---|---|---|
| home | string | yes | The traveller's home town or village, e.g. "New Haven" or "Hamden, US". Not an airport. Add the country when the name is common. |
| destinations | array | yes | Where to: airport codes (LIS), city codes (NYC), country codes (PT), a region, a continent (Asia), "anywhere" or "abroad" (outside the home country). |
| anywhere | boolean | no | True to find the cheapest places anywhere in the countries or regions named, instead of searching each one's biggest airports. A continent (Asia, Europe), "anywhere" or "abroad" (outside the home coun |
| dates | string | yes | "from_user" whenever the user named any time at all (a month, season, holiday, "next week"); "assumed" only when they named none and you picked dates or left them out. |
| depart_from | no | The window to leave in: first day. Leave out with depart_to for the next 3 months. A window of about six months at most, within the next year. | |
| depart_to | no | The window to leave in: last day. A window of about six months at most, within the next year. | |
| nights_min | no | Trip length in nights: shortest. Default 2. | |
| nights_max | no | Trip length in nights: longest. Default 14. | |
| travellers | integer | no | Adults travelling together. Default 1. |
| priority | string | no | What matters most: budget (the cheapest door to door), time (the fastest) or balanced. Default balanced; the picks show the cheapest, the fastest and the balanced trip either way. |
| from_airports | no | Only these departure airports. For narrowing a previous answer. | |
| one_way | boolean | no | True if the user wants one way only: then the trip length is ignored. |
| mode | no | How the user gets to the airport: public (train or bus), train, bus, car (their own, parked at the airport), or any (car, taxi and public compete). Leave out unless the user says: then any for a home | |
| currency | no | ISO code (USD, GBP, EUR) to show prices in. Default: the traveller's home currency. | |
| max_ground_hours | no | The most hours from the front door to the departure airport, one way. Default 8.5: farther airports are left out and named in the answer. Set it only when the user says how far they would travel to th | |
| limit | no | Rows to return, 1-25. Default: the picks plus the best trip from each airport. |
Shows the cheapest month to travel from someone's home town to a place, for each airport within reach: the cheapest fare found for each month (or, where none is found, what that route usually costs) plus the train or bus to the airport and the transfer into the city. Takes a few seconds. Airports further than 8.5 hours from home are left out and named. Use it when the user's dates are flexible or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| home | string | yes | The traveller's home town or village, e.g. "New Haven" or "Hamden, US". Not an airport. Add the country when the name is common. |
| destinations | array | yes | Where to: airport codes (LIS), city codes (NYC) or country codes (PT). |
| month_from | no | First month, "2027-03". Default: this month. | |
| month_to | no | Last month. Default: 6 months in all. | |
| one_way | boolean | no | True for one-way fares. |
| currency | no | ISO code (USD, GBP, EUR). Default: the home's. |
Shows one trip from a find_trips answer step by step, door to door: leaving home, the train or bus to the airport, the airport wait, the flight, the transfer into the city and arrival, then the way back, with local times. Also gives the booking link and a calendar file (.ics) the user can add. Pass a trip id from the find_trips answer ("Trip ids, row by row", or a row's id). Use it when the user
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trip_id | string | yes | A trip id from the find_trips answer, e.g. "t_k3m9q2xa". |
Tell Doorfarer's maker where Doorfarer fell short, so it can be fixed. Use it when a find_trips answer was wrong, confusing, or missing something you needed to help, or when the user asks you to pass something on. Write as the assistant that used the tool: what you asked for, what came back, what you expected instead. The report is about Doorfarer only, never about the user: leave out names, conta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | bug: something is wrong. confusing: right but hard to use. idea: something that would help. |
| what_happened | string | yes | What you asked for, what came back and what you expected. About Doorfarer, not the user. At most 600 characters. |
| suggestion | no | What would have helped. At most 400 characters. | |
| search_id | no | The id from the find_trips answer this is about, e.g. "s_7f3kq2m9xa". |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Doorfarer or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| find_trips | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| price_calendar | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| trip_details | no tags | |
| send_feedback | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Doorfarer can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.