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.

Egonex

REMOTE · API.EGONEX.AI

Search items and services from independent sellers, ask the seller, and request an order.

Available components

63 Trust /100

Last scanned (1 minute ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 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 Security63
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5445 tokens (~907/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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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 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.

  • 5 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 4 Nov 26 63

    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://api.egonex.ai/api/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=egonex.ai CN=YE2,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 ECDSA 256 ECDSA-SHA384 546f7b4faa2a16d4fdb2aedac0aef8263d9
SANs: *.egonex.ai, egonex.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 insecure

Validation of api.egonex.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
egonex.ai. 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
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.egonex.ai/api/v1/mcp Verified 200
http (plaintext) http://api.egonex.ai/api/v1/mcp HTTPS enforced 301 https://api.egonex.ai:443/api/v1/mcp
MCP tools · 6 exposed · ~5,186 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
ask_seller ~369

Ask one question about a listing before your user decides: availability, condition, what is included, timing, location, sizes, how delivery or pickup works. If the seller has their assistant (Ego) answering (seller.answers_questions is true in search results), the answer comes back in this response, written only from the seller's public page and listings; when the seller has set a lowest price, Ego can also talk price with you about that listing: it may counter once, and when you agree a price the answer has deal (deal.id, valid for 24 hours, for one request_order). For 24 hours it holds the price it named to you and won't go lower, and it declines questions that are not about this store (reason declined). Otherwise the response says the seller answers in chat. For a follow-up about the same listing, pass the conversation_id from the previous answer so Ego sees the earlier questions and answers. After three declined questions in a row in one conversation, Ego stops answering there (reason conversation_stopped). Ego answers a limited number of questions from you per seller per minute and per day (reasons slow_down, handoff, email_required); Ego may tell the seller about a question it can't answer, but the seller's reply doesn't come back through ask_seller. To send your question to the seller as your user instead, use message_seller.

NameTypeReqDescription
conversation_idstring–From the previous ask_seller answer about the same listing (kept for 30 minutes): Ego then sees the earlier questions and answers.
offer_idstringyesThe listing id from search_offers (the 8-character id at the end of a listing page URL also works).
questionstringyesYour question, up to 500 characters.
NameTypeReqDescription
answerstring–The answer, or what Ego said when it didn't answer.
answeredbooleanyestrue = answer is the seller's assistant answering now.
conversation_idstring–Pass it with the next question about the same listing (kept for 30 minutes).
dealobject–The price Ego agreed with you (only when it agreed one). Pass deal.id as deal_id to request_order within 24 hours; that request then keeps this price for pay_order and for the order your user pays on…
nextstringyesWhat to do next.
offerobjectyesOne listing.
reasonstring–Why it wasn't answered: seller_answers_in_chat, handoff (the seller has to answer, also after many questions from you today), busy (Ego answers no more questions for this seller today; send the selle…

No examples provided.

check_request ~1,463

Check a request made with request_order or message_seller: the confirm link and, once there is one, the order it led to (order has its title, quantity, amount and deadlines). Returns the confirm_url again. status is one of: - pending: Your user hasn't confirmed or declined yet. Nothing has happened: no order, no charge, no message sent. Give your user the confirm_url. - declined: Your user chose not to go ahead on the confirm page. Nothing was ordered, charged or sent. Don't make a new request unless your user asks. - expired: Nobody acted on the link within 7 days, so it no longer works. Nothing was ordered, charged or sent. Make a new request if your user still wants it. - listing_unavailable: This listing isn't for sale anymore (it was taken down, or it sold out), so the request can't go ahead. Nothing was ordered, charged or sent. Search again for something else, or ask the seller with ask_seller whether it will be back. - message_sent (messages only): Your user confirmed and the message was sent to the seller as your user. The seller replies in the Egonex chat (a buyer without an Egonex account gets the reply by email); you don't see the reply here. - awaiting_order (orders only): Your user confirmed: a chat with the seller is open with the order filled in, but they haven't placed the order yet. They place it and pay on Egonex; once they do, this status follows that order. After an order is placed, everything about it (confirming delivery, a problem with it, a refund or a cancellation) is handled on Egonex, in your user's chat with the seller (a buyer without an Egonex account opens it from the link in Egonex's email), not through these tools. - payment_in_progress (orders only): A payment for this order is being processed: usually a few seconds when you paid with pay_order; a few minutes after pay_order returned payment_error, while Egonex checks with Stripe whether it went through; and up to a few business days for a bank payment your user made on Egonex. Do…

NameTypeReqDescription
request_idstringyesThe id returned by request_order or message_seller.
NameTypeReqDescription
close_reasonstring–closed_unpaid only: why the order closed (absent for orders closed before 2026-11-01).
confirm_urlstringyesThe page your user opens to confirm.
dealobject–The price Ego agreed with you (only when it agreed one). Pass deal.id as deal_id to request_order within 24 hours; that request then keeps this price for pay_order and for the order your user pays on…
expires_atstringyesWhen a pending request expires (RFC 3339).
idstringyesRequest id (pass it as request_id).
kindstringyesorder (request_order) or message (message_seller).
nextstring–What to do next (when the request is created).
offer_idstringyesThe listing.
orderobject–The order this request led to: made with pay_order, or placed by your user in the chat after confirming. Times are given only where they matter for the status.
order_idstring–The order this request led to (same as order.id).
paymentobject–On a new order request that can be paid directly with a Stripe Shared Payment Token (pay_order).
statusstringyesWhere this request and its order stand: pending (waiting for your user to confirm or decline; nothing has happened yet), declined (your user chose not to go ahead), expired (nobody acted within 7 day…

No examples provided.

message_seller ~224

Send a message to the seller of a listing as your user: a question Ego couldn't answer, a custom request, or whether a sold-out listing will be back. Returns a confirm_url for your user: nothing is sent until they open it and confirm. They need only an email address, no Egonex account. The message then goes to the seller's Egonex chat as your user, and the seller replies there (a buyer without an Egonex account gets the reply by email); you don't see the reply. Use check_request with the returned id to see whether it was sent (message_sent). To get an answer from the seller's assistant (Ego) right away instead, use ask_seller.

NameTypeReqDescription
agent_namestring–Your name, shown to your user when they confirm.
messagestringyesWhat the seller gets from your user, up to 1000 characters.
offer_idstringyesThe listing id from search_offers (the 8-character id at the end of a listing page URL also works).
NameTypeReqDescription
close_reasonstring–closed_unpaid only: why the order closed (absent for orders closed before 2026-11-01).
confirm_urlstringyesThe page your user opens to confirm.
dealobject–The price Ego agreed with you (only when it agreed one). Pass deal.id as deal_id to request_order within 24 hours; that request then keeps this price for pay_order and for the order your user pays on…
expires_atstringyesWhen a pending request expires (RFC 3339).
idstringyesRequest id (pass it as request_id).
kindstringyesorder (request_order) or message (message_seller).
nextstring–What to do next (when the request is created).
offer_idstringyesThe listing.
orderobject–The order this request led to: made with pay_order, or placed by your user in the chat after confirming. Times are given only where they matter for the status.
order_idstring–The order this request led to (same as order.id).
paymentobject–On a new order request that can be paid directly with a Stripe Shared Payment Token (pay_order).
statusstringyesWhere this request and its order stand: pending (waiting for your user to confirm or decline; nothing has happened yet), declined (your user chose not to go ahead), expired (nobody acted within 7 day…

No examples provided.

pay_order ~1,246

Pay for an order made with request_order without the confirm page, using a Stripe Shared Payment Token that your user approved (for example in Stripe Link). request_order returns payment: the amount per unit in USD, max_quantity and payment_handlers with the Stripe network_id to issue the token to; the token must allow at least amount × quantity in USD (plus sales tax where Egonex collects it, calculated from the shipping address for an item that ships and from the card's billing address otherwise; if the token doesn't cover it, nothing is charged and the error gives the total). Egonex creates the order for your user (a guest account on the email you give; receipts and seller replies go to that email). The result has the same status and order as check_request (order has its title, quantity, amount and deadlines), so you can tell your user where the order stands. The seller confirms an order before the buyer pays: when the result has status waiting_for_seller, the order was sent to the seller and nothing was charged; once check_request shows ready_to_pay, call pay_order again with the same request_id and buyer_email and a valid token (or your user pays from the link Egonex emails them). If the seller declines or doesn't respond, the order closes and nothing is charged. When the result has status paid and order.accept_by, the token was charged first and the seller has until then to accept; if they decline or don't respond, your user is refunded minus the payment processing fee. For an item that ships (payment.requires_shipping_address), the pay_order call that charges must have shipping_address and shipping_address_confirmed=true, otherwise nothing is charged (shipping_address_required / shipping_address_not_confirmed): before you pay, ask your user for the full address, read it back to them and pass it only once they say it's right. A call that only sends the order to the seller charges nothing and doesn't keep an address: pass it on the call that pays. An address t…

NameTypeReqDescription
accept_termsbooleanyestrue only if your user agreed to Egonex's Terms of Service and Privacy Policy (payment.terms_url).
buyer_emailstringyesYour user's email address. Receipts, the order and seller replies go there.
buyer_namestring–Optional name shown to the seller.
delivery_daysinteger–Days the seller has to deliver once the order starts (it starts when it is paid and accepted): shipping time for an item, the day of the lesson or service, 1 for digital goods. Default: the listing's…
quantityinteger–How many units (items, hours, sessions...) at the listed price. Default 1.
request_idstringyesThe id returned by request_order.
shared_payment_tokenstringyesThe Stripe Shared Payment Token (spt_...) your user approved for this purchase.
shipping_addressobject–For an item that ships (payment.requires_shipping_address): where to ship it, as your user confirmed it. Required on the call that charges (when the seller accepts first, the call after they accept);…
shipping_address_confirmedboolean–true only if you read shipping_address back to your user and they said it's right. Required with shipping_address on the call that charges.
NameTypeReqDescription
nextstringyesWhat happens next.
orderobjectyesThe order this request led to: made with pay_order, or placed by your user in the chat after confirming. Times are given only where they matter for the status.
paidbooleanyestrue = the payment went through.
request_idstringyesThe request.
statusstringyesWhere the order stands, as check_request reports it: pending (waiting for your user to confirm or decline; nothing has happened yet), declined (your user chose not to go ahead), expired (nobody acted…

No examples provided.

request_order ~284

Start an order for one listing on your user's behalf. Returns a confirm_url: your user opens it, checks the listing and price, enters an email address and pays on Egonex (payments are processed by Stripe). Nothing is ordered or charged until they confirm, and no Egonex account is needed. Use note for what the seller needs to know, such as dates, quantity, size, or the area for delivery or pickup. For an item that ships, your user enters the shipping address when they pay on Egonex. Use check_request with the returned id to see whether your user confirmed. A sold-out listing, or one whose seller isn't taking new orders right now, can't be ordered (error listing_unavailable); ask_seller can still ask whether it will be back.

NameTypeReqDescription
agent_namestring–Your name, shown to your user when they confirm.
deal_idstring–Optional: deal.id from an ask_seller answer in which Ego agreed a price with you for this listing (use it within 24 hours, once). The order then uses that price.
notestring–Optional note to the seller, e.g. the date or quantity your user wants.
offer_idstringyesThe listing id from search_offers (the 8-character id at the end of a listing page URL also works).
NameTypeReqDescription
close_reasonstring–closed_unpaid only: why the order closed (absent for orders closed before 2026-11-01).
confirm_urlstringyesThe page your user opens to confirm.
dealobject–The price Ego agreed with you (only when it agreed one). Pass deal.id as deal_id to request_order within 24 hours; that request then keeps this price for pay_order and for the order your user pays on…
expires_atstringyesWhen a pending request expires (RFC 3339).
idstringyesRequest id (pass it as request_id).
kindstringyesorder (request_order) or message (message_seller).
nextstring–What to do next (when the request is created).
offer_idstringyesThe listing.
orderobject–The order this request led to: made with pay_order, or placed by your user in the chat after confirming. Times are given only where they matter for the status.
order_idstring–The order this request led to (same as order.id).
paymentobject–On a new order request that can be paid directly with a Stripe Shared Payment Token (pay_order).
statusstringyesWhere this request and its order stand: pending (waiting for your user to confirm or decline; nothing has happened yet), declined (your user chose not to go ahead), expired (nobody acted within 7 day…

No examples provided.

search_offers ~1,600

Search listings on Egonex, a marketplace where individual people sell things and services directly. Use it when your user wants to buy, hire, book, rent or commission something from a person rather than a store, for example: - items, new or used: cameras and lenses, phones, laptops, bikes, furniture, clothing, collectibles, instruments, gear; - lessons and coaching: languages, music, tutoring and test prep, fitness, cooking, art, coding; - services in person: photography, repairs (bikes, electronics, film cameras), cleaning, moving help, pet care, babysitting, beauty, tours; - online and freelance work: design, writing and editing, translation, software, marketing, consulting, video editing; - digital goods, tickets, handmade and custom work. Each result is one listing with a price and unit (per item, package, hour, session, day, week, month, night, person or project; USD), how it is delivered (in person in a city, online, or either), for physical items its condition (new, like_new, good, fair, for_parts), brand / model / gtin when the seller gave them, and ships = true when the seller posts it (your user enters the shipping address when paying on Egonex, or you pass it to pay_order when you pay), delivery_days when the seller states a usual delivery time (days to ship for posted items), up to 4 photo URLs, the listing's own page, ask_url / order_url links a person can open, and the seller: their public page, seller.answers_questions (true = ask_seller gets an answer right away), seller.trusted (true = Egonex's Trusted badge, given automatically for the seller's recent trading on Egonex, not set by the seller) and, when there are 3 or more, seller.orders_completed; seller.review_count, seller.positive_count and seller.negative_count appear when the seller has counted buyer reviews (each review is positive or negative), and seller.positive_rate (0 to 100, rounded down) once there are 10 or more. Results are ranked by how well they match the query words (rarer words…

NameTypeReqDescription
categorystring–One category. Goods: electronics (electronics & accessories), fashion (clothing & shoes), jewelry (jewelry, bags & accessories), beauty (beauty & personal care), home (home & living), toys (toys & ga…
citystring–City for in-person listings, e.g. "San Francisco" or "Portland, OR". In-person listings in that city come first, then those nearby (same metro area or within about 30 miles); listings done only in pe…
conditionstring–Physical items: the lowest condition your user accepts (new > like_new > good > fair > for_parts); like_new returns new and like_new. Listings that don't state a condition are included.
deliverystring–onsite = in person only, remote = online only, hybrid = either.
limitinteger––
max_pricenumber–Highest price in USD (per the listing's unit).
min_pricenumber–Lowest price in USD (per the listing's unit).
offsetinteger––
querystring–What your user wants, in a few words, e.g. "spanish lessons for kids", "used fujifilm camera", "logo design", "road bike tune-up". Matched as whole words and their word forms (lesson / lessons, color…
storestring–Only this seller's storefront (the store name after shop.egonex.ai/@).
NameTypeReqDescription
browse_urlstring–When nothing matched: the sellers directory for people.
categoriesarray–When nothing matched: categories that have listings.
next_offsetinteger|nullyesPass as offset for the next page; null = no more.
notestring–How the results were found, when not every word matched or nothing did, or not every word was used.
offersarrayyesListings on this page.
searched_asobject–Only when Egonex searched a rewrite of query (it isn't in English, has words too short to search, ends with a place, or nothing matched): what was searched. matched_words and missing_words are in the…
totalintegeryesHow many listings match in all.
unused_wordsarray–Words of query that were not used: only the first 12 search words count. Search again with them if they matter.

No examples provided.

Install

How do I install the Egonex MCP server?

Egonex is a hosted endpoint at https://api.egonex.ai/api/v1/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 · api.egonex.ai

# add to Claude Code
claude mcp add --transport http ai-egonex-marketplace 'https://api.egonex.ai/api/v1/mcp'
Common questions

What is the Egonex MCP server?

Egonex is an MCP server listed in the public MCP registry as ai.egonex/marketplace. Search items and services from independent sellers, ask the seller, and request an order. This page covers its hosted endpoint (https://api.egonex.ai/api/v1/mcp).

Is the Egonex MCP server safe to use?

Egonex scores 63 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 Egonex MCP server expose?

Egonex exposes 6 tools: ask_seller, check_request, message_seller, pay_order, request_order, search_offers. Their descriptions and schemas cost roughly 5,186 tokens of context every time the server is loaded.

Does the Egonex MCP server require authentication?

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

Is the Egonex MCP server still maintained?

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