faucet vs com.mcparmory/postman
faucet is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑02.
faucet is a plugin bundle for AI coding tools published by faucet-hq. No marketplace we read lists it any more. com.mcparmory/postman is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-05. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace faucet-hq/faucet-stream | Removed on 2026-11-02 Version: 1.16.0 Forks (GitHub): 8 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Downloads/month (PyPI): 820 Downloads/week (PyPI): 149 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.0.2 Downloads/month (PyPI): 820 Downloads/week (PyPI): 149 Forks (GitHub): 4 Stars (GitHub): 32 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
| Fact | faucetno longer listed · | com.mcparmory/postman |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 22 | 32 |
| Forks (GitHub) (differs) | 8 | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcparmory-postman) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT OR Apache-2.0 | MIT |
| Repository (differs) | github.com/faucet-hq/faucet-stream | github.com/mcparmory/registry |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of faucet
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
💻 FAOS Developer Agent — Senior Software Engineer
-
Environment setup, credential management, container building, and workflow orchestration.
-
Build an MCP server and bundle your tools into a shareable plugin, end to end. Two skills: build-mcp scaffolds one server; build-plugin packages skills, hooks, agents, and MCP…
-
Agents, commands, skills, and scripts for scaffolding, reviewing, aligning, and deploying homelab MCP server plugins. Includes canonical Python, TypeScript, and Rust server…
-
Forge de CLIs validées pour agents — registre central, scaffolding et manifestes CLI normalisés.
-
Shared rules, secrets handling, and workspace MCP for dlthub
What each says it does
faucet
Write and validate faucet pipeline configs, debug, verify and tune runs, deploy and operate faucet, drive its HTTP API, handle credentials safely, migrate to it, use and publish Template Hub templates, and build connector crates.
com.mcparmory/postman
Create, organize, and manage API collections, specifications, and team workspaces
How to run each
faucet
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.mcparmory/postman As a local MCP server: PyPI package
claude mcp add --transport stdio postman -- uvx mcparmory-postman
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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: faucet · What it can do: com.mcparmory/postman · Compare two other plugins
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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.