Ext Ops Panel
Open dashboard
Comparison

Postman MCP Server vs tierproxy

Postman MCP Server is an MCP server published by postman.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). tierproxy is an MCP server published by tierproxy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplacePostman MCP Servertierproxy
Official MCP Registry Listed
Version: 2.13.0
Downloads/month (npm): 31 219
Downloads/week (npm): 4 519
Forks (GitHub): 87
Stars (GitHub): 317
Not marked · First seen
Listed
Version: 0.4.0
Downloads/month (PyPI): 78
Downloads/week (PyPI): 22
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:73f715030cbe
Forks (GitHub): 87
Pulls (Docker Hub): 45 079
Stars (Docker Hub): 6
Stars (GitHub): 317
Not marked · First seen
Not listed

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

Postman MCP Server vs tierproxy
FactPostman MCP Servertierproxy
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)317 (better)0 (worse)
Pulls (Docker Hub) (differs)45 079No figure on Docker Hub
Forks (GitHub) (differs)87 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineOn your machine (tierproxy)
Transport (differs)Streamable HTTP, stdiostdio
Tools it declares (differs)42Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/postmanlabs/postman-mcp-servergithub.com/tierproxy/python-sdk
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

Postman MCP Server

In its own words, on Official MCP Registry:

Give your AI agents trusted access to the full Postman platform.

tierproxy

In its own words, on Official MCP Registry:

Multi-provider proxy infrastructure for AI/ML. Geo, sessions, cost-aware routing, usage tools.

How to run each

Postman MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http postman-mcp-server https://mcp.postman.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: POSTMAN_API_KEY (secret), Authorization header

tierproxy As a local MCP server: PyPI package

Claude Code
claude mcp add --env "TIERPROXY_API_KEY=<YOUR_TIERPROXY_API_KEY>" --transport stdio python-sdk -- uvx --spec "tierproxy[mcp]" tierproxy tierproxy-mcp

Requires: TIERPROXY_API_KEY (secret)

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

Tools each declares

The marketplaces of tierproxy publish no list of tools, so we do not compare tools.

Settings each asks for

Only Postman MCP Server asks for

  • POSTMAN_API_KEY (secret)

Only tierproxy asks for

  • TIERPROXY_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Postman MCP Server · What it can do: tierproxy · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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