MCP server for interacting with your LINE Official Account
Nothing to run from here
Ray notifications is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
8
downloads a day
local
or remote
259
downloads in 30d
What it does
Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'RAY_API_KEY=${RAY_API_KEY}' --transport stdio ray-notifications-mcp '--' npx -y @gege-mn/ray-mcp
# 2 — ask your agent for something these tools do
# whoami, get_usage, list_channels and 19 more
It needs RAY_API_KEY: this reads it from your environment, so export it first.
Ray notifications costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GMAll 1 server
gege-mn1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads RAY_API_KEY (Ray API key (ck_live_...). Create one at https://ray.gege.mn under API keys; use the write scope to send and edit) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx RAY_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'RAY_API_KEY=${RAY_API_KEY}' --transport stdio ray-notifications-mcp '--' npx -y @gege-mn/ray-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://ray-api.gege.mn/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http ray-notifications-mcp https://ray-api.gege.mn/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: RAY_API_KEY — Ray API key (ck_live_...). Create one at https://ray.gege.mn under API keys; use the write scope to send and edit.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
No parameter schema on file.
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, generic_webhook), templateKind is the template channelKind it accepts, and recipientSchema is t
No parameter schema on file.
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 `
No parameter schema on file.
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
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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
No parameter schema on file.
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, eit
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Get one outbound webhook (GET /tenant-webhooks/{id}) including its delivery health (consecutiveFailures, lastDeliveryAt, lastFailureAt, lastError).
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ray notifications or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest099d9563f80972dce3daa48fce8bac64e8b9efb1549e645c6f6efa03532899e0
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ray | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest099d9563f80972dc
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Ray notifications can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.