Ext Ops Panel
Open dashboard
Comparison

io.github.Smartoire/paxaver-mcp vs io.github.tixuz/openemis-pro

io.github.Smartoire/paxaver-mcp is an MCP server published by Smartoire. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.tixuz/openemis-pro is an MCP server published by tixuz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplaceio.github.Smartoire/paxaver-mcpio.github.tixuz/openemis-pro
Official MCP Registry Listed
Version: 2.7.5
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.1.0
Downloads/month (npm): 120
Downloads/week (npm): 15
Forks (GitHub): 0
Stars (GitHub): 2
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

io.github.Smartoire/paxaver-mcp vs io.github.tixuz/openemis-pro
Factio.github.Smartoire/paxaver-mcpio.github.tixuz/openemis-pro
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last release (differs)2026-10-17Not published
Where it runs (differs)Remote server (mcp.paxaver.com/mcp)On your machine (openemis-mcp-pro)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published6, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/smartoire/paxaver-mcpgithub.com/tixuz/openemis-mcp-pro
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days ago, requires a keyno remote endpoint we check

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

io.github.Smartoire/paxaver-mcp

In its own words, on Official MCP Registry:

MCP adapter for the Paxaver school community platform. Streamable HTTP, OAuth 2.1, capability auth.

io.github.tixuz/openemis-pro

In its own words, on Official MCP Registry:

Read + write MCP server for OpenEMIS — free open-source school management system. 675 resources.

How to run each

io.github.Smartoire/paxaver-mcp As a remote MCP server

Claude Code
claude mcp add --transport http paxaver-mcp https://mcp.paxaver.com/mcp

io.github.tixuz/openemis-pro As a local MCP server: npm package

Claude Code
claude mcp add --env "OPENEMIS_API_KEY=<YOUR_OPENEMIS_API_KEY>" --env "OPENEMIS_BASE_URL=<YOUR_OPENEMIS_BASE_URL>" --env "OPENEMIS_PASSWORD=<YOUR_OPENEMIS_PASSWORD>" --transport stdio openemis-pro -- npx -y openemis-mcp-pro

Requires: OPENEMIS_API_KEY (secret), OPENEMIS_BASE_URL, OPENEMIS_PASSWORD (secret)

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

Only io.github.Smartoire/paxaver-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.Smartoire/paxaver-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.Smartoire/paxaver-mcp · What it can do: io.github.tixuz/openemis-pro · Compare two other plugins

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