[pggalaviz]

Description

Adds EventSend to the Model Context Protocol Registry extension's official entries. EventSend routes product events (payments, signups, deploys, errors) to Slack, Discord, Telegram, webhooks and push; its official hosted MCP server lets an assistant read those events, per-customer timelines, delivery outcomes, daily stats and quota. All 9 tools are read-only.

• Endpoint: https://eventsend.io/mcp (Streamable HTTP), set as remoteUrl for a direct connection in Raycast, with the same mcp-remote fallback as the other hosted entries
• Auth: OAuth 2.1 with dynamic client registration and PKCE, no API key to paste; free plan available
• Docs: https://eventsend.io/docs/mcp
• Official MCP Registry: io.eventsend/eventsend

Changes: one entry in OFFICIAL_ENTRIES (placed alphabetically between Edgepedia and EvoLink), the matching README table row, and a CHANGELOG entry using {PR_MERGE_DATE}.

This PR was prepared with Claude Code at the request of the submitter (EventSend's developer).

Screencast

Data-only change: one registry entry, no new commands or UI.

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast: not run locally for this data-only change; the entry mirrors the shape of existing hosted entries, and CI will build it
• I checked that files in the assets folder are used by the extension itself (no assets added)
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool (no README assets added)

🤖 Generated with Claude Code

[raycastbot]

Thank you for your contribution! 🎉

🔔 @thomaspaulmann @nagauta @pernielsentikaer @porenes you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="add-eventsend"
FORK_URL="https://github.com/pggalaviz/extensions.git"
EXTENSION_NAME="model-context-protocol-registry"
REPO_NAME="extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The change reaches users browsing or installing the official MCP registry.

Replace the changelog date with {PR_MERGE_DATE} before merging to meet the repository requirement.

Findings

1.  Changelog date is fixed ▶

Fix with agent prompt

### Issue 1
extensions/model-context-protocol-registry/CHANGELOG.md:3
The new heading uses `2026-10-28`, but the repository requires `{PR_MERGE_DATE}` in new changelog headings. Replace the fixed date before merging so the release gets its actual merge date.

```suggestion
## [Add EventSend MCP Server] - {PR_MERGE_DATE}
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Adds EventSend to the official MCP registry.

• The official registry now lists EventSend's read-only event server.

_{Reviews (3) · Last reviewed commit: "Update CHANGELOG.md" · Reviewed by Greptile}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/raycast/model-context-protocol-registry

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@pggalaviz).

Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.

[greptile-apps]

Changelog date is fixed

The new heading uses 2026-10-28, but the repository requires {PR_MERGE_DATE} in new changelog headings. Replace the fixed date before merging so the release gets its actual merge date.

Suggested change

	## [Add EventSend MCP Server] - 2026-10-28
	## [Add EventSend MCP Server] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE} placeholder in titles, be placed at the top of the file, and maintain descending version order. Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/model-context-protocol-registry/CHANGELOG.md
Line: 3

Comment:
**Changelog date is fixed**

The new heading uses `2026-10-28`, but the repository requires `{PR_MERGE_DATE}` in new changelog headings. Replace the fixed date before merging so the release gets its actual merge date.

```suggestion
## [Add EventSend MCP Server] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}` placeholder in titles, be placed at the top of the file, and maintain descending version order.  Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... ([source](https://app.greptile.com/raycast/-/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.