Event Presence Index MCP Server
Map a company domain to the third-party conferences and trade shows it publicly says it attends via the Apify Event Presence Index actor.
Call the
map_company_event_presencetool with a requireddomain.Optionally provide
company_nameto improve matching when the brand differs from the domain.Optionally set
years(default2025,2026); events outside the set are still returned and flagged.Optionally include the company’s own conference separately with
include_own_events(default true); it is never mixed into attendance.Tune
max_queries(1–5, default 2) andskipCache(false/true, defaultfalse) for fresh vs 21-day cached results.Read the flat output row and use
coverage,fetch_status, andqueries_failedto interpret empty results.Requires
APIFY_TOKEN, consumes Apify credits, and is read-only; it is not an events database or exhibitor list.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Event Presence Index MCP Server What events does openai.com attend?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Event Presence Index MCP Server
MCP server for the Mamba Labs Event Presence Index actor on Apify.
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.
Install
npx -y @mambalabsdev/mcp-event-presence-indexClaude Desktop
{
"mcpServers": {
"mamba-event-presence-index": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-event-presence-index"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get an Apify token at console.apify.com/account/integrations.
Related MCP server: AI Tooling Detector MCP Server
Tool
map_company_event_presence
Company domain in, the events that company says it attends out.
Input | Type | Required | Notes |
| string | yes | A single company domain, for example 6sense.com. Protocol and path are stripped. |
| 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. |
| 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 |
| boolean | no | Reports whether the company runs its own conference as a separate field. It is never mixed into the attendance list. Default |
| enum | no |
|
| enum | no |
|
| number | no | Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit to rely on the maximum cost per run set in Apify. |
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.
Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.
Event | Price (USD) |
Company analyzed ( | 0.005 |
Actor Start ( | 0.00005 |
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.
Source
The actor is on the Apify Store. This wrapper is MIT licensed.
Built by Mamba Labs
Available Tools
1 toolmap_company_event_presenceMap Company Event PresenceARead-onlyIdempotent
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. The search runs against the company's own domain, which is what stops a brand collision returning another company's events. The company's own conference is reported separately and is never mixed into the attendance list. It finds events for roughly 2 companies in 10, and an empty row is an honest empty row rather than a guess: read coverage, fetch_status and queries_failed to tell a company with no published events apart from a search that could not see. Events dated outside the years you ask for are still returned and flagged, so filter on event year rather than assuming the input filtered for you. This is not an events database and not an exhibitor list: it takes a company and reports what that company publishes. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: domain (required), years, skipCache, max_queries, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusion with other tools. The tool's purpose is clearly described, distinguishing it from any potential alternative.
The single tool uses a clear verb_noun naming convention, which is consistent and descriptive.
With only one tool, the server feels minimal, but the tool is comprehensive in its single responsibility. The count is borderline thin for a typical MCP server.
The tool covers its stated purpose of mapping company event presence, including handling edge cases such as coverage status and query failures. There are no obvious missing operations within its read-only scope.
Maintenance
Related MCP Connectors
Company data, tech stack, DMARC/SPF, ABN, hiring and Shopify signals by domain via Apify.
Open jobs and hiring changes for any company, from its domain. Runs on Apify.
B2B company domain discovery, web SERP footprint & firmographic enrichment API for AI agents.
Domain to public business contacts: role emails, phones, socials, company name and address.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables querying and retrieving structured event data from the Informa Connect event directory, with support for various filters, pagination, and speaker extraction.9-
- AlicenseAqualityBmaintenanceEnables AI clients to analyze any company domain and determine its AI maturity tier (commercialized, deployed, declared, or none) with supporting evidence, via a single tool backed by an Apify actor.188 npmMIT
- AlicenseAqualityBmaintenanceExtracts people (names and titles) from a company's team, leadership, or about page given a domain. Uses Apify to crawl and return structured data, with optional filters for seniority and email inclusion.172 npmMIT
- AlicenseAqualityBmaintenanceMCP server for the Mamba Labs GitHub Organization Signal Scanner actor on Apify. Resolve a company domain to its GitHub organization with repo, language and activity signals.186 npmMIT