MCP server for interacting with your LINE Official Account
Nothing to run from here
Zaungast 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.
97/100
trust score
2
downloads a day
local
runs on your machine
100
downloads in 30d
What it does
Read-only, offline MCP server for Teams: search chats, read conversations, surface trending topics, find people, and browse meetings & calls — straight from the local on-disk cache, with no Graph API, no cloud, no credentials, and token-economical output
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user zaungast-mcp '--' npx -y zaungast
# 2 — ask your agent for something these tools do
# describe_schema, find_person, get_message and 7 more
Zaungast costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MBAll 2 servers
mbe242 servers
2 categories
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 Zaungast 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.
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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user zaungast-mcp '--' npx -y zaungastReconnect, or start a new session, and the tools appear in the model’s tool list.
Free 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 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
10 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.
Inspect the raw Teams IndexedDB stores and PROPOSE a field mapping. Use when tools report the schema is unrecognized (after a Teams update), or to inspect the DB structure. Proposes only — applies nothing; a human verifies the proposal and saves it as a new schema version.
No parameter schema on file.
Resolve a name/nickname fragment to a person's canonical name and stable p:handle, with message count and last-contact time. Use when a name is ambiguous or unrecognized, or when you need contact stats or a p:handle. For ordinary filtering, just pass a name substring directly to search (from/in)…
No parameter schema on file.
Fetch ONE message in full — its complete, untruncated body (line breaks preserved) plus reactions. Target it by conversation (c:xxxx or title/participant substring) PLUS message:m:<id> (the m:… from a search hit or a thread root). Page a very long body with offset:. Use read_conversation to BROWSE…
No parameter schema on file.
Your call log: who called whom, when, and for how long. direction:Outgoing|Incoming, missed:true for the callState=Missed subset, participant filters by resolved counterpart/group name. Deleted calls are filtered out. Tags recorded/voicemail/spam calls and pivots a recording to the chat message…
No parameter schema on file.
Your Teams sidebar: the newest N conversations (default), or filter by kind/participant/title/time. …
No parameter schema on file.
Your calendar: meetings and appointments, defaulting to a FORWARD window (today..+7d — pass since/until to look elsewhere). type:meeting|appointment|all; query/attendee filter by substring. Metadata by default (attendee names/response tallies, no join URLs — those are never stored); include_body…
No parameter schema on file.
Rank the distinctive/trending topics over a window (vs your baseline), overall or scoped to a person/conversation. Returns each topic with an exemplar message. …
No parameter schema on file.
Browse one conversation's messages in STORY ORDER (oldest→newest). Target by handle (c:xxxx) or title/participant substring; window with since/until, page back with the returned older: cursor. CHANNELS render as a thread digest (root + recent replies, threads by last activity); to read one thread…
No parameter schema on file.
Read ONE channel reply-chain in full (root + all replies, in order). Target by conversation (c:xxxx or substring) plus thread:m:<id> — the m:<id> of the chain's root OR of any reply in it (either resolves to the whole chain; a reply is centered and marked →). Page a very long chain back with the…
No parameter schema on file.
Full-text search across all messages with filters. Empty query = filtered browse. from/in accept display-name / title substrings or handles. mentions_me finds messages that @mention you. … …
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 Zaungast 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 97 / 100
Release 0.5.0 · scanned 13 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 score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest71f4b2f856610669bec107fdcee1b0827ef55b0fb11b7936ac8a601436852db0
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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 surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can start a fixed program (a process-spawning capability, not arbitrary code execution)
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 digest71f4b2f856610669
Scanned2026-10-13
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.5.0. Pin a release below and the command asks for exactly that one.
0.5.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 Zaungast 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.