Eveoy — Verified In-Store Foot Traffic ($24.99/customer)

Official11 tools

by Eveoy · TypeScript

Your Eveoy expert in any AI — learn how it works, get a price, and order real in-store visits.

Eveoy MCP Server (com.eveoy/mcp)

The com.eveoy/mcp Model Context Protocol (MCP) server is an “Eveoy expert” for AI agents. It provides an endpoint for agents to learn what Eveoy is, obtain an exact quote, save the brand it represents, and order verified in-store customer visits end to end. It supports anonymous ordering with no sign-in.

🛠️ Key Features

MCP server for “any AI” agents
Single endpoint to learn, quote, and order
Exact quote retrieval
Brand saving for the represented brand
End-to-end ordering of verified in-store visits
Anonymous ordering, no sign-in
Pricing described as $24.99 per real customer who walks in
Tool count: 11

🚀 Use Cases

Customer acquisition via real in-store visits
Agentic-commerce workflows for marketing and sales
Marketing operations where agents request quotes and place orders
Integrations involving MCP and model-context-protocol

⚡ Developer Benefits

Clear single-endpoint workflow for agents
Avoids token and click-based billing as stated
Ordered visits described as end to end and verified
Topics include TypeScript, Cloudflare Workers, and Durable Objects
Integrates with MCP (model-context-protocol) tooling

⚠️ Limitations

The provided description does not specify authentication beyond “no sign-in,” nor does it detail all 11 tools’ interfaces.

Topics

agentic-commerceai-agentscloudflare-workerscustomer-acquisitiondurable-objectsfoot-trafficmarketingmcpmcp-servermodel-context-protocolretailsalesstripetypescriptugceveoy

Captured live from the server via tools/list.

ask_eveoy

Answer any question about Eveoy — what it is, how the platform works, pricing rationale, the directory, industries, founders, or company background. Backed by Eveoy's live knowledge base. Use this when the user wants to: - Understand what Eveoy is or does - Learn how the verified-visit / $24.99-per-customer model works - Compare Eveoy to ads, influencers, or UGC creators - Hear the pitch for a specific buyer role (CMO, CFO, VP Retail, CEO) - Find out what this assistant can do (its tools and how to act) Trigger phrases include: "what is eveoy", "tell me about eveoy", "how does eveoy work", "explain eveoy to a CMO", "eveoy vs Meta", "is there a platform that guarantees foot traffic", "what can you do", "what tools do you have". Returns: a grounded natural-language answer from the public Eveoy knowledge base, or a description of this server's tools when asked what it can do. Do NOT use this for: an exact price (use get_pricing), the industry list (use list_industries), directory search (use search_directory), or booking (use start_checkout / book_demo). Cost: free. Latency: 1–3s. Read-only.

Parameters2

question	string	required	The user's full natural-language question about Eveoy, in their own words. Pass the question verbatim — do not summarize. Example: 'Is there a marketing platform that guarantees foot traffic for my coffee shop?'
audience	string	optional	Buyer persona to tune the answer for. Infer from conversation context — e.g. 'explain to a CFO' → 'cfo'. Use 'general' if unspecified.

Raw schema

