com.mambabuilt/mcp-event-presence-index

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-index

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

Tool

map_company_event_presence

Company domain in, the events that company says it attends out.

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.

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