Is Event Presence Index free?

Yes, Event Presence Index is free to use.

How do I install Event Presence Index?

Event Presence Index is a local plugin. Install it using npm package: @mambalabsdev/mcp-event-presence-index and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Event Presence Index safe to use?

Yes. Event Presence Index passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Event Presence Index need?

Event Presence Index requires the following credentials or environment variables: APIFY_TOKEN. You can find setup instructions on the server detail page.

What AI apps work with Event Presence Index?

Event Presence Index uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Event Presence Index MCP Server

by mambabuilt

Developer ToolsLow Risk10.0Local

Free

Find the conferences and trade shows a company publicly says it attends, from its domain.

About

Find the conferences and trade shows a company publicly says it attends, from its domain.

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (76/76 approved).

11 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

What You'll Need

Set these up before or after installing:

Apify API token from https://console.apify.com/account/integrationsRequired

Environment variable: APIFY_TOKEN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-mambabuilt-mcp-event-presence-index": {
      "env": {
        "APIFY_TOKEN": "your-apify-token-here"
      },
      "args": [
        "-y",
        "@mambalabsdev/mcp-event-presence-index"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

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`.
`max_charge_usd`	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 (`company-analyzed`)	0.005
Actor Start (`apify-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.