Ext Ops Panel
Open dashboard
Comparison

frysker-mcp vs Scriptura

frysker-mcp is an MCP server published by anned20. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Scriptura is an MCP server published by scriptura.si. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacefrysker-mcpScriptura
npm registry (MCP servers) Listed
Version: 0.2.0
Downloads/month (npm): 641
Downloads/week (npm): 599
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

frysker-mcp vs Scriptura
Factfrysker-mcpScriptura
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)Not published2026-10-25
Where it runs (differs)On your machine (frysker-mcp)Remote server (scriptura.si/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/anned20/frysker-mcpNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-25
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 42 h ago returned HTTP 200

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

frysker-mcp

In its own words, on npm registry (MCP servers):

MCP server exposing Frysker's Frisian language aids (word lookup, Dutch/Frisian translation, spell-check) as agent tools.

Scriptura

In its own words, on Official MCP Registry:

953 classic works in the original beside English: Greek, Latin, philosophy, literature, scripture

How to run each

frysker-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Scriptura As a remote MCP server

Claude Code
claude mcp add --transport http scriptura https://scriptura.si/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Scriptura has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of frysker-mcp nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: frysker-mcp · What it can do: Scriptura · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built