Ray notifications MCP server
io.github.gege-mn/ray-mcpgege-mnstreamable-httpv0.1.0Scanned
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
21 tools: 2 can delete or cancel things, 3 do something that can't be undone, 5 change things and 11 only read.
- Reads private data · 4
- Reads text others write · 5
- Can send data out · 5
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 3 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Ray notifications MCP server can do
The Ray notifications MCP server is published by the GitHub account gege-mn. It has 21 tools. It can delete or cancel things (2 tools: archive_template and delete_webhook), do things that cannot be undone, such as sending, paying or publishing (send_notification, publish_template and test_send_template) and create or change data (5 tools: create_template, update_template_draft, unarchive_template, create_webhook and 1 more). 11 tools only read.
4 tools read private data (get_usage, list_templates, get_click_stats and 1 more); 5 tools bring in text other people can write (send_notification, list_templates, test_send_template and 2 more); 5 tools can send data out of your system (send_notification, publish_template, test_send_template and 2 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
21 tools
Deletes or cancels 2Claude Code: deny
archive_templateArchive a template (POST /templates/{id}/archive; write scope).No findings
Why it is in this group
- The name "archive_template" says "archive": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Archive a template (POST /templates/{id}/archive; write scope). Sends that reference it fail until it is restored with unarchive_template; its name stays reserved meanwhile. Confirm with the user first if it may be in production use.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
delete_webhookDelete (archive) a webhook so it receives no more events (DELETE /tenant-webhooks/{id}; write scope).No findings
Why it is in this group
- The name "delete_webhook" says "delete": a word for removing or ending something.
- The description says "cannot be restored".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete (archive) a webhook so it receives no more events (DELETE /tenant-webhooks/{id}; write scope). It cannot be restored through the API; confirm with the user first.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
Can't be undone 3Claude Code: ask
publish_templatePublish a template's current draft as its new live version (POST /templates/{id}/publish; write scope).Can send data outNo findings
Why it is in this group
- The name "publish_template" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "publish_template" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Publish a template's current draft as its new live version (POST /templates/{id}/publish; write scope). Sends by templateId use it immediately. Fails if there is no draft or the template is archived.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
send_notificationSend a notification (POST /send; needs a `write`-scoped key).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_notification" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.recipient): what it sends cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "send_notification" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Description, as the server wrote it Send a notification (POST /send; needs a `write`-scoped key). Returns `{ sendId }` with HTTP 202: delivery is asynchronous, so check the outcome with get_send_status. Use exactly one mode: 1. Single: `channelConfigId` + `recipient`. 2. Fan-out: `channelConfigId` + `targets` (1-1000 `{ recipient, externalUserId? }`), one channel, one sendId. 3. Multi-channel: `deliveries` (1-10, each with its own `channelConfigId`, `recipient` and `templateId` or `content`) for ONE person over several channels; add `feed` + `externalUserId` for a single in-app feed entry. 4. Feed-only: `feed` (with `title`) + `externalUserId` and no channel: an in-app notification only. In modes 1-2 give exactly one of `templateId` (a published template, plus `params`) or inline `content`; in mode 3 that choice is made per delivery. Get channel ids and each recipient shape from list_channels first. Pass `idempotencyKey` whenever a retry must not deliver twice.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
test_send_templateSend a real test of a template's PUBLISHED version to one recipient (POST /templates/{id}/test-send; write scope).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "test_send_template" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.recipient): what it sends cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "test_send_template" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.recipient): what the tool writes goes there.
Description, as the server wrote it Send a real test of a template's PUBLISHED version to one recipient (POST /templates/{id}/test-send; write scope). It goes through the provider for real, so use a recipient the user controls. Test sends don't count toward the monthly quota (a small daily allowance applies instead) and never appear in feeds. Returns `{ sendId }` for get_send_status.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 5Claude Code: ask
create_templateCreate a template (POST /templates; write scope).No findings
Why it is in this group
- The name "create_template" says "create": a word for a change.
Description, as the server wrote it Create a template (POST /templates; write scope). `channelKind` is permanent and must match the channels you'll send through (list_channels `templateKind`). It is saved as an unpublished draft unless `publish: true`; sending by templateId needs a published version (publish_template). Names are unique per workspace including archived templates: a collision returns 409, so unarchive_template the old one instead. Returns `{ id, requiredParams }`. Designed (drag-and-drop) email templates can only be made in the dashboard.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
create_webhookCreate an outbound webhook that Ray POSTs signed event payloads to (POST /tenant-webhooks; write scope; Pro plan or higher, otherwise 403).Can send data outNo findings
Why it is in this group
- The name "create_webhook" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Create an outbound webhook that Ray POSTs signed event payloads to (POST /tenant-webhooks; write scope; Pro plan or higher, otherwise 403). The URL must be public HTTPS. The response contains the signing `secret` exactly once: show it to the user to store (e.g. as an env var), since it can't be read again, only rotated with update_webhook. Read the `webhooks` docs page for the signature scheme.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
unarchive_templateRestore an archived template (POST /templates/{id}/unarchive; write scope).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Restore an archived template (POST /templates/{id}/unarchive; write scope). This is how to reclaim a name held by an archived template instead of creating a new one.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
update_template_draftReplace a template's draft (PATCH /templates/{id}; write scope).No findings
Why it is in this group
- The name "update_template_draft" says "update": a word for a change.
Description, as the server wrote it Replace a template's draft (PATCH /templates/{id}; write scope). This is a full replacement, not a partial patch: pass content, logTitle, logDescription and paramOverrides as they should end up (get_template first). `name`, `folder` and `channelKind` are required for validation but not changed (channelKind must equal the original). Live sends keep using the published version until you publish, either with `publish: true` here or publish_template. Fails on archived templates.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
update_webhookChange a webhook (PATCH /tenant-webhooks/{id}; write scope).Can send data outNo findings
Why it is in this group
- The name "update_webhook" says "update": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Change a webhook (PATCH /tenant-webhooks/{id}; write scope). Only the fields you pass change; pass at least one. `rotateSecret: true` issues a new signing secret, returned once in the response, and the old secret stops verifying immediately, so the receiving service must be updated at the same time.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
Only reads 11Show 11 read-only tools
get_click_statsEmail link click counts grouped by destination URL (GET /clicks) for a `sendId`, a `campaignId`, or both (at least one is required).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_click_stats" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it Email link click counts grouped by destination URL (GET /clicks) for a `sendId`, a `campaignId`, or both (at least one is required). Only links from email sends made with `trackClicks: true` are counted.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
get_send_statusDelivery status of a send (GET /sends/{id}): `aggregate` counts per status over the whole send (pending, claimed, delivered, failed_retryable, failed_terminal, suppressed) plus one…No findings
Why it is in this group
- The name "get_send_status" says "get": a word for reading.
Description, as the server wrote it Delivery status of a send (GET /sends/{id}): `aggregate` counts per status over the whole send (pending, claimed, delivered, failed_retryable, failed_terminal, suppressed) plus one page of per-recipient delivery rows including provider errors. Right after sending, rows are usually `pending`; check again after a few seconds. Feed-only sends have no rows. For more rows, pass the returned `nextCursor` as `cursor`.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
get_templateGet one template with its published version and its current draft (GET /templates/{id}): content, logTitle/logDescription, `requiredParams` a send must supply, and paramOverrides.No findings
Why it is in this group
- The name "get_template" says "get": a word for reading.
Description, as the server wrote it Get one template with its published version and its current draft (GET /templates/{id}): content, logTitle/logDescription, `requiredParams` a send must supply, and paramOverrides. Read this before update_template_draft, which needs the full body.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
get_usageThe workspace's plan, subscription status and this calendar month's usage against the monthly quota (GET /billing/subscription).Reads private dataNo findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "calendar": it reads calendars.
Description, as the server wrote it The workspace's plan, subscription status and this calendar month's usage against the monthly quota (GET /billing/subscription). `used`/`remaining` are null on unmetered plans. On a hard-capped plan, sends beyond the quota fail with HTTP 402 quota_exceeded.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
get_webhookGet one outbound webhook (GET /tenant-webhooks/{id}) including its delivery health (consecutiveFailures, lastDeliveryAt, lastFailureAt, lastError).No findings
Why it is in this group
- The name "get_webhook" says "get": a word for reading.
Description, as the server wrote it Get one outbound webhook (GET /tenant-webhooks/{id}) including its delivery health (consecutiveFailures, lastDeliveryAt, lastFailureAt, lastError).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
list_channelsList the delivery channels configured in this workspace (GET /channels).1 finding
Why it is in this group
- The name "list_channels" says "list": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...it expects. Channels and their provider credentials are set up in the Ray dashboard, not th..."
Description, as the server wrote it List the delivery channels configured in this workspace (GET /channels). Call this FIRST before sending: each entry's `id` is the `channelConfigId` for send_notification and test_send_template, `kind` is the channel type (ses_email, smtp_email, fcm_push, slack_webhook, discord_webhook, telegram_bot, twilio_sms, sendsms_mn, generic_webhook), `templateKind` is the template channelKind it accepts, and `recipientSchema` is the exact JSON Schema of the `recipient` it expects. Channels and their provider credentials are set up in the Ray dashboard, not through this API; if the list is empty, ask the user to add one there.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
list_feed_notificationsRead one end user's in-app notification feed (GET /notifications): the entries created by sends with `feed` or `showInFeed`.No findings
Why it is in this group
- The name "list_feed_notifications" says "list": a word for reading.
Description, as the server wrote it Read one end user's in-app notification feed (GET /notifications): the entries created by sends with `feed` or `showInFeed`. This is what an in-app inbox would show, not delivery status (use get_send_status for that). Paginate by passing `nextCursor` back as `cursor`.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
list_templatesList message templates (GET /templates): id, name, folder, channelKind, and `publishedVersionId` (null = never published, so it cannot be sent by templateId yet).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_templates" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- private-dataThe input names a folder (input.folder), and the tool reads: it reads files.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it List message templates (GET /templates): id, name, folder, channelKind, and `publishedVersionId` (null = never published, so it cannot be sent by templateId yet). Archived templates are hidden unless `includeArchived` is true. Use get_template for content and required params.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
list_webhooksList the workspace's outbound event webhooks (GET /tenant-webhooks): url, subscribed events, enabled flag and delivery health (consecutiveFailures, lastError).Reads text others writeNo findings
Why it is in this group
- The name "list_webhooks" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it List the workspace's outbound event webhooks (GET /tenant-webhooks): url, subscribed events, enabled flag and delivery health (consecutiveFailures, lastError). Signing secrets are never returned.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
read_docsRead Ray's documentation as markdown.Reads private dataNo findings
Why it is in this group
- The name "read_docs" says "read": a word for reading.
What it can reach
- private-dataThe name "read_docs" says "read" and "doc": it reads documents.
Description, as the server wrote it Read Ray's documentation as markdown. With no `slug` it returns the index (llms.txt) listing every page; then pass a page slug, i.e. the path after /docs/ without `.md`, such as `sending`, `templates`, `idempotency`, `errors`, `rate-limits`, `webhooks`, `status-and-feeds` or `channels/telegram`. Use it for anything the tool descriptions don't cover.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
whoamiIdentify the API key this connection uses (GET /me): `tenantId` (the workspace), `apiKeyId` and `scopes`.No findings
Why it is in this group
- The name "whoami" says "whoami": a word for reading.
Description, as the server wrote it Identify the API key this connection uses (GET /me): `tenantId` (the workspace), `apiKeyId` and `scopes`. Write tools need the `write` scope; call this to check before attempting them.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
100 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 4 private-data tools breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__ray__get_click_stats",
"mcp__ray__get_usage",
"mcp__ray__list_templates",
"mcp__ray__read_docs"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (2 destructive, 3 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ray-api.gege.mn/mcp: tools/list returned 21 tools to an anonymous client, including archive_template (destructive), delete_webhook (destructive), send_notification (irreversible), publish_template (irreversible), test_send_template (irreversible) and 5 more
Findings
Matches of fixed checks, with the text they matched.
- Infolist_channels
The description mentions "credentials".
What this check looks forMatched text
description: "...it expects. Channels and their provider credentials are set up in the Ray dashboard, not th..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:send_notificationCan't be undoneinputSchema
- Changed:test_send_templateCan't be undoneinputSchema
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ray https://ray-api.gege.mn/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http ray https://ray-api.gege.mn/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ray__whoami",
"mcp__ray__get_usage",
"mcp__ray__list_channels",
"mcp__ray__get_send_status",
"mcp__ray__list_templates",
"mcp__ray__get_template",
"mcp__ray__list_feed_notifications",
"mcp__ray__get_click_stats",
"mcp__ray__list_webhooks",
"mcp__ray__get_webhook",
"mcp__ray__read_docs"
],
"ask": [
"mcp__ray__send_notification",
"mcp__ray__create_template",
"mcp__ray__update_template_draft",
"mcp__ray__publish_template",
"mcp__ray__unarchive_template",
"mcp__ray__test_send_template",
"mcp__ray__create_webhook",
"mcp__ray__update_webhook"
],
"deny": [
"mcp__ray__archive_template",
"mcp__ray__delete_webhook"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ray. Review it before you use it.
Capability tags behind 10 rules
- mcp__ray__get_usage private-data
- mcp__ray__send_notification untrusted-input, outbound
- mcp__ray__list_templates private-data, untrusted-input
- mcp__ray__publish_template outbound
- mcp__ray__test_send_template untrusted-input, outbound
- mcp__ray__get_click_stats private-data, untrusted-input
- mcp__ray__list_webhooks untrusted-input
- mcp__ray__create_webhook outbound
- mcp__ray__update_webhook outbound
- mcp__ray__read_docs private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.gege-mn/ray-mcp/verify?hash=7c334e7e8a2fe56371b11a70eb149f870b7f258c6f9cb8a2a610998c4e73c6f5" | jq -e '.changed == false'Pinned hash 7c334e7e8a2f, from Nov 19, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.gege-mn/ray-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.gege-mn/ray-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.
Ray notifications MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Ray notifications MCP server safe?
- No scan can promise that. What its definitions show: 21 tools, 10 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Ray notifications MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: archive_template and delete_webhook.
Can the Ray notifications MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: send_notification, publish_template and test_send_template.
What tools does the Ray notifications MCP server have?
- 21 tools: 2 destructive, 3 irreversible, 5 write, 11 read. archive_template, delete_webhook, send_notification, publish_template, test_send_template, create_template, update_template_draft, unarchive_template and 13 more.
Does the Ray notifications MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Ray notifications MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_notification, publish_template, test_send_template, create_webhook and update_webhook.
Has the Ray notifications MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.