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.

Mahonia

REMOTE · MAHONIA.APP

Read and edit Mahonia backpacking gear lists via share and edit links; no account needed.

Available components

−9 this week 69 Trust /100

Last scanned (11 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Productivity and Notes

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 Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2493 tokens (~415/item across 6 items; 6 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 Management43
  • Stability check failed: schema churn in the 30 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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.

  • 1 Nov 26 −9
    • Stability: pass → fail ▼ security
    • Tool “add_items” was removed ▼ security
    • Tool “get_catalog_product” was removed ▼ security
    • Tool “get_list_markdown” was removed ▼ security
    • Tool “set_trip” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “edit_list”, which the server declares destructive security
    • New tool “edit_my_gear”, which the server declares destructive security
    • Tool “create_list” rewrote its description, which is the text the model reads security
    • Tool “get_list” rewrote its description, which is the text the model reads security
    • Tool “search_catalog” rewrote its description, which is the text the model reads security
    • Schema quality: 183 → 415 ▼ functional
    • Tool coverage: 86% → 100% ▲ functional
    • Tool coverage: 79% → 94% ▲ functional
    • Server version: 1.0.0 → 2.0.0 functional
    • New tool “get_my_gear” functional
    • “get_list” added an optional parameter “format” cosmetic
    • “search_catalog” added an optional parameter “brand” cosmetic
    • “search_catalog” added an optional parameter “name” cosmetic
    • “search_catalog” added an optional parameter “product_id” cosmetic
    • “get_list” reworded the description of “share_code” cosmetic
    • “search_catalog” reworded the description of “limit” cosmetic
    • “search_catalog” reworded the description of “query” cosmetic
    • “get_list” made “share_code” optional cosmetic
    • “search_catalog” made “query” optional cosmetic
    • Tool “get_list” changed its title: Read a shared list → Read a list cosmetic
  • 12 Oct 26 +1
    • Stability: 0.93 → pass security
  • 10 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 93. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.

  • 4 Oct 26 +1

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

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_list” rewrote its description, which is the text the model reads security
    • Tool “get_list_markdown” rewrote its description, which is the text the model reads security
    • Schema quality: 157 → 182 ▼ functional
    • Tool coverage: 74% → 79% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “add_items” now declares an output schema ▲ functional
    • Tool “create_list” now declares an output schema ▲ functional
    • Tool “get_catalog_product” now declares an output schema ▲ functional
    • Tool “get_list” now declares an output schema ▲ functional
    • Tool “search_catalog” now declares an output schema ▲ functional
    • Tool “set_trip” now declares an output schema ▲ functional
    • First check of Tool coverage: 86 functional
    • “add_items” added an optional parameter “again” cosmetic
    • “create_list” reworded the description of “unit” cosmetic
    • “set_trip” reworded the description of “unit” cosmetic
  • 12 Sept 26 0

    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://mahonia.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mahonia.app CN=YR1,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 6b466ea7a7300aac2af6af475e7aafaf781
SANs: mahonia.app
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mahonia.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
mahonia.app. 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=63072000
content-security-policy default-src 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data: blob: https://tile.opentopomap.org; font-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; connect-src 'self'; worker-src 'self' blob:; manifest-src 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mahonia.app/mcp Verified 200
http (plaintext) http://mahonia.app/mcp HTTPS enforced 308 https://mahonia.app/mcp
MCP tools · 6 exposed · ~1,870 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
create_list ~270

Creates a list and returns its edit link and share link. Optionally with a title, unit, trip dates, a trail link and rows, grouped into folders; a row with items nested under it is a group (stakes under a tent, snacks under a day). Keep the edit link: it is the only way to change a list that isn't filed under an account. If this connector carries a read-and-write access token the list is filed under that account too, and saved_to_account says whether it was; otherwise the list belongs to whoever holds the edit link, as every list does.

NameTypeReqDescription
end_datestring–YYYY-MM-DD
foldersarray–Folders in order, each with its default classification and, optionally, its rows.
itemsarray–Rows not placed through a folder above; each may name its folder.
start_datestring–YYYY-MM-DD
titlestring––
trail_distance_kmnumber––
trail_labelstring–What to call the trail, when the link's own name won't do.
trail_urlstring–An http(s) link to the route or trail page.
unitstring–The unit the list displays in. Weights are in grams regardless.
NameTypeReqDescription
account_notestring–Only when the connector sent an access token and the list still could not be filed under its account: the reason, and what to do instead.
edit_linkstringyesThe write capability. Keep it; it is the only way to change a list that isn't filed under an account.
foldersintegeryesFolders made.
itemsintegeryesRows made.
saved_to_accountbooleanyesTrue when the connector's read-and-write access token filed the list under its account, where the owner sees it on every device they sign in on.
share_codestringyes–
share_linkstringyesThe read capability, safe to pass on.
titlestringyesUser text.
totalsobjectyesWhole grams, summed over every row of the list.

No examples provided.

edit_list ~488

Changes a list that already exists, all of it in one call. list sets the list's own title, display unit, trip dates and trail (only the fields given; an empty string clears a date or the trail). folders renames, reorders, reclassifies or removes folders, named by id or current name; removing one removes its rows. add puts new rows on, into a folder by name (made when missing) or under a group by the parent row's id. update changes rows by the ids get_list gives: any field, null clearing one that can be cleared; a new folder, place or group; a catalog_id to link or relink the row where it sits, null to unlink. remove takes rows off by id, a group's nested rows with it. The parts apply in that order as one change, and nothing is applied unless every part is valid: a row or folder named that isn't there fails the whole call. A name or weight changed on a catalog-linked row is kept as the owner's own. Takes the list's edit link, or its share code under a signed-in account that has filed it.

NameTypeReqDescription
addarray–New rows. Each may name its folder, or the group to join.
againboolean–A call with rows to add that is identical to one made in the last ten minutes is taken as a retry and does nothing: the earlier result comes back with repeated set. Pass true to make the same change…
edit_linkstring–The list's edit link, whole (mahonia.app/e/CODE#token). The part after # is the write capability. Leave it out to name a list filed under the signed-in account by share_code instead.
foldersarray–Changes to folders that exist.
listobject–The list's own fields. Only the fields given change.
removearray–Ids of rows to take off, from get_list.
share_codestring–Instead of the edit link: the share code or share link of a list filed under the connector's account, as get_list with no share_code gives it. Takes a sign-in with read-and-change access, and reaches…
updatearray–Changes to rows that exist, each by id.
NameTypeReqDescription
addedintegeryesRows added, nested ones counted.
datesobject|nullyes–
foldersarrayyesEvery folder's name, in the list's order, after the change.
folders_changedintegeryesFolders renamed, reordered, reclassified or removed.
folders_madearrayyesFolders that didn't exist and were made for rows named into them.
removedintegeryesRows taken off: by remove, with a removed group, or with a removed folder.
repeatedbooleanyesTrue when this call, with rows to add, repeated one made in the last ten minutes: nothing was done again, and the figures are that call's. Pass again: true to do it a second time.
share_linkstringyes–
titlestringyesUser text.
totalsobjectyesWhole grams, summed over every row of the list.
trailobject|nullyes–
unitstringyesThe unit the list displays in. Weights are in grams regardless.
updatedintegeryesRows changed, moved or regrouped.

No examples provided.

edit_my_gear ~252

Changes the connector's account's My Gear, in one call. add puts new pieces in; one the account already holds (same brand, name and variant) comes back as already_have and is left as it was. update changes pieces by the ids get_my_gear gives, only the fields sent, null clearing one. A piece that names a catalog_id, as it is added or later, is linked to that catalog row and takes its brand, name, variant, gear type and weight where none were given; null unlinks it. remove puts pieces away by id: they stop being offered on lists, and the lists that still carry them will not bring them back. restore brings put-away pieces back. Each piece answers for itself, in the order sent. What is added or changed here counts as the owner's own word on the piece, so a list saved later cannot overwrite it. Needs a read-and-change access token.

NameTypeReqDescription
addarray–New pieces.
removearray–Ids of pieces to put away.
restorearray–Ids of put-away pieces to bring back.
updatearray–Changes to pieces that exist, each by id.
NameTypeReqDescription
addedintegeryesPieces that were new to My Gear.
removedarrayyesOne per id in remove, then one per id in restore, in the order sent.
resultsarrayyesOne per piece in add, in the order sent.
updatedarrayyesOne per entry in update, in the order sent.

No examples provided.

get_list ~427

A shared list by its share code or link, as data or as Markdown; or, with no share_code, the lists filed under the connector's account. Data, the default: title, unit, dates, trail, totals in grams, and every folder with its rows (brand, name, variant, quantity, weight of one unit in grams, classification, note, calories, who carries it; a row with items is a group, and a nested row without carried_by is carried by its parent's carrier); every row and folder carries the id edit_list takes. Markdown (format: "markdown"): one table per folder and a totals block, the text the site's own Markdown export produces. An edit link's address carries the share code too. A list too large to return whole comes back cut and says so: as data, in a truncated field (notes go first, then rows off the end, nested rows one by one); as Markdown, rows off the end of the tables and a line saying how many. The totals still count every row. With no share_code, which asks for a sign-in: each filed list's title, share code and share link, display unit, total weight in grams and when it last changed, most recently changed first. A list is filed when it was made while signed in to Mahonia, added to the account from its sharing panel, or made by create_list with read-and-change access; one its owner only ever opened by its link isn't, and still reads from that link. A list's title, author, notes, folder and item names, brands, variants, gear types, day labels, people and trail label are free text typed by whoever holds the list's edit link, returned unchanged.

NameTypeReqDescription
formatstring–data (the default) or markdown. Only with a share_code.
share_codestring–The list's share code, its share link (mahonia.app/s/CODE), or its edit link. From an edit link only the code in the address is read, never the part after #.

Structured output declared, but exposes no named fields.

No examples provided.

get_my_gear ~203

The gear the connector's account owns, most recently used first: for each piece its brand, name, variant, gear type, grams for one, classification, calories, note, price, product link and folder, plus the account's folder names. A query ranks by a search instead; a folder name keeps to that folder. Works only when this connector carries the account's access token. Brands, names, variants, gear types, notes and folder names are text the account holder typed, returned unchanged.

NameTypeReqDescription
folderstring–Keep to one folder, by name. An empty string means the unfiled pieces.
limitinteger–At most 1000; 300 when omitted.
offsetinteger–How many matches to skip, for the next page.
querystring–Two characters or more (one is enough in Chinese). Ranks by brand, name, variant and gear type instead of by recent use.
NameTypeReqDescription
foldersarrayyesEvery folder My Gear has, in the owner's order, empty ones included.
geararrayyesThis page of the matches.
offsetintegeryes–
totalintegeryesMatches in all, before offset and limit.

No examples provided.

search_catalog ~230

Mahonia's cited gear catalog. With query: a fuzzy search by brand, product or kind of gear ("duplex", "zpacks", "quilt"), best first, each result a catalog row with its id, the cited weight in grams and whether it is verified. With product_id (a row id from a search), or brand and name: every variant of that one product (sizes, lengths, temperature ratings) with the weight and source of each. A row on a list that names a catalog_id takes the catalog's brand, variant, gear type and weight.

NameTypeReqDescription
brandstring–With name, instead of a query: the product's maker.
limitinteger–Matches to return, up to 25. Default 12.
namestring–With brand, instead of a query: the product name without brand or variant.
product_idinteger–Instead of a query: a catalog row id, for that product's variants.
querystring–What to search for: two characters or more, or a single Chinese character.
NameTypeReqDescription
productobject–The product looked up, when one was.
querystring–The query as searched: trimmed, at most 100 characters. On a search.
resultsarrayyesA search's matches, best first; or a product's variants, in variant order.

No examples provided.

Install

How do I install the Mahonia MCP server?

Mahonia is a hosted endpoint at https://mahonia.app/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 · mahonia.app

# add to Claude Code
claude mcp add --transport http app-mahonia-mahonia 'https://mahonia.app/mcp'
Common questions

What is the Mahonia MCP server?

Mahonia is an MCP server listed in the public MCP registry as app.mahonia/mahonia. Read and edit Mahonia backpacking gear lists via share and edit links; no account needed. This page covers its hosted endpoint (https://mahonia.app/mcp).

Is the Mahonia MCP server safe to use?

Mahonia scores 69 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 Mahonia MCP server expose?

Mahonia exposes 6 tools: get_list, search_catalog, create_list, edit_list, get_my_gear, edit_my_gear. Their descriptions and schemas cost roughly 1,870 tokens of context every time the server is loaded.

Does the Mahonia MCP server require authentication?

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

Is the Mahonia MCP server still maintained?

Mahonia 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.