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.

AI Event Pro

REMOTE · AIEVENTPRO.ART

AI event and travel planner: dream events, concerts, weddings, conferences and bucket-list trips mad

Available components

+4 this week 71 Trust /100

Last scanned (22 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 549 tokens (~68/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • Tool “get_checkout_link” rewrote its description, which is the text the model reads security
    • Schema quality: 57 → 68 ▼ functional
    • “get_checkout_link” added an optional parameter “accept_terms” cosmetic
    • “get_checkout_link” added an optional parameter “buyer_email” cosmetic
    • “get_checkout_link” added an optional parameter “store_handle” cosmetic
    • “get_checkout_link” reworded the description of “interval” cosmetic
    • “get_checkout_link” reworded the description of “plan” cosmetic
    • Tool “get_checkout_link” changed its title: Checkout link cosmetic
  • 17 Nov 26 +1
    • Tool “get_checkout_link” rewrote its description, which is the text the model reads security
    • Schema quality: 49 → 57 ▼ functional
    • Tool coverage: 50% → 75% ▲ functional
    • “get_checkout_link” reworded the description of “interval” cosmetic
    • “get_checkout_link” reworded the description of “plan” cosmetic
    • Tool “get_checkout_link” changed its title: Checkout link cosmetic
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 −3
    • HSTS header: pass → fail ▼ security
    • Schema quality: 60 → 49 ▲ functional
    • First check of Tool coverage: 50 functional
    • Schema quality: fair → good functional
    • New tool “get_checkout_link” functional
    • New tool “get_company_info” functional
    • New tool “list_pricing” functional
    • New tool “search_site” functional
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 69

    First indexed and scored.

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 21 Nov 2026 · Probed https://aieventpro.art/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aieventpro.art CN=YE2,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 ECDSA 256 ECDSA-SHA384 5fb3c66b0187942950e22db71dfbef8a419
SANs: *.aieventpro.art, aieventpro.art
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aieventpro.art. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
art. DS published 29485, 32002 8, 8 Verified
aieventpro.art. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aieventpro.art/mcp Verified 200
http (plaintext) http://aieventpro.art/mcp HTTPS enforced 301 https://aieventpro.art/mcp
MCP tools · 8 exposed · ~549 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
aieventpro_about ~69

What AiEventPro does and what is free Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://aieventpro.art/pricing"}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

aieventpro_plans ~85

Returns each plan with its USD monthly and annual price and the features the pricing page lists, including monthly AI planning credits. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://aieventpro.art/pricing"}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

aieventpro_pricing ~68

Where prices live and what costs nothing Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://aieventpro.art/pricing"}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_checkout_link ~206

Checkout URL for a plan. With no arguments: the main paid plan. Where the site supports it the URL is a Stripe-hosted Checkout session (created unpaid; a human pays, nothing is charged by this tool). A free plan is only returned when the plan is requested or the company sells nothing else.

NameTypeReqDescription
accept_termsboolean–ONLY where the site requires the buyer to accept its Terms/refund policy before checkout: set true only after the human buyer has read and accepted the policy links the tool lists. Never set it on yo…
buyer_emailstring–only for sites that need the buyer's email or store handle before checkout: the human buyer's own receipt email
intervalstring––
planstring–plan name from list_pricing
store_handlestring–only where the site asks for it (StoreForge): the store handle the buyer chose, 3+ chars a-z 0-9 -

No output schema declared.

No examples provided.

get_company_info ~30

What this company sells, who it is for, and every agent/API entry point. No account needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_pricing ~34

Current plans and prices in USD: plan, interval, amount_usd, currency, what_you_get. No account needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_site ~38

Find pages on this site by keyword; returns url, title and summary.

NameTypeReqDescription
limitinteger––
querystringyeskeywords

No output schema declared.

No examples provided.

usage_get ~19

Usage for the calling key (last 30 days)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the AI Event Pro MCP server?

AI Event Pro is a hosted endpoint at https://aieventpro.art/mcp, 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 · aieventpro.art

# add to Claude Code
claude mcp add --transport http art-aieventpro-aieventpro 'https://aieventpro.art/mcp'
Common questions

What is the AI Event Pro MCP server?

AI Event Pro is an MCP server listed in the public MCP registry as art.aieventpro/aieventpro. AI event and travel planner: dream events, concerts, weddings, conferences and bucket-list trips mad. This page covers its hosted endpoint (https://aieventpro.art/mcp).

Is the AI Event Pro MCP server safe to use?

AI Event Pro scores 71 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 AI Event Pro MCP server expose?

AI Event Pro exposes 8 tools: aieventpro_plans, aieventpro_about, aieventpro_pricing, get_checkout_link, usage_get, and 3 more. Their descriptions and schemas cost roughly 549 tokens of context every time the server is loaded.

Does the AI Event Pro MCP server require authentication?

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

Is the AI Event Pro MCP server still maintained?

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

What did VerifyMCP test on the AI Event Pro MCP server?

VerifyMCP ran 13 checks on AI Event Pro, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.