Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lemmy

NPM · @PIPEWORX/MCP-LEMMY · 2 COMPONENTS

Lemmy MCP — public reads on any Lemmy instance.

+3 this week 80 Trust /100

Last scanned (4 hours ago)

Scores higher than 65% of npm servers

Category News and Social

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-lemmy). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 693 tokens (~99/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 16% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 77

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-lemmy@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-lemmy
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-lemmy/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3649672465
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:277af781291ea5354d08bf185e5a11d9be33a1425148b52249392cb264286a367be6cb66591764ec5c31ebb7e707e4e19cd79b1f53bd1d3d2dfbb6721

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~640 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
comments ~101

List Lemmy comments under a post or thread. Returns author, body, score, parent, posted date. Use to read discussion threads on federated Reddit-alternative communities.

NameTypeReqDescription
communitystring––
instancestring––
limitnumber––
max_depthnumber––
pagenumber––
parent_idnumber––
post_idnumber––
sortstring––

No output schema declared.

No examples provided.

communities ~89

List communities on a Lemmy instance (default lemmy.world), sortable by Active/Hot/New/TopMonth/etc. and filterable by type (All/Local/Subscribed). Returns community name, description, and subscriber count.

NameTypeReqDescription
instancestring––
limitnumber––
pagenumber––
sortstring––
type_string––

No output schema declared.

No examples provided.

community ~61

Fetch metadata for a specific Lemmy community by name (e.g. "asklemmy") or numeric id from the specified instance. Returns description, icon, subscriber count, and moderators.

NameTypeReqDescription
instancestring––
name_or_idstringyes–

No output schema declared.

No examples provided.

post ~55

Fetch a single Lemmy post by numeric id from the specified instance (default lemmy.world). Returns title, body, author, score, comment count, and community.

NameTypeReqDescription
idnumberyes–
instancestring––

No output schema declared.

No examples provided.

posts ~162

List Lemmy posts (federated Reddit-alternative; ActivityPub) from a community or feed. Sort by Active / Hot / New / TopDay / TopWeek / etc. Returns post title, body, author, upvotes, comment count. Use for federated open-source discussion forum content.

NameTypeReqDescription
communitystring–Community name (e.g. "asklemmy@lemmy.world") or id.
instancestring––
limitnumber––
pagenumber––
sortstring–Active | Hot | New | Old | TopDay | TopWeek | TopMonth | TopYear | TopAll | MostComments | NewComments
type_string–All | Local | Subscribed

No output schema declared.

No examples provided.

search ~126

Full-text search across a Lemmy instance (default lemmy.world) for posts, comments, communities, or users matching query `q`. Filter by type (Posts/Comments/Communities/Users), listing (All/Local), and sort order.

NameTypeReqDescription
instancestring––
limitnumber––
listing_typestring–All | Local | Subscribed
pagenumber––
qstringyes–
sortstring––
type_string–All | Comments | Posts | Communities | Users | Url

No output schema declared.

No examples provided.

site ~46

Fetch instance-level metadata for a Lemmy instance (default lemmy.world), including site name, description, version, admin info, and federated instances list.

NameTypeReqDescription
instancestring––

No output schema declared.

No examples provided.

Install

How do I install the Lemmy MCP server?

Lemmy runs locally as an npm package, launched with npx -y @pipeworx/mcp-lemmy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-lemmy

# add to Claude Code
claude mcp add pipeworx-io-lemmy -- npx -y @pipeworx/mcp-lemmy
Common questions

What is the Lemmy MCP server?

Lemmy is an MCP server listed in the public MCP registry as io.github.pipeworx-io/lemmy. Lemmy MCP, public reads on any Lemmy instance. This page covers its npm package (@pipeworx/mcp-lemmy).

Is the Lemmy MCP server safe to use?

Lemmy scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Lemmy MCP server expose?

Lemmy exposes 7 tools: posts, post, comments, communities, community, and 2 more. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.

Is the Lemmy MCP server still maintained?

Lemmy is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Lemmy MCP server under?

Lemmy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.