Ext Ops Panel
Open dashboard
Comparison

@portone/mcp-server vs Pontis

@portone/mcp-server is an MCP server published by @portone. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Pontis is an MCP server published by pontis.company. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplace@portone/mcp-serverPontis
npm registry (MCP servers) Listed
Version: 0.20.1
Downloads/month (npm): 828
Downloads/week (npm): 141
Forks (GitHub): 3
Stars (GitHub): 29
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

@portone/mcp-server vs Pontis
Fact@portone/mcp-serverPontis
Marketplaces that list it11
Stars (GitHub) (differs)29No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@portone/mcp-server)Remote server (pontis.company/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MIT OR Apache-2.0Not stated
Repository (differs)github.com/portone-io/mcp-serverNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-04
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 h ago

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

@portone/mcp-server

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

포트원 사용자를 위한 MCP (Model Context Protocol) 서버입니다. 포트원 개발자센터, 헬프센터 등 공식 문서 내용을 LLM(Large Language Model)에 제공해 정확한 정보를 바탕으로 사용자의 연동 및 질의를 돕도록 합니다.

Pontis

In its own words, on Official MCP Registry:

Read-only public information about Pontis: what it does, its gatherings, content and focus.

How to run each

@portone/mcp-server

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

Pontis As a remote MCP server

Claude Code
claude mcp add --transport http site https://pontis.company/mcp

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

Only Pontis 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

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

What it can do: @portone/mcp-server · What it can do: Pontis · 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