Eveoy — Verified In-Store Foot Traffic ($24.99/customer)
REMOTE · MCP.EVEOY.COM · SCANNED AUG 3
Your Eveoy expert in any AI — learn how it works, get a price, and order real in-store visits.
Available components
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 →
Endpoint Security51
- 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 7 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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4356 tokens (~207/item across 21 items; 11 tools + 10 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 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
- Structured output schemas are declared (64% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.eveoy.com
claude mcp add --transport http com-eveoy-mcp https://mcp.eveoy.com/mcp
[mcp_servers.com-eveoy-mcp] url = "https://mcp.eveoy.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-eveoy-mcp": {
"type": "remote",
"url": "https://mcp.eveoy.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-eveoy-mcp --url https://mcp.eveoy.com/mcp --transport streamable-http
mcp_servers:
com-eveoy-mcp:
url: "https://mcp.eveoy.com/mcp" {
"mcpServers": {
"com-eveoy-mcp": {
"type": "http",
"url": "https://mcp.eveoy.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 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.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 61
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.eveoy.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eveoy.com | CN=WE1,O=Google Trust Services,C=US | 22 Jun 2026 | 21 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | d16130a7f61a510c13ccc7b5ee9c5ae3 |
| SANs: eveoy.com, mcp.eveoy.com, *.mcp.eveoy.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.eveoy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| eveoy.com. | 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; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.eveoy.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.eveoy.com/mcp | Inconclusive | 406 |
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.
ask_eveoy Ask about Eveoy ~376
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | — | Buyer persona to tune the answer for. Infer from conversation context — e.g. 'explain to a CFO' → 'cfo'. Use 'general' if unspecified. |
| question | string | yes | 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 c… |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | — |
| audience | string | yes | — |
| sections | array | yes | — |
No examples provided.
book_demo Book an Eveoy demo ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | — | Company or brand the demo is for. Optional if capture_profile was called first. |
| contact_name | string | — | Name of the person requesting the demo — prefills the booking page and tells the Eveoy team who is coming. |
| work_email | string | — | Work email of the requester — prefills the booking page and lets the team follow up if the booking is not completed. |
No output schema declared.
No examples provided.
capture_profile Save your company profile ~322
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_website | string | — | The brand's website URL. |
| company_name | string | yes | The company or brand the agent represents. |
| contact_name | string | — | Primary contact name for follow-up. |
| goals | string | — | What the brand wants from Eveoy (foot traffic, UGC, launches, etc.). |
| locations | integer | — | Number of physical store locations. |
| sector | string | — | Industry sector, from the Eveoy public list. |
| work_email | string | — | Work email — enables team follow-up and a smoother checkout. |
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | — |
| note | string | yes | — |
| ok | boolean | yes | — |
No examples provided.
check_order_status Check Eveoy order status ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | Stripe Checkout session id (cs_...). |
No output schema declared.
No examples provided.
get_app_link Get the Eveoy app ~157
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | yes | — |
| platforms | array | yes | — |
| url | string | yes | — |
No examples provided.
get_case_studies List Eveoy case studies & lookbooks ~299
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | — | Filter to one kind: case_study, lookbook, or playbook. Omit to return all. |
| limit | integer | — | Max items to return (1–100). Omit to return all. |
| Name | Type | Req | Description |
|---|---|---|---|
| archive_url | string | yes | — |
| items | array | yes | — |
| note | string | yes | — |
No examples provided.
get_pricing Get Eveoy pricing ~821
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 [email protected] Cost: free. Latency: <100ms. Read-only.…
| Name | Type | Req | Description |
|---|---|---|---|
| customers_per_location | integer | — | Verified shoppers per store (UI label "Shoppers per location"). Mirrors eveoy.com/order: min 20, max 1000. Default 40 (the "$999 pilot" config). |
| guarantee_type | string | — | 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… |
| locations | integer | — | Number of store locations. Mirrors eveoy.com/order: min 1, max 50. Default 1. |
| shopper_bonus_cents | integer | — | 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… |
| top_sku_price_cents | integer | — | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| bonus_tiers | integer | yes | — |
| customers_per_location | integer | yes | — |
| fee_breakdown | object | yes | — |
| formatted_total | string | yes | — |
| guarantee_type | string | yes | — |
| is_starter_tier | boolean | yes | — |
| locations | integer | yes | — |
| shopper_bonus_cents | integer | yes | — |
| top_sku_price_cents | — | yes | — |
| total_customers | integer | yes | — |
| total_usd | number | yes | — |
| ugc_photos | integer | yes | — |
| unit_price_usd | number | yes | — |
No examples provided.
list_industries List Eveoy industries ~198
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | — |
| industries | array | yes | — |
| notes | string | yes | — |
No examples provided.
request_human Talk to a human ~223
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).
| Name | Type | Req | Description |
|---|---|---|---|
| contact_name | string | — | Your name. |
| reason | string | — | Why you want a human, or what you need help with. |
| work_email | string | — | Email for the Eveoy team to reach you. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | — |
| ok | boolean | yes | — |
No examples provided.
start_checkout Start an Eveoy checkout ~787
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.
| Name | Type | Req | Description |
|---|---|---|---|
| advancedTargeting | — | — | — |
| brand_website | string | — | Brand website URL. Optional if saved via capture_profile. |
| campaign_start_date | string | — | Campaign start date (YYYY-MM-DD, ≥ 14 days out). Required to check out without signing in. |
| customers_per_location | integer | yes | Verified customers per store (20–1000); mirrors eveoy.com/order. |
| guarantee_type | string | — | 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… |
| locations | integer | — | Number of store locations (1–50). |
| phone | string | — | Phone (optional). |
| shopper_bonus_cents | integer | — | 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… |
| top_sku_price_cents | integer | — | 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. |
| work_email | string | — | Work email. Optional if saved via capture_profile. |
| your_name | string | — | Your name. Optional if saved via capture_profile. |
No output schema declared.
No examples provided.
subscribe_newsletter Subscribe to the Eveoy newsletter ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email to subscribe to the Eveoy newsletter. |
No output schema declared.
No examples provided.