MCP server for interacting with your LINE Official Account
Nothing to run from here
Peachai 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.
96/100
trust score
8
downloads a day
local
runs on your machine
138
downloads in 30d
What it does
MCP server for the Peach AI WhatsApp Business Messaging Platform
Quickstart
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with npx -y @peachai/mcp and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Publishernot claimed
PEAll 1 server
@peachai1 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 runs on your machine: your client starts Peachai as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with npx -y @peachai/mcp and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
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 Peachai 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 96 / 100
Release 0.1.3 · 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 score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digestdd6ec801625f50a7adf442f31482c7d9c3515ba27dc21b36923dbb14671c6cee
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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 (20 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| peach_create_contact | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/contacts") at dist/tools/contacts.js:12 |
| peach_create_contacts | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/contacts") at dist/tools/contacts.js:18 |
| peach_update_contact | external-sink | external-sink: handler sends an HTTP PATCH ( client.patch(/api/v1/contacts/${encodeURIComponent(phone_number)}) at dist/tools/contacts.js:33 |
| peach_send_template_message | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/events?sync=true") at dist/tools/events.js:18 |
| peach_launch_broadcast | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/events?sync=true") at dist/tools/events.js:41 |
| peach_connect_to_ai_agent | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/events?sync=true") at dist/tools/events.js:58 |
| peach_send_app_message | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/events?sync=true") at dist/tools/events.js:74 |
| peach_get_event_status | no tags | |
| peach_list_template_messages | no tags | |
| peach_list_media | no tags | |
| peach_upload_media | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/medias") at dist/tools/media.js:19 |
| peach_delete_media | external-sink | external-sink: handler sends an HTTP DELETE ( client.delete(/api/v1/medias/${media_id}) at dist/tools/media.js:27 |
| peach_list_messages | no tags | |
| peach_list_templates | no tags | |
| peach_get_template | no tags | |
| peach_create_template | external-sink | external-sink: handler sends an HTTP POST ( client.post("/api/v1/whats_app_templates") at dist/tools/templates.js:39 |
| peach_update_template | external-sink | external-sink: handler sends an HTTP PATCH ( client.patch(/api/v1/whats_app_templates/${id}) at dist/tools/templates.js:57 |
| peach_archive_template | external-sink | external-sink: handler sends an HTTP PATCH ( client.patch(/api/v1/whats_app_templates/${id}/archive) at dist/tools/templates.js:68 |
| peach_pause_template | external-sink | external-sink: handler sends an HTTP PATCH ( client.patch(/api/v1/whats_app_templates/${id}/pause) at dist/tools/templates.js:74 |
| peach_submit_template | external-sink | external-sink: handler sends an HTTP PATCH ( client.patch(/api/v1/whats_app_templates/${id}/submit) at dist/tools/templates.js:80 |
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 digestdd6ec801625f50a7
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.3. Pin a release below and the command asks for exactly that one.
0.1.3
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 Peachai 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.