Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Gechmind/mcp-postmanWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/gechmind/mcp-postman/mcp-postman)<a href="https://agentmods.dev/mcp/gechmind/mcp-postman/mcp-postman"><img src="https://agentmods.dev/badge/mcp/gechmind/mcp-postman/mcp-postman/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/gechmind/mcp-postman/mcp-postman"><img src="https://agentmods.dev/badge/mcp/gechmind/mcp-postman/mcp-postman.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-postman scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "mcp-postman": { "command": "npx", "args": [ "-y", "mcp-postman" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 46c113fb3e2d
mcp-postman is an MCP server published in the GitHub repository Gechmind/mcp-postman (0 stars, last pushed 1y ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other mcp servers, from other repositories
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
mcp
A deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new. Runs locally from the fetchsandbox-mcp npm package. Needs 3 environment variables to run.
bruno-mcp
MCP server for Bruno API collections. Runs locally from the bruno-mcp Python package.
flakiness-knowledge-graph-mcp
MCP server + Playwright reporter that builds a flakiness knowledge graph from test run history. Runs locally from the flakiness-knowledge-graph-mcp npm package.
mcp-selenium-grid
MCP Server for managing Selenium Grid. Runs locally from the mcp-selenium-grid Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.