Ext Ops Panel
Open dashboard
Comparison

Postman vs Browser URL Check

Postman is a plugin bundle for AI coding tools published by postmanlabs. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). Browser URL Check is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplacePostmanBrowser URL Check
Claude Code: claude-plugins-official Listed
Version: 2.0.1
Forks (GitHub): 8
Stars (GitHub): 21
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

Postman vs Browser URL Check
FactPostmanBrowser URL Check
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)21 (better)0 (worse)
Forks (GitHub) (differs)8 (better)0 (worse)
Last release (differs)2026-10-15Not published
Where it runs (differs)Installs as a plugin bundleRemote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/browser-url-ok/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)19Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/postmanlabs/postman-plugingithub.com/sadri-dridi/named-mcp-utilities
Changes in the last 7 days (differs)80
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days 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

Postman

In its own words, on Claude Code: claude-plugins-official:

Work with Postman from your agent: bootstrap a repo's Postman setup, mock an API before it's implemented, run collection and governance checks in CI, monitor a live endpoint, deploy and debug Postman Flows, and publish generated API documentation.

Browser URL Check

In its own words, on Official MCP Registry:

Check whether a URL can be opened. No browser is launched.

How to run each

Postman As a Claude Code plugin

Claude Code
/plugin install postman@claude-plugins-official

Browser URL Check As a remote MCP server

Claude Code
claude mcp add --transport http browser-url-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/browser-url-ok/mcp

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

Only Browser URL Check 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: Postman · What it can do: Browser URL Check · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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