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.

EverList Hub

REMOTE · EVERLIST.NETWORK

Listing-first agent commerce: search, book, and settle dated listings in Midnight escrow. 21 tools.

Available components

+6 this week 68 Trust /100

Last scanned (21 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2181 tokens (~103/item across 21 items; 21 tools + 0 resources), lean.Pass
  • 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 Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_from_cart" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

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

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

  • 16 Nov 26 +1

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

  • 15 Nov 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “everlist_book” rewrote its description, which is the text the model reads security
    • Tool “everlist_booking” rewrote its description, which is the text the model reads security
    • Tool “everlist_listing” rewrote its description, which is the text the model reads security
    • Tool “everlist_search” rewrote its description, which is the text the model reads security
    • Schema quality: 88 → 103 ▼ functional
    • Schema quality: 88 → 97 ▼ functional
    • Tool coverage: 37% → 97% ▲ functional
    • Tool coverage: 37% → 96% ▲ functional
    • Destructive annotations: pass → 0 functional
    • New tool “everlist_bookings” functional
    • New tool “everlist_cancel” functional
    • New tool “everlist_confirm” functional
    • New tool “everlist_dispute” functional
    • New tool “everlist_escrow_proof” functional
    • New tool “everlist_rate” functional
    • New tool “add_to_cart” functional
    • New tool “checkout” functional
    • New tool “get_cart” functional
    • New tool “get_order_status” functional
    • New tool “get_product_details” functional
    • New tool “remove_from_cart” functional
    • New tool “search_policies” functional
    • New tool “search_products” functional
    • New tool “update_cart_item” functional
    • “everlist_book” reworded the description of “attendee” cosmetic
    • “everlist_book” reworded the description of “buyer” cosmetic
    • “everlist_book” reworded the description of “client” cosmetic
    • “everlist_book” reworded the description of “human_verified” cosmetic
    • “everlist_book” reworded the description of “idempotency_key” cosmetic
    • “everlist_book” reworded the description of “listing_id” cosmetic
    • “everlist_book” reworded the description of “quantity” cosmetic
    • “everlist_book” reworded the description of “worker” cosmetic
    • “everlist_booking” reworded the description of “booking_id” cosmetic
    • “everlist_search” reworded the description of “category” cosmetic
    • “everlist_search” reworded the description of “from” cosmetic
    • “everlist_search” reworded the description of “max_price” cosmetic
    • “everlist_search” reworded the description of “min_price” cosmetic
    • “everlist_search” reworded the description of “to” cosmetic
  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 62

    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 21 Nov 2026 · Probed https://everlist.network/mcp

TLS valid

Negotiated TLS 1.3 with TLS_CHACHA20_POLY1305_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=everlist.network CN=YE1,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 513ac8749e63bfc5110d24bdad1eba8bc94
SANs: everlist.network
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 secure

Validation of everlist.network. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
network. DS published 11416 8 Verified
everlist.network. DS published 51402 13 Verified
everlist.network. Verified address RRset verified with the apex keys
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
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://everlist.network/mcp Verified 200
http (plaintext) http://everlist.network/mcp HTTPS enforced 308 https://everlist.network/mcp
MCP tools · 21 exposed · ~2,052 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
add_to_cart ~80

Stage one listing in the session draft (replaces any previous draft: EverList books one listing per booking). Does NOT book. Follow with checkout when the customer is ready.

NameTypeReqDescription
product_idstringyeslisting id from search_products, e.g. even-1
quantityinteger–seats/units (capped at 12)

No output schema declared.

No examples provided.

checkout ~53

Stage the hosted booking page for the draft. Returns checkout_url for the customer to open; the rail label states exactly how money moves (or that it is a free/demo booking). No order is placed and no money moves here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

everlist_book ~265

CREATE a booking (or apply+pay for jobs) holding funds in Midnight-blockchain escrow; read status afterward with everlist_booking. Requires a hub token in the X-Hub-Token header on the MCP request (header-only auth; obtain via the hub auth contract: POST /accounts/signup + /accounts/login, keypair stays client-side). human_verified must be true (interim credential; production = zk-personhood). Booking fields depend on the vertical (attendee / buyer+quantity / client / worker).

NameTypeReqDescription
attendeestring–events vertical: attendee identity ref
buyerstring–food/p2p vertical: buyer identity ref
clientstring–services vertical: client identity ref
human_verifiedboolean–must be true: interim human-attestation (production = zk-personhood)
idempotency_keystring–optional client key: retry-safe booking (same key = same booking, never a duplicate)
listing_idstringyeslisting id from everlist_search/everlist_listing, e.g. even-1
quantityinteger–seats/units to book (capacity verticals)
workerstring–jobs vertical: worker identity ref (the human who takes the job)

No output schema declared.

No examples provided.

everlist_booking ~106

READ the status of ONE booking you created: escrow state (HELD/RELEASED/REFUNDED/...), amount, confirmation code. Naming: everlist_book CREATES, everlist_booking READS - booking_id comes from the everlist_book response. Auth: same X-Hub-Token header as everlist_book. Storefront twin: get_order_status.

NameTypeReqDescription
booking_idstringyesbooking id from the everlist_book response, e.g. bk-...

No output schema declared.

No examples provided.

everlist_bookings ~70

LIST YOUR bookings: every booking made with your principal, with escrow state, amount and listing. Use it to find booking_ids before everlist_booking / everlist_cancel. Auth: your usual X-Hub-Token header (book or list token). Principal-scoped: you see only your own.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

everlist_cancel ~113

CANCEL a booking before fulfillment: full refund out of escrow (escrow flips to REFUNDED). Works while escrow is HELD and inside the listing refund window (free/WAIVED bookings cancel too; instant-rail DIRECT bookings have no refund window). Auth for THIS call: THIS booking's cancel_token as the X-Hub-Token header. The chain claim deadline is authoritative - past it only the contract auto-release applies.

NameTypeReqDescription
booking_idstringyesbooking id to cancel, e.g. bk-...

No output schema declared.

No examples provided.

everlist_confirm ~110

ORGANIZER action: confirm fulfillment - escrow RELEASES to the organizer (owner_received reports the payout; free/WAIVED bookings confirm too and no money moves). Buyers correctly get a 403 - fulfillment belongs to the listing owner. Auth: your organizer list token as the X-Hub-Token header (or an admin confirm token). Instant-rail (DIRECT) bookings settled at booking and have nothing to confirm.

NameTypeReqDescription
booking_idstringyesbooking id to confirm, e.g. bk-...

No output schema declared.

No examples provided.

everlist_contract ~37

Discovery: the EverList hub manifest - payment mode, fee policy, identity requirements, verticals, and endpoint map. Call this first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

everlist_dispute ~116

FREEZE a HELD booking for arbitration (DISPUTED): no release and no refund while frozen; if the arbiter vanishes, arbiterTimeoutRefund returns buyer funds after the deadline. Buyer side via MCP: your cancel_token (or book token) as the X-Hub-Token header. Organizer side stays on REST (manage_code never belongs in tool arguments - MCP-ARGS law). Only HELD bookings can be disputed.

NameTypeReqDescription
booking_idstringyesbooking id to freeze, e.g. bk-...

No output schema declared.

No examples provided.

everlist_escrow_proof ~134

VERIFY-WITHOUT-TRUST: read the escrow straight from the Midnight indexer (dual-source when configured, fail-closed) and get the raw chain projection + verification metadata. No booking details, no identities - only what the chain itself says. Public: no token needed. escrow_id and contract come from a booking escrow_ref (everlist_booking / get_order_status responses) or the /verify link.

NameTypeReqDescription
contractstring–escrow contract address (optional when the hub has HUB_ESCROW_CONTRACT configured)
escrow_idintegeryeschain escrow id from the booking escrow_ref

No output schema declared.

No examples provided.

everlist_listing ~87

Fetch ONE full listing record by id: title, description, date/time, location, price, escrow payment terms (rail + refund window), capacity and spots left, rating. Use after everlist_search to inspect before everlist_book. Storefront twin: get_product_details (same handler).

NameTypeReqDescription
idstringyeslisting id, e.g. even-1 or jobs-1

No output schema declared.

No examples provided.

everlist_rate ~104

RATE a settled booking 1-5 (once, buyer-only, owner-immutable). Opens after settlement (escrow RELEASED / WAIVED / DIRECT). Paid reviews are amount-weighted, self-reviews rejected; ratings touch no ledger entries. Auth: your book token as the X-Hub-Token header.

NameTypeReqDescription
booking_idstringyesyour settled booking id, e.g. bk-...
ratingintegeryes1-5 (integer)

No output schema declared.

No examples provided.

everlist_search ~254

Search the public EverList catalog of bookable listings (events, classes, food, services, jobs, p2p). Free-text q plus optional filters: vertical, category, tags (comma-separated), date window from/to (YYYY-MM-DD), min_price/max_price, sort (date|price|newest). Returns matches with id, title, date, location, price, spots left. Next step: everlist_listing for one full record, then everlist_book. Storefront twin: search_products (same handler, Claude commerce contract name).

NameTypeReqDescription
categorystring–vertical-specific category (see everlist_verticals)
fromstring–window start, YYYY-MM-DD (inclusive)
max_pricenumber–maximum price in major units
min_pricenumber–minimum price in major units (0 = free included)
qstring–free-text query
sortstring–date | price | newest (invalid values are rejected)
tagsstring–comma-separated tags
tostring–window end, YYYY-MM-DD (inclusive)
verticalstring–events|food|services|jobs|classes|p2p

No output schema declared.

No examples provided.

everlist_verticals ~41

Vertical schema registry: required/optional fields, categories, and booking shape per vertical (events, food, services, jobs, classes, p2p).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_cart ~57

The session draft (at most ONE staged listing). Nothing is booked and no money has moved until the hosted checkout page is completed. Pair: add_to_cart stages, update_cart_item edits quantity, remove_from_cart empties, checkout hands off.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_order_status ~89

Storefront-contract alias of everlist_booking (same handler): booking and escrow state for the token holder (X-Hub-Token header), including the wallet-less verify URL when an escrow reference exists. Create a booking via everlist_book or the cart flow (add_to_cart -> checkout).

NameTypeReqDescription
booking_idstringyesbooking id from the booking/checkout response, e.g. bk-...

No output schema declared.

No examples provided.

get_product_details ~72

Storefront-contract alias of everlist_listing (same handler): one listing in full - description, date/time, place, price, capacity left, escrow terms (rail + refund window). Inspect before add_to_cart.

NameTypeReqDescription
product_idstringyeslisting id from search_products, e.g. even-1

No output schema declared.

No examples provided.

remove_from_cart ~43

Empty the session draft cart (EverList drafts hold at most one listing). Nothing is booked and no money has moved; add_to_cart can stage a different listing afterward.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_policies ~50

Hub commerce policies: fee policy, payment mode, escrow and refund rules; optionally one listing's terms via listing_id (e.g. refund window before you book).

NameTypeReqDescription
listing_idstring––

No output schema declared.

No examples provided.

search_products ~91

Search EverList listings (events, classes, food, services, jobs, p2p). Returns best matches with price, date, location, and spots left. Storefront-contract alias of everlist_search (same handler) - use whichever family your manifest enabled.

NameTypeReqDescription
limitinteger–max matches to return
querystringyesfree-text search, e.g. "yoga class Vienna"

No output schema declared.

No examples provided.

update_cart_item ~80

Change the quantity (1-12) of the staged draft item. EverList carts hold exactly ONE listing, so quantity is the only editable field; get_cart shows the draft. Session-local (TTL 1h) - nothing is booked and no money moves until checkout completes.

NameTypeReqDescription
quantityintegeryesnew seats/units for the staged listing

No output schema declared.

No examples provided.

Install

How do I install the EverList Hub MCP server?

EverList Hub is a hosted endpoint at https://everlist.network/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 · everlist.network

# add to Claude Code
claude mcp add --transport http everlist-hq-everlist-hub 'https://everlist.network/mcp'
Common questions

What is the EverList Hub MCP server?

EverList Hub is an MCP server listed in the public MCP registry as io.github.everlist-hq/everlist-hub. Listing-first agent commerce: search, book, and settle dated listings in Midnight escrow. 21 tools. This page covers its hosted endpoint (https://everlist.network/mcp).

Is the EverList Hub MCP server safe to use?

EverList Hub 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 EverList Hub MCP server expose?

EverList Hub exposes 21 tools: everlist_contract, everlist_verticals, everlist_search, everlist_listing, everlist_book, and 16 more. Their descriptions and schemas cost roughly 2,052 tokens of context every time the server is loaded.

Does the EverList Hub MCP server require authentication?

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

Is the EverList Hub MCP server still maintained?

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

What did VerifyMCP test on the EverList Hub MCP server?

VerifyMCP ran 12 checks on EverList Hub, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about EverList Hub: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.