Find the conferences and trade shows a company publicly says it attends, from its domain.
Event Presence Index MCP Server
The com.mambabuilt/mcp-event-presence-index MCP server finds conferences and trade shows that a company publicly states it attends, using its domain. It is identified as “Event Presence Index MCP Server” in the provided readme excerpt, and is listed in the MCP registry.
🛠️ Key Features
Publicly stated event discovery
Event types: conferences and trade shows
Input basis: company domain
Server slug: com-mambabuilt/mcp-event-presence-index
🚀 Use Cases
Retrieve a company’s listed event presence from its domain
Compile conferences and trade shows for research or prospecting
⚡ Developer Benefits
Domain-based event lookup
Provides an events-oriented result set grounded in public statements
⚠️ Limitations
Scope is limited to conferences and trade shows the company publicly says it attends
No tool names, counts, or additional capabilities were included in the provided data
Give it a company domain. It returns the third party conferences and trade shows that company publicly says it attends, with a year for each where one can be resolved, as one flat row. Its own conference is reported separately and never mixed into the attendance list.
Company domain in, the events that company says it attends out.
Input
Type
Required
Notes
domain
string
yes
A single company domain, for example 6sense.com. Protocol and path are stripped.
company_name
string
no
Improves matching when the brand differs from the domain stem, for example Gong for gong.io. Derived from the domain when left empty.
years
string
no
Comma separated, for example 2025,2026. Events dated outside this set are still returned and flagged. Sent as a string so it works from Clay. Default 2025,2026.
include_own_events
boolean
no
Reports whether the company runs its own conference as a separate field. It is never mixed into the attendance list. Default true.
max_queries
enum
no
1 to 5. 2 is the measured sweet spot: search engines refuse a third query from the same container almost every time. Sent as a string so it works from Clay. Default 2.
skipCache
enum
no
false uses the 21 day result cache, true forces a fresh look. Default false.
Reading the output
It finds events for roughly 2 companies in 10, and every event it returns is real. An empty row is an honest empty row rather than a guess, so read coverage, fetch_status and queries_failed to tell a company that publishes nothing apart from a search that could not see.
Events dated outside the years you asked for are still returned and flagged, so filter on the event year rather than assuming the input filtered for you.
Billing
You are charged per company analyzed, plus a small actor start fee. A repeat run inside the 21 day cache window costs nothing new.
Pricing is on the actor's Apify page. Running this server consumes Apify credits.
What this server does and does not do
It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.
This is not an events database. It is not a ticketing feed, not a directory of conferences, and not a list of everyone exhibiting at a show. It takes a company and reports what that company publishes about the events it attends.
Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.
