Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Nevent MCP

REMOTE · MCP.NEVENT.AI · 2 COMPONENTS

Talk to your live-events CRM (campaigns, analytics, paid ads, segments) in Claude and ChatGPT.

0 this week 80 Trust /100

Last scanned (23 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security66
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 14916 tokens (~236/item across 63 items; 63 tools + 0 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety92
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "nevent_segment_execute" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “nevent_quote_campaign” rewrote its description, which is the text the model reads security
    • Tool “nevent_schedule_campaign” rewrote its description, which is the text the model reads security
    • Tool “nevent_update_template” rewrote its description, which is the text the model reads security
    • Tool “nevent_reset_tenant” is now declared destructive security
    • Schema quality: 12757 → 14916 ▼ functional
    • New tool “nevent_list_events” functional
    • New tool “nevent_event_sales_provenance” functional
    • New tool “nevent_get_campaign_deliverability” functional
    • New tool “nevent_get_campaign_unsubscribes” functional
    • “nevent_help” reworded the description of “topic” cosmetic
    • “nevent_quote_campaign” reworded the description of “channel” cosmetic
  • 26 Oct 26 0
    • Stability: fail → pass ▲ security
  • 10 Oct 26 +1
    • DNSSEC: fail → pass ▲ security
  • 28 Sept 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 Sept 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “nevent_analytics_query” rewrote its description, which is the text the model reads security
    • Tool “nevent_campaign_report” rewrote its description, which is the text the model reads security
    • “nevent_campaign_report” added a required parameter “month”, so existing callers break ▼ functional
    • “nevent_campaign_report” added a required parameter “year”, so existing callers break ▼ functional
    • “nevent_campaign_report” dropped the required parameter “campaignId” ▼ functional
    • “nevent_campaign_report” dropped the optional parameter “timeRange” cosmetic
  • 25 Sept 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
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 10 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “nevent_segment_preview” rewrote its description, which is the text the model reads security
    • Tool “nevent_segment_execute” rewrote its description, which is the text the model reads security
    • Tool “nevent_create_segment” rewrote its description, which is the text the model reads security
    • “nevent_segment_preview” reworded the description of “definition” cosmetic
    • “nevent_update_segment” reworded the description of “definition” cosmetic
    • “nevent_segment_execute” reworded the description of “definition” cosmetic
    • “nevent_create_segment” reworded the description of “definition” cosmetic
Diagnostics

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 4 Nov 2026 · Probed https://mcp.nevent.ai/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.nevent.ai CN=Amazon RSA 2048 M04,O=Amazon,C=US 21 Aug 2026 6 Mar 2027 RSA 2048 SHA256-RSA e35681722decc1b7209ba6e4ecddf69
SANs: *.nevent.ai, nevent.ai
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.nevent.ai. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
nevent.ai. present 30403 13 Verified
mcp.nevent.ai. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains
content-security-policy default-src 'self';script-src 'self';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;font-src 'self' https://fonts.gstatic.com;img-src 'self' data: https://admin.nevent.es https://avatars.slack-edge.com https://upload.wikimedia.org;connect-src 'self';frame-ancestors 'none';form-action *;base-uri 'self';object-src 'none';script-src-attr 'none';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nevent.ai/ Verified 200
http (plaintext) http://mcp.nevent.ai/ HTTPS enforced
MCP tools · 63 exposed · ~13,782 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
nevent_quote_campaign ~543

Estimate the credit cost and eligible audience of a campaign BEFORE sending it. Read-only pre-flight check against nev-api POST /campaigns/quote — it never debits credits and never sends. Call this after nevent_create_campaign and before nevent_schedule_campaign: scheduling a campaign the tenant cannot afford fails at send time with a 402. Returns cost (credits required), available (credits in the pool), missing (shortfall), recipientCount, affordable (boolean — the gate to check), blocked, unlimited, and an audience block with uniqueAudience, estimatedEligible per channel, eligibleAnyChannel and emailExclusions (no_email / invalid_email / opt_out / unknown). The audience block is null when the estimate could not be computed: a channel mix that combines WhatsApp with another channel (for example EMAIL_AND_WHATSAPP or ALL_CHANNELS), more than 20 segments, a WhatsApp selection too large for the segmentation budget, or a data-api failure/timeout — cost and recipientCount are still valid in that case. A WHATSAPP_ONLY quote IS estimated (by nev-api, with the same eligibility the send applies: consent of the tenant or its descendants, opt-outs, Meta stops and cooldowns, one recipient per phone) and fills extra audience fields: estimatedEligible.whatsapp (recipients that will receive the message), whatsappExclusions (why audience users do NOT receive it, one count per reason) and whatsappConsentSources (list of {tenantId, tenantName, relation SELF|DESCENDANT, recipients}: whose WhatsApp consent authorises the recipients, sending tenant first). Those three are null/absent for every other channel. Use segment_ids from nevent_list_segments; omit them to quote the full addressable audience. Set transactional=true only for genuinely transactional sends (order confirmations, ticket delivery) — it estimates against the TRANSACTIONAL consent mode, which reaches recipients who opted out of marketing.

NameTypeReqDescription
channelstringyesDelivery channel to quote (nev-api CommunicationChannel enum). Legacy values EMAIL/SMS/WHATSAPP are accepted and mapped to the _ONLY variants. WHATSAPP_ONLY returns a WhatsApp-specific audience estim…
segment_idsarray–Segment IDs to quote (optional, max 20). Omit to quote the full addressable audience for the channel. More than 20 segments makes the backend skip the audience estimate.
transactionalboolean–Whether this is a transactional campaign (default false). Transactional uses the TRANSACTIONAL consent mode for the audience estimate, which reaches recipients who have opted out of marketing.

No output schema declared.

No examples provided.

nevent_rename_template ~136

Rename an email template without modifying its content (lightweight — no re-render triggered). Use after nevent_clone_template to give the clone a proper name, or to reorganize existing templates. Returns the updated template with the new name. Next step: nevent_update_template to change content, or nevent_preview_template to validate rendering.

NameTypeReqDescription
namestringyesThe new name for the template. Must be between 1 and 255 characters. Duplicate names are allowed by the API.
template_idstringyesThe ID of the email template to rename. Use nevent_list_templates to get valid template IDs.

No output schema declared.

No examples provided.

nevent_reset_tenant ~93

Restore the original tenant context set at session start. ALWAYS call this after cross-tenant queries (nevent_switch_tenant) to avoid leaving your SUPERADMIN account pointing to another tenant. For SUPERADMIN users, tenant switches PERSIST in the user record in the database — this tool reverses that. For OWNER/ADMIN/STAFF users, this resets to the session's home tenant. No parameters needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

nevent_schedule_campaign ~306

Schedule an existing DRAFT campaign for delivery at a specific ISO-8601 datetime. IMPORTANT: this is a DESTRUCTIVE action — the campaign will be queued for sending to real contacts. You MUST set confirmed=true in the call, which requires explicit user consent. Call nevent_get_campaign first to verify the draft content and recipient segment. scheduled_time must be in the future (ISO-8601, e.g. 2025-06-01T10:00:00Z). The campaign transitions from DRAFT to SCHEDULED status on success. If the sender identity or sending domain is not eligible, nev-api refuses with 409 SENDER_INELIGIBLE and the campaign stays DRAFT: check nevent_get_sending_profile, fix the sender or domain, then schedule again. A scheduled campaign can also be paused later by the same check (status PAUSED, pause code AUTO_PAUSED_SENDER_INELIGIBLE).

NameTypeReqDescription
campaign_idstringyesCampaign ID to schedule (must be in DRAFT status)
confirmedbooleanyesMust be the literal value true to proceed. Set confirmed=true to confirm you want to schedule this campaign for sending.
scheduled_timestringyesISO 8601 datetime for scheduled send (must be in the future). Example: "2026-05-01T10:00:00Z" or "2026-05-01T10:00:00+02:00"

No output schema declared.

No examples provided.

nevent_segment_execute ~188

Execute a segment definition and retrieve matching contacts with pagination. SEMANTICS: criteria in the same stanza are OR-combined — a fan matches the stanza if ANY criterion matches. Stanzas are AND-combined — a fan must match EVERY stanza. To require A AND B, put them in separate stanzas; to accept A OR B, put both in the same stanza.

NameTypeReqDescription
definitionobjectyesSegment DSL. Criteria in the same stanza are OR-combined: a fan matches the stanza if ANY criterion matches. Stanzas are AND-combined: a fan must match EVERY stanza. To require A AND B, put them in s…
pagenumber–Zero-based page index (default 0)
page_sizenumber–Results per page (max 100, default 20)

No output schema declared.

No examples provided.

nevent_segment_preview ~361

Preview estimated audience size for a segment definition without saving it. Returns fan count and sample contacts. SEMANTICS: criteria in the same stanza are OR-combined — a fan matches the stanza if ANY criterion matches. Stanzas are AND-combined — a fan must match EVERY stanza. To require A AND B, put them in separate stanzas; to accept A OR B, put both in the same stanza. MANDATORY RULES: (1) ENTITY operators (is/is_not) accept a single string OR an array of strings (e.g. value: "EVENT_ID" or value: ["EVENT_1","EVENT_2"]). (2) Do NOT include modifiers unless specifically asked for frequency or recency filtering. If included, time_range.value MUST be > 0. KNOWN LIMITATION: Do NOT combine attendance criteria (attended_event, ticket_type) with spending criteria (total_spent, ticket_spent, cashless_recharge_amount) in the SAME stanza. Put them in SEPARATE stanzas. Example — attended EVENT_ID AND spent >= 200, because a fan must match EVERY stanza: { stanzas: [{ criteria: [{ criterion_id: "attended_event", operator: "is", value: "EVENT_ID" }] }, { criteria: [{ criterion_id: "total_spent", operator: "gte", value: 200 }] }] }.

NameTypeReqDescription
definitionobjectyesSegment DSL. Criteria in the same stanza are OR-combined: a fan matches the stanza if ANY criterion matches. Stanzas are AND-combined: a fan must match EVERY stanza. To require A AND B, put them in s…

No output schema declared.

No examples provided.

nevent_segmentation_criteria ~28

List all available audience segmentation criteria including their IDs, operators, and value types.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

nevent_send_test_template ~317

Send a test email of the template to one or more email addresses via SES. Use after nevent_preview_template validates rendering. Test emails carry test indicators in headers and are sent via AWS SES. This call may take up to 60 seconds due to SES delivery. Returns success status, list of recipients the email was sent to, and any error details.

NameTypeReqDescription
emailsarrayyesList of email addresses to send the test email to. Each entry must be a valid email address. Minimum 1, maximum 10 recipients. Example: ["qa@example.com", "dev@company.com"].
parametersobject–Optional custom parameters for merge-tag substitution in the test email. Key-value pairs where keys match merge tag names. Example: {name: "Juan", city: "Madrid"}. When provided, overrides sample use…
sample_user_emailstring–Optional user email within the active tenant for merge-tag personalization. Ignored when sample_user_id is also provided.
sample_user_idstring–Optional user ID for merge-tag personalization in the test email. When provided, {{name}}, {{email}} and custom fields are resolved from this user's profile. Takes priority over sample_user_email.
subjectstring–Optional subject line for the test email. Omit to use the default subject from the template.
template_idstringyesThe ID of the email template to send as a test. Use nevent_list_templates to discover valid template IDs.

No output schema declared.

No examples provided.

nevent_switch_tenant ~216

Switch the active tenant for this session. All subsequent queries (analytics, segments, campaigns, paid media) will use the specified tenant's data. SUPERADMIN: this mutates your user record in the database — the switch PERSISTS. Always call nevent_reset_tenant when cross-tenant work is done to avoid leaving your account pointing at another tenant. OWNER/ADMIN/STAFF: session-scoped only; you can only switch to tenants in your hierarchy subtree (max 3 levels deep). Use nevent_list_tenants to discover available tenant IDs.

NameTypeReqDescription
tenant_idstringyesThe tenant ID to activate for this MCP session. All subsequent analytics, segmentation, campaign, and paid media queries will use this tenant's data. Use nevent_list_tenants to discover available ten…

No output schema declared.

No examples provided.

nevent_update_segment ~173

Modify an existing segment's name and/or filter definition. Call this after nevent_get_segment to inspect the current definition before changing it. At least one of name or definition must be provided. After update, call nevent_segment_preview to confirm the new audience count before scheduling a campaign.

NameTypeReqDescription
definitionobject–Replacement segment DSL. The full definition is replaced when provided. Criteria in the same stanza are OR-combined: a fan matches the stanza if ANY criterion matches. Stanzas are AND-combined: a fan…
namestring–New human-readable name for the segment. Omit to leave unchanged.
segment_idstringyesIdentifier of the segment to update. Use nevent_list_segments to get valid segment IDs.

No output schema declared.

No examples provided.

nevent_update_short_url ~304

Update an existing short URL's configuration. Only provided fields are changed — omitted fields remain unchanged. Changes apply immediately. Use after nevent_list_short_urls to get the `id`. Supported updates: title, expiresAt (pass null to remove expiration), isActive (true/false), tags (replaces existing), metadata (replaces existing), longUrl (changes redirect destination). Returns the updated ShortUrlDTO. WRITE operation — requires STANDARD or FULL operation mode. In READ_ONLY mode this tool returns an operation_not_permitted error immediately without making any API call.

NameTypeReqDescription
expiresAt––New expiration date/time (ISO 8601). Pass null to remove an existing expiration and make the link permanent. Omit this field entirely to leave expiration unchanged.
idstringyesMongoDB ObjectId of the short URL (24 hex characters). Obtain from nevent_list_short_urls response field "id".
isActiveboolean–Activate (true) or deactivate (false) the short URL. Deactivated links stop redirecting immediately.
longUrlstring–New destination URL. Changes where existing links redirect to — takes effect immediately.
metadataobject–New metadata object. Replaces (not merges) the existing metadata.
tagsarray–New tag list. Replaces (not merges) the existing tags.
titlestring–New descriptive title (max 200 chars). Replaces the existing title.

No output schema declared.

No examples provided.

nevent_update_template ~278

Update an existing email template: change the name, MJML/HTML content, or tags. Call nevent_get_template first to inspect the current version before modifying. At least one of name, content, or tags must be provided. Note: updating a template does NOT retroactively change campaigns already sent with it. If the template changed since you read it (another editor, the image processor or an AI edit), nev-api answers 409 template_edit_conflict and nothing is written: re-read it with nevent_get_template, re-apply your change on the current content and call this tool again (it never retries by itself).

NameTypeReqDescription
formatstring–New template format: "html" or "mjml". Omit to leave unchanged.
html_bodystring–New raw HTML content for the template. Omit to leave unchanged.
mjml_bodystring–New MJML source code for the template. Omit to leave unchanged.
namestring–New human-readable name for the template. Omit to leave unchanged.
tagsarray–Replacement list of tags. The full tag list is replaced when provided. Omit to leave existing tags unchanged.
template_idstringyesIdentifier of the template to update. Use nevent_list_templates to get valid template IDs.

No output schema declared.

No examples provided.

nevent_upload_image ~288

Upload an image to the Nevent media library and get a CDN URL. Accepts base64-encoded images as a data URL (data:image/png;base64,...) or as raw base64 with an explicit mimeType. Returns a destinationUrl (CloudFront CDN URL) that can be used directly in <img src="..."> inside email template HTML. Maximum decoded size: 5 MB. Upload the image, then reference the returned destinationUrl in nevent_update_template or nevent_create_template HTML content.

NameTypeReqDescription
imageNamestring–Optional file name for the uploaded resource (e.g. "event-banner.png"). When omitted, a name is generated from the upload timestamp.
mimeTypestring–MIME type of the image, e.g. "image/png" or "image/jpeg". Required when source is raw base64 (no data URL prefix). Ignored when source is a data URL (MIME type parsed from prefix). Common values: ima…
sourcestringyesBase64-encoded image. Two accepted forms: 1. Data URL: "data:image/png;base64,<base64data>" — MIME type parsed from prefix. 2. Raw base64 string — mimeType parameter required. Maximum decoded size: 5…

No output schema declared.

No examples provided.

Install

How do I install the Nevent MCP server?

Nevent MCP is a hosted endpoint at https://mcp.nevent.ai/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.nevent.ai

# add to Claude Code
claude mcp add --transport http nevent-dev-mcp-nevent 'https://mcp.nevent.ai/'
Common questions

What is the Nevent MCP server?

Nevent MCP is listed in the public MCP registry as io.github.nevent-dev/mcp-nevent. Talk to your live-events CRM (campaigns, analytics, paid ads, segments) in Claude and ChatGPT. This page covers its hosted endpoint (https://mcp.nevent.ai/).

Is the Nevent MCP server safe to use?

Nevent MCP scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Nevent MCP server expose?

Nevent MCP exposes 63 tools: nevent_analytics_query, nevent_analytics_capabilities, nevent_analytics_table_schema, nevent_analytics_filter_values, nevent_campaign_report, and 58 more. Their descriptions and schemas cost roughly 13,782 tokens of context every time the server is loaded.

Does the Nevent MCP server require authentication?

No. We connected to Nevent MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Nevent MCP server still maintained?

Nevent MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.