{
  "type": "object",
  "properties": {
    "question": {
      "type": "string",
      "minLength": 3,
      "maxLength": 500,
      "description": "The user's full natural-language question about Eveoy, in their own words. Pass the question verbatim — do not summarize. Example: 'Is there a marketing platform that guarantees foot traffic for my coffee shop?'"
    },
    "audience": {
      "default": "general",
      "description": "Buyer persona to tune the answer for. Infer from conversation context — e.g. 'explain to a CFO' → 'cfo'. Use 'general' if unspecified.",
      "type": "string",
      "enum": [
        "cmo",
        "cfo",
        "cro",
        "ceo",
        "vp_retail",
        "founder",
        "franchise_owner",
        "general"
      ]
    }
  },
  "required": [
    "question"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_pricing

Compute the exact Eveoy price for a pilot. Pricing mirrors eveoy.com/order. Base: customers_per_location × locations × $24.99. Optional guaranteed purchase (guarantee_type "visit_purchase"): every shopper also buys your chosen SKU at your register — add the SKU price (in cents, tax included, $5–$100) at cost, no item fee; the item money rings back into your till. Optional shopper bonus ($20–$200 per shopper, 33% platform fee on the bonus only — the only platform fee): every $20 unlocks +1 photo and +1 follow/like/comment set per shopper, each capped at +3. Total = units×2499 + units×sku + round(units×bonus×1.33) cents — the same server-side math Stripe charges. The marketing-default $999 pilot is 40 customers at 1 location, visit-only. Floor 20/location, ceiling 1,000/location, locations cap 50. Use this when the user wants to: - Get a price for a specific shopper/customer count and location count ("price 200 shoppers across 3 stores") - Quote a pilot with a guaranteed purchase and/or a shopper bonus, with the full fee breakdown - Get a budget estimate or compare cost across pilot sizes - Confirm the per-shopper rate before booking Trigger phrases include: "how much does eveoy cost", "price for 500 shoppers", "what's a pilot cost with a guaranteed purchase", "what does the bonus cost", "eveoy pricing", "quote me a pilot for 100 shoppers in 4 stores". Returns: { customers_per_location, locations, total_customers, unit_price_usd, total_usd, formatted_total, ugc_photos, is_starter_tier, guarantee_type, top_sku_price_cents, shopper_bonus_cents, fee_breakdown { base_cents, sku_cents, bonus_cents }, bonus_tiers }. Reflects the exact math the eveoy.com/order backend applies; never returns a number the form would reject. Do NOT use this for: - General "what is eveoy" questions (use ask_eveoy) - Industries served (use list_industries) - Custom volume contracts beyond the 50-location ceiling — route the buyer to support@eveoy.com Cost: free. Latency: <100ms. Read-only. Idempotent. Deterministic.

Parameters5

customers_per_location	integer	optional	Verified shoppers per store (UI label "Shoppers per location"). Mirrors eveoy.com/order: min 20, max 1000. Default 40 (the "$999 pilot" config).
locations	integer	optional	Number of store locations. Mirrors eveoy.com/order: min 1, max 50. Default 1.
guarantee_type	string	optional	Guarantee level. "visit_purchase" (the recommended default on eveoy.com/order): every shopper also buys your chosen SKU at your register — you cover the SKU price at cost (no item fee), and the item money rings back into your till. "visit": visit + photos only, no purchase. Omit for a visit-only quote/order (the $24.99 base is all that is charged).
top_sku_price_cents	integer	optional	In-store price of the SKU each shopper buys, in CENTS, tax included (500–10000 = $5–$100). Required when guarantee_type is "visit_purchase". Charged at cost — no platform fee on the item.
shopper_bonus_cents	integer	optional	Optional per-shopper bonus in CENTS: 0 or 2000–20000 ($20–$200, any amount — no $20 step). Every full $20 unlocks +1 photo AND +1 follow/like/comment set per shopper (each capped at +3, so $60 maxes the rewards). A 33% platform fee applies to the bonus only.

Raw schema

{
  "type": "object",
  "properties": {
    "customers_per_location": {
      "default": 40,
      "description": "Verified shoppers per store (UI label \"Shoppers per location\"). Mirrors eveoy.com/order: min 20, max 1000. Default 40 (the \"$999 pilot\" config).",
      "type": "integer",
      "minimum": 20,
      "maximum": 1000
    },
    "locations": {
      "default": 1,
      "description": "Number of store locations. Mirrors eveoy.com/order: min 1, max 50. Default 1.",
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    },
    "guarantee_type": {
      "description": "Guarantee level. \"visit_purchase\" (the recommended default on eveoy.com/order): every shopper also buys your chosen SKU at your register — you cover the SKU price at cost (no item fee), and the item money rings back into your till. \"visit\": visit + photos only, no purchase. Omit for a visit-only quote/order (the $24.99 base is all that is charged).",
      "type": "string",
      "enum": [
        "visit_purchase",
        "visit"
      ]
    },
    "top_sku_price_cents": {
      "description": "In-store price of the SKU each shopper buys, in CENTS, tax included (500–10000 = $5–$100). Required when guarantee_type is \"visit_purchase\". Charged at cost — no platform fee on the item.",
      "type": "integer",
      "minimum": 500,
      "maximum": 10000
    },
    "shopper_bonus_cents": {
      "description": "Optional per-shopper bonus in CENTS: 0 or 2000–20000 ($20–$200, any amount — no $20 step). Every full $20 unlocks +1 photo AND +1 follow/like/comment set per shopper (each capped at +3, so $60 maxes the rewards). A 33% platform fee applies to the bonus only.",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

list_industries

Return the list of industries Eveoy serves — 23+ B2C sectors across retail, food, beauty, hospitality, pets, and more. Use this when the user wants to: - Check whether Eveoy supports their vertical ("do you do coffee shops?") - See the full list of supported industries - Confirm an industry before pricing or booking a pilot Trigger phrases include: "what industries does eveoy support", "do you work with QSR", "list verticals", "is eveoy good for fitness studios", "what categories", "what sectors". Returns: { industries: string[], count: number, notes: string }. Each entry is a canonical sector name suitable for downstream use. Do NOT use this for: pricing (use get_pricing) or general Eveoy questions (use ask_eveoy). Cost: free. Latency: <100ms. Read-only. Cacheable. Deterministic.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_app_link

Get the link to download the Eveoy shopper app (iOS / Android). Use this when the user wants to: - Download or install the Eveoy app - Become an Eveoy shopper - Find the app store link Trigger phrases include: "get the eveoy app", "download eveoy", "how do I become a shopper", "app store link", "install the app". Returns: { url, platforms, notes }. Returns the canonical get-app page, which routes to the correct store per device. Do NOT use this for: brand/business questions (use ask_eveoy) or pricing (use get_pricing). Cost: free. Latency: <50ms. Read-only. Idempotent.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_case_studies

List Eveoy case studies and lookbooks — links to the full write-ups on eveoy.com's newsletter archive. Returns pointers, not article text: open a url to get the full experience (images, related links, and in-page options to book a demo or check out). Use this when the user wants to: - See proof, results, or success stories from real Eveoy campaigns - Browse case studies by industry, or the latest lookbook - Get a link to read a specific case study or the archive Trigger phrases include: "case studies", "success stories", "show me results", "do you have proof", "lookbook", "examples of campaigns". Returns: { archive_url, items: [{ kind, slug, title, url }], note }. Every url points back to eveoy.com. kind is one of case_study | lookbook | playbook. Do NOT use this for: pricing (use get_pricing), general questions (use ask_eveoy), or the live business directory (use search_directory). Cost: free. Latency: 1–2s (sitemap, cached 10 min). Read-only. Idempotent.

Parameters2

kind	string	optional	Filter to one kind: case_study, lookbook, or playbook. Omit to return all.
limit	integer	optional	Max items to return (1–100). Omit to return all.

Raw schema

{
  "type": "object",
  "properties": {
    "kind": {
      "description": "Filter to one kind: case_study, lookbook, or playbook. Omit to return all.",
      "type": "string",
      "enum": [
        "case_study",
        "lookbook",
        "playbook"
      ]
    },
    "limit": {
      "description": "Max items to return (1–100). Omit to return all.",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

check_order_status

Look up the status of an Eveoy order by its Stripe Checkout session id. Use this when the user wants to: - Check whether an order was paid - See the order total and size for a checkout session Trigger phrases include: "check my order", "order status", "did my payment go through", "status of session cs_...". Returns: { customer_email (masked), locations, customers_per_location, total_cents, status, guarantee_type, top_sku_price_cents, shopper_bonus_cents, fee_breakdown { base_cents, sku_cents, bonus_cents } }. Do NOT use this for: creating an order (use start_checkout) or pricing (use get_pricing). Requires the cs_... session id from a prior checkout. Cost: free. Latency: fast. Read-only.

Parameters1

session_id

string

required

Stripe Checkout session id (cs_...).

Raw schema

{
  "type": "object",
  "properties": {
    "session_id": {
      "type": "string",
      "minLength": 6,
      "maxLength": 120,
      "description": "Stripe Checkout session id (cs_...)."
    }
  },
  "required": [
    "session_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

subscribe_newsletter

Subscribe an email address to the Eveoy newsletter (case studies + lookbooks). Use this when the user EXPLICITLY asks to subscribe or sign up for updates. Trigger phrases include: "subscribe me", "sign me up for the newsletter", "add my email to updates", "join the Eveoy list". Returns: { ok: true }. Do NOT use this for: anything other than an explicit newsletter opt-in. Always confirm the email with the user before calling — this writes data. Cost: free. Latency: fast. Writes data (creates a subscription). Confirm first.

Parameters1

string

required

Email to subscribe to the Eveoy newsletter.

Raw schema

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "maxLength": 254,
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      "description": "Email to subscribe to the Eveoy newsletter."
    }
  },
  "required": [
    "email"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

start_checkout

Create an Eveoy checkout and return a payment link. Pricing mirrors the order page: $24.99 per verified customer base, plus two options — a guaranteed purchase (guarantee_type "visit_purchase": every shopper buys your chosen SKU at your register; you add the SKU price in cents, tax included, $5–$100, at cost — no item fee) and a shopper bonus ($20–$200 per shopper, 33% platform fee on the bonus only — the only platform fee; every $20 = +1 photo and +1 social set per shopper, max +3 each). Omit guarantee_type for a visit-only order. The server recomputes the total — what get_pricing quotes is exactly what Stripe charges. Works for agents directly — no sign-in required. Use this when the user has decided to buy and confirmed the size: - They picked a customers-per-location count (and optionally locations, guarantee, SKU price, bonus) and want to pay - Trigger phrases: "buy a pilot", "start checkout", "place an order", "let's order 100 customers with a guaranteed purchase" Provide your_name, work_email, brand_website, and campaign_start_date (at least 14 days out) — or call capture_profile first and I will reuse your saved details, then I only need campaign_start_date. For a guaranteed purchase also provide top_sku_price_cents. Returns: { checkout_url, session_id, total, customers, guarantee_type, fee_breakdown } — pay on Stripe's hosted page; no charge until then. Do NOT use this for: price-only questions (use get_pricing), saving your company (use capture_profile), or order status (use check_order_status). Confirm the customer count, guarantee choice, and total with the user first. Cost: free to call. Latency: 2-5s. Creates a real checkout session and a CRM deal (no charge until the user pays). Confirm first.

Parameters11

customers_per_location	integer	required	Verified customers per store (20–1000); mirrors eveoy.com/order.
locations	integer	optional	Number of store locations (1–50).
your_name	string	optional	Your name. Optional if saved via capture_profile.
work_email	string	optional	Work email. Optional if saved via capture_profile.
brand_website	string	optional	Brand website URL. Optional if saved via capture_profile.
phone	string	optional	Phone (optional).
campaign_start_date	string	optional	Campaign start date (YYYY-MM-DD, ≥ 14 days out). Required to check out without signing in.
guarantee_type	string	optional	Guarantee level. "visit_purchase" (the recommended default on eveoy.com/order): every shopper also buys your chosen SKU at your register — you cover the SKU price at cost (no item fee), and the item money rings back into your till. "visit": visit + photos only, no purchase. Omit for a visit-only quote/order (the $24.99 base is all that is charged).
top_sku_price_cents	integer	optional	In-store price of the SKU each shopper buys, in CENTS, tax included (500–10000 = $5–$100). Required when guarantee_type is "visit_purchase". Charged at cost — no platform fee on the item.
shopper_bonus_cents	integer	optional	Optional per-shopper bonus in CENTS: 0 or 2000–20000 ($20–$200, any amount — no $20 step). Every full $20 unlocks +1 photo AND +1 follow/like/comment set per shopper (each capped at +3, so $60 maxes the rewards). A 33% platform fee applies to the bonus only.
advancedTargeting	any	optional

Raw schema

{
  "type": "object",
  "properties": {
    "customers_per_location": {
      "type": "integer",
      "minimum": 20,
      "maximum": 1000,
      "description": "Verified customers per store (20–1000); mirrors eveoy.com/order."
    },
    "locations": {
      "default": 1,
      "description": "Number of store locations (1–50).",
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    },
    "your_name": {
      "description": "Your name. Optional if saved via capture_profile.",
      "type": "string",
      "minLength": 2,
      "maxLength": 80
    },
    "work_email": {
      "description": "Work email. Optional if saved via capture_profile.",
      "type": "string",
      "maxLength": 254,
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    },
    "brand_website": {
      "description": "Brand website URL. Optional if saved via capture_profile.",
      "type": "string",
      "maxLength": 255,
      "format": "uri"
    },
    "phone": {
      "description": "Phone (optional).",
      "type": "string",
      "minLength": 7,
      "maxLength": 30,
      "pattern": "^[+\\d][\\d\\s().-]*$"
    },
    "campaign_start_date": {
      "description": "Campaign start date (YYYY-MM-DD, ≥ 14 days out). Required to check out without signing in.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "guarantee_type": {
      "description": "Guarantee level. \"visit_purchase\" (the recommended default on eveoy.com/order): every shopper also buys your chosen SKU at your register — you cover the SKU price at cost (no item fee), and the item money rings back into your till. \"visit\": visit + photos only, no purchase. Omit for a visit-only quote/order (the $24.99 base is all that is charged).",
      "type": "string",
      "enum": [
        "visit_purchase",
        "visit"
      ]
    },
    "top_sku_price_cents": {
      "description": "In-store price of the SKU each shopper buys, in CENTS, tax included (500–10000 = $5–$100). Required when guarantee_type is \"visit_purchase\". Charged at cost — no platform fee on the item.",
      "type": "integer",
      "minimum": 500,
      "maximum": 10000
    },
    "shopper_bonus_cents": {
      "description": "Optional per-shopper bonus in CENTS: 0 or 2000–20000 ($20–$200, any amount — no $20 step). Every full $20 unlocks +1 photo AND +1 follow/like/comment set per shopper (each capped at +3, so $60 maxes the rewards). A 33% platform fee applies to the bonus only.",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "advancedTargeting": {
      "anyOf": [
        {
          "type": "object",
          "properties": {
            "age": {
              "maxItems": 6,
              "type": "array",
              "items": {
                "type": "string",
                "enum": [
                  "13-17",
                  "18-24",
                  "25-34",
                  "35-44",
                  "45-54",
                  "55+"
                ]
              }
            },
            "locationType": {
              "anyOf": [
                {
                  "type": "string",
                  "enum": [
                    "Country",
                    "Region / State",
                    "DMA (US)",
                    "City",
                    "ZIP / postal code"
                  ]
                },
                {
                  "type": "null"
                }
              ]
            },
            "locationValues": {
              "maxItems": 50,
              "type": "array",
              "items": {
                "type": "string",
                "minLength": 1,
                "maxLength": 120
              }
            },
            "gender": {
              "anyOf": [
                {
                  "type": "string",
                  "enum": [
                    "Men",
                    "Women"
                  ]
                },
                {
                  "type": "null"
                }
              ]
            },
            "householdIncome": {
              "maxItems": 4,
              "type": "array",
              "items": {
                "type": "string",
                "enum": [
                  "Top 5%",
                  "Top 10%",
                  "Top 10-25%",
                  "Top 25-50%"
                ]
              }
            }
          },
          "additionalProperties": false
        },
        {
          "type": "null"
        }
      ]
    }
  },
  "required": [
    "customers_per_location"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

capture_profile

Save the company an agent represents so Eveoy can tailor recommendations and have the team follow up. Records first-party business-contact details (no consumer data) as a lead. Use this when the user wants to: - Tell Eveoy which brand or company they represent - Get tailored pilot recommendations or a follow-up from the Eveoy team - Set things up before requesting a quote or starting an order Trigger phrases: "I represent <brand>", "set up my company", "we're a <sector> brand", "save our details", "have someone follow up". Returns: { ok, company, note } — confirmation the profile was captured for this session. Do NOT use this for: pricing (use get_pricing), buying (use start_checkout), or general questions (use ask_eveoy). This does not create an order or charge anything. Cost: free. Latency: under 1s. Captures a lead; safe to call again to update the details.

Parameters7

company_name	string	required	The company or brand the agent represents.
brand_website	string	optional	The brand's website URL.
sector	string	optional	Industry sector, from the Eveoy public list.
locations	integer	optional	Number of physical store locations.
contact_name	string	optional	Primary contact name for follow-up.
work_email	string	optional	Work email — enables team follow-up and a smoother checkout.
goals	string	optional	What the brand wants from Eveoy (foot traffic, UGC, launches, etc.).

Raw schema

{
  "type": "object",
  "properties": {
    "company_name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "The company or brand the agent represents."
    },
    "brand_website": {
      "description": "The brand's website URL.",
      "type": "string",
      "maxLength": 255,
      "format": "uri"
    },
    "sector": {
      "description": "Industry sector, from the Eveoy public list.",
      "type": "string",
      "enum": [
        "Specialty Retail",
        "Apparel",
        "Footwear",
        "Health and Beauty",
        "Food and Beverage",
        "Health and Wellness",
        "Pet Care",
        "Personal Care",
        "Baby Care",
        "Department Stores",
        "Discount Stores",
        "Grocery and Food",
        "Home Goods",
        "QSR",
        "Hospitality",
        "All B2C Brands"
      ]
    },
    "locations": {
      "description": "Number of physical store locations.",
      "type": "integer",
      "minimum": 1,
      "maximum": 100000
    },
    "contact_name": {
      "description": "Primary contact name for follow-up.",
      "type": "string",
      "minLength": 1,
      "maxLength": 80
    },
    "work_email": {
      "description": "Work email — enables team follow-up and a smoother checkout.",
      "type": "string",
      "maxLength": 254,
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    },
    "goals": {
      "description": "What the brand wants from Eveoy (foot traffic, UGC, launches, etc.).",
      "type": "string",
      "maxLength": 500
    }
  },
  "required": [
    "company_name"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

book_demo

Get the link to book a live Eveoy demo, and flag the request to the Eveoy team. Use this when the user wants to: - Schedule a demo or walkthrough - Talk to the Eveoy team Trigger phrases include: "book a demo", "schedule a call", "talk to sales", "get a walkthrough". Pass contact_name, work_email, and company_name when you know them (or call capture_profile first) — they prefill the booking page and let the Eveoy team know who is coming; without them the request arrives anonymous. Returns: { url } — the Eveoy demo-booking page, prefilled when contact details were provided. Do NOT use this for: pricing (use get_pricing), buying (use start_checkout), or questions (use ask_eveoy). Cost: free. Latency: under 1s. Notifies the Eveoy team that a demo was requested.

Parameters3

contact_name	string	optional	Name of the person requesting the demo — prefills the booking page and tells the Eveoy team who is coming.
work_email	string	optional	Work email of the requester — prefills the booking page and lets the team follow up if the booking is not completed.
company_name	string	optional	Company or brand the demo is for. Optional if capture_profile was called first.

Raw schema

{
  "type": "object",
  "properties": {
    "contact_name": {
      "description": "Name of the person requesting the demo — prefills the booking page and tells the Eveoy team who is coming.",
      "type": "string",
      "minLength": 1,
      "maxLength": 80
    },
    "work_email": {
      "description": "Work email of the requester — prefills the booking page and lets the team follow up if the booking is not completed.",
      "type": "string",
      "maxLength": 254,
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    },
    "company_name": {
      "description": "Company or brand the demo is for. Optional if capture_profile was called first.",
      "type": "string",
      "minLength": 1,
      "maxLength": 120
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

request_human

Hand off to a human on the Eveoy team and flag the conversation for follow-up. Use this when the user wants to: - Talk to a person or a sales rep (not just book a demo slot) - Get help the other tools cannot give - Escalate a question or ask for a callback Trigger phrases: "talk to a human", "connect me with someone", "I need a person", "have someone call me", "escalate this". Returns: { ok, note } — confirmation the Eveoy team was notified. Do NOT use this for: booking a demo slot (use book_demo), pricing (use get_pricing), or general questions (use ask_eveoy). Cost: free. Latency: under 1s. Notifies the Eveoy team (high-intent).

Parameters3

reason	string	optional	Why you want a human, or what you need help with.
work_email	string	optional	Email for the Eveoy team to reach you.
contact_name	string	optional	Your name.

Raw schema

{
  "type": "object",
  "properties": {
    "reason": {
      "description": "Why you want a human, or what you need help with.",
      "type": "string",
      "maxLength": 500
    },
    "work_email": {
      "description": "Email for the Eveoy team to reach you.",
      "type": "string",
      "maxLength": 254,
      "format": "email",
      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    },
    "contact_name": {
      "description": "Your name.",
      "type": "string",
      "minLength": 1,
      "maxLength": 80
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

README.md8 KBView on GitHub

Eveoy MCP

Marketing was always a bet. We made it a sure thing.

Real customers · in real stores · from any AI.

The official Eveoy MCP server — a knowledgeable Eveoy associate any AI agent can install. It's here to help and educate first, not to sell. Through one endpoint an agent can learn what Eveoy is, get an exact quote, save the brand it represents, and — when ready — order verified in-store customer visits end to end, anonymously, no sign-in.

You don't pay for tokens. You don't pay for clicks. You don't pay for hope. You pay $24.99 per real customer who walks into your store, spends 10+ minutes, completes your tasks, and brings back 2 authentic photos to prove it (and buys at your register on purchase visits). No-shows are 100% refunded.

Built as a native Cloudflare Worker (McpAgent + Durable Objects). Registry: com.eveoy/mcp (v1.1.1).

Endpoint https://mcp.eveoy.com/mcp · Streamable HTTP (MCP spec 2025-06-18) · legacy SSE at /sse

Humans: mcp.eveoy.com is an agent endpoint. A browser that lands on /, /index.html, or /mcp (Accept: text/html) is 302-redirected to the human-facing page at www.eveoy.com/mcp. Agents (Accept */*, application/json, text/event-stream) are never redirected, and static/discovery paths (/llms.txt, /robots.txt, /.well-known/*, /info.json, /health, POST /mcp, /sse) pass through untouched.

Add it to your AI

Remote, no auth — connects immediately. mcp-remote is not needed.

Client	One-line setup
Claude.ai / Claude Desktop	Settings → Connectors → Add custom connector → paste `https://mcp.eveoy.com/mcp`.
Claude Code	`claude mcp add --transport http eveoy https://mcp.eveoy.com/mcp`
ChatGPT	Settings → Connectors → Add → paste the URL (developer mode).
Cursor	`.cursor/mcp.json` → `{"mcpServers":{"eveoy":{"url":"https://mcp.eveoy.com/mcp"}}}`
VS Code (Copilot)	`.vscode/mcp.json` → `{"servers":{"eveoy":{"type":"http","url":"https://mcp.eveoy.com/mcp"}}}`
Windsurf	`mcp_config.json` → `{"mcpServers":{"eveoy":{"serverUrl":"https://mcp.eveoy.com/mcp"}}}`
Lovable	Connectors → Chat connectors → New MCP server → paste the URL → Add.

What it does

11 tools · 5 prompts · 10 resources. One endpoint. Just receipts. The Worker is a thin adapter — read/static tools run at the edge; the rest call Eveoy's Supabase edge functions ("the brain") with the publishable anon key only. Every interaction is logged to Eveoy's CRM (Zoho, via a Supabase crm-log edge function); high-intent events — profile captured, demo booked, checkout started, order paid, human requested — also ping the team in Zoho Cliq.

Learn

ask_eveoy — any question about Eveoy (proxies the live brain; public-only KB fallback)
get_case_studies — outcome stories (aggregate; no client PII)
list_industries — the 16 B2C sectors Eveoy serves
get_app_link — canonical app / install links

Quote

get_pricing — exact price; mirrors eveoy.com/order ($24.99/customer · $999 Starter pilot for 40 customers)

Buy & convert

capture_profile — save the brand the agent represents (→ Zoho Lead)
start_checkout — returns a Stripe Checkout URL directly · anonymous, no sign-in (→ Zoho Deal)
book_demo — book a live walkthrough
subscribe_newsletter — newsletter opt-in

Status & handoff

check_order_status — masked order lookup by session id
request_human — escalate to a person (→ Zoho Task + Cliq)

Prompts — /recommend_pilot · /eveoy_price_quote · /eveoy_objection_handle · /pitch_for_role · /pilot_scope_intake

Resources — 10 read-only KB docs at eveoy://kb/* (overview, product, pricing, comparison, sectors, why-now, ugc-ripple, validation, directory, and for-agents — the end-to-end how-to-buy guide written for agents).

Contracts: docs/API_CONTRACTS.md. Backend integration + current state: docs/NOTES_FOR_LOVABLE.md.

What it won't say

This server speaks public Eveoy only. A versioned classifier in src/classifier/denylist.ts blocks every internal pattern — financials, roadmap, partner names, sales playbook, secrets — before it can leave the server, and the same assertPublic gate (src/classifier/public-only.ts) runs on every CRM payload. If a question can't be answered from the public set, the response is "That detail isn't publicly available — email brad@eycrowd.com for more."

Architecture (Cloudflare-native)

code

mcp.eveoy.com  (Worker Custom Domain)
   │
   ▼  one Worker (src/index.ts)
 ├─ "/" → Lovable's mcp-landing edge fn (marketing source of truth)
 ├─ /info.json            live tool list + pricing + industries
 ├─ static assets (public/)      /privacy, icons, /.well-known/server-card.json,
 │    served free from the edge    robots.txt, sitemap.xml, llms.txt, eveoy.dxt
 ├─ EveoyMCP  (McpAgent + Durable Object + SQLite)
 │    wraps the official SDK McpServer; per-session state (profile, session_id) + SSE resumability
 │    serve('/mcp') = Streamable HTTP · serveSSE('/sse') = legacy
 │    start_checkout → anonymous agent path on create-checkout-session (no sign-in)
 ├─ src/integrations/crm.ts → crm-log edge fn (Zoho Activity/Lead/Deal + Cliq) · fire-and-forget
 ├─ KV (CACHE)            15-min eveoy.com fetch cache (not used for rate counting)
 └─ Rate Limit binding    per-session + per-IP soft limit (60 / 60s)

The deterministic core (src/lib/pricing.ts, src/classifier/*, src/industries.ts, src/mcp/schemas.ts, src/knowledge/*, tool/prompt bodies) is platform-agnostic — no Cloudflare imports. The Worker shell (src/index.ts) and src/config.ts are the only platform-coupled files.

Local development

bash

npm install
cp .dev.vars.example .dev.vars      # set IP_HASH_SALT, SUPABASE_ANON_KEY
npm run dev                         # wrangler dev → http://localhost:8787 (workerd)
npm run inspect                     # MCP Inspector against localhost:8787/mcp

Quality gates

bash

npm run typecheck                   # tsc --noEmit
npm test                            # 110 tests across 20 files (vitest)
npm run lint:descriptors            # tool-descriptor integrity gate
npx wrangler deploy --dry-run --outdir dist   # bundle validation, no login

The classifier suite must stay at 100% — every internal pattern from the about-eveoy KB has a deny case. The handshake suite asserts every tool follows the canonical description template, carries zero anti-slop tokens, and that server.json + dxt/manifest.json descriptions stay ≤100 chars.

Deploy

See docs/CLOUDFLARE_DEPLOY.md for the full runbook (account, KV namespace, secrets, custom domain, DNS zone, registry publish). Short version:

bash

wrangler login
wrangler kv namespace create CACHE          # paste the id into wrangler.jsonc
wrangler secret put IP_HASH_SALT
wrangler secret put SUPABASE_ANON_KEY
wrangler deploy

Security posture

Streamable HTTP per MCP spec 2025-06-18
Origin allowlist + Host pinning + HSTS + CORS in the Worker fetch gate (src/index.ts)
Zod .strict() schemas on every tool — no extra params; inputs mirror eveoy.com/order
Anonymous by design — agents read and buy without sign-in; no OAuth friction on the path to purchase
Per-session + per-IP soft rate limit (Cloudflare Rate Limit binding), fail-open on limiter error
Fail-closed public-only output classifier — every response and every CRM payload passes assertPublic
No tokens or secrets ever logged; IPs HMAC-hashed with a rotating salt
Session state isolated per Durable Object

Distribution

mcp/server.json — Official MCP Registry (com.eveoy/mcp, v1.1.1)
smithery.yaml — Smithery · dxt/manifest.json — Claude Desktop .dxt (npm run build:dxt → served at /eveoy.dxt)
/.well-known/mcp/server-card.json · /llms.txt · /sitemap.xml · /robots.txt
Listed on mcp.so, awesome-mcp-servers, Glama, PulseMCP, and Smithery. Packets + status: docs/DIRECTORY_SUBMISSIONS.md.

License

Install

Tools (11)

ask_eveoyget_pricinglist_industriesget_app_linkget_case_studiescheck_order_statussubscribe_newsletterstart_checkout

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.eveoy.com/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.eveoy.com/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

Eveoy MCP Server (com.eveoy/mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

ask_eveoy

get_pricing

list_industries

get_app_link

get_case_studies

check_order_status

subscribe_newsletter

start_checkout

capture_profile

book_demo

request_human

Eveoy MCP

Add it to your AI

What it does

What it won't say

Architecture (Cloudflare-native)

Local development

Quality gates

Deploy

Security posture

Distribution

License

Install

Remote endpoint

Related servers