com.mcparmory/postman
PYPI · MCPARMORY-POSTMAN · 2 COMPONENTS
Create, organize, and manage API collections, specifications, and team workspaces
Available components
Last scanned (4 hours ago)
Scores higher than 68% of PyPI servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 2 of 40 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 176 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5740 tokens (~104/item across 55 items; 55 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
Tool Safety93
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 8 of 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_fork_to_collection" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −14
- Stability: pass → unverified ▼ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/mcparmory-postman@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 40 packages
| Packages resolved | 40 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
update_environment Update Environment ~126
Replace an existing environment with updated configuration. Specify the environment to modify by its unique identifier and provide the new environment name and variable values.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_uid | string | yes | The unique identifier of the environment to update. |
| name | string | – | The new name for the environment. Must be between 1 and 254 characters. |
| values | array | – | An array of environment variables (up to 100 items). Each variable must have a key and value (both 1-254 characters), and may optionally include a type and enabled status. Variables are applied in th… |
No output schema declared.
No examples provided.
update_mock Update Mock ~145
Update an existing mock server by its unique identifier. Modify properties such as name, description, environment, privacy settings, and version tag.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | A descriptive text explaining the purpose or details of the mock server. |
| environment | string | – | The unique identifier of the environment where this mock server operates. |
| mock_uid | string | yes | The unique identifier of the mock server to update. |
| name | string | – | A human-readable name for the mock server. |
| private | boolean | – | Whether the mock server is private (true) or publicly accessible (false). |
| versionTag | string | – | The unique identifier of the version tag associated with this mock server. |
No output schema declared.
No examples provided.
update_monitor Update Monitor ~205
Update an existing monitor's name and execution schedule. Modify the monitor identified by its unique identifier to change its display name and/or cron-based execution frequency and timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| cron | string | – | A cron expression defining the monitor's execution schedule (e.g., `*/5 * * * *` for every 5 minutes, `0 17 * * *` for daily at 5pm). Only certain predefined schedules are supported—verify your desir… |
| monitor_uid | string | yes | The unique identifier of the monitor to update. This is a required path parameter that specifies which monitor will be modified. |
| name | string | – | The new display name for the monitor. Use this to give the monitor a more descriptive or updated label. |
| timezone | string | – | The timezone for interpreting the cron schedule (e.g., `America/Chicago`). Use IANA timezone database identifiers to ensure the monitor runs at the intended local time. |
No output schema declared.
No examples provided.
update_schema Update Schema ~176
Update an existing API schema by replacing its content and metadata. Supports OpenAPI (v1, v2, v3), RAML, and GraphQL schema types in their respective formats.
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | The unique identifier of the API containing the schema to update. |
| apiVersionId | string | yes | The unique identifier of the API version containing the schema to update. |
| language | string | – | The schema language format. Use `json` or `yaml` for OpenAPI and RAML schemas; use `graphql` for GraphQL schemas. |
| schemaId | string | yes | The unique identifier of the schema to update. |
| type | string | – | The schema type being updated. Allowed values are `openapi3`, `openapi2`, `openapi1`, `raml`, or `graphql`. |
No output schema declared.
No examples provided.
update_workspace Update Workspace ~231
Update a workspace's properties and manage its associations with collections, environments, mocks, and monitors. The endpoint replaces all associated entities with those specified in the request, so omitted entities will be removed from the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| collections | array | – | Array of collection UIDs to associate with this workspace. Replaces all existing collections—only specified collections will remain associated after the update. |
| description | string | – | A text description for the workspace to help identify its purpose or contents. |
| environments | array | – | Array of environment UIDs to associate with this workspace. Replaces all existing environments—only specified environments will remain associated after the update. |
| mocks | array | – | Array of mock UIDs to associate with this workspace. Replaces all existing mocks—only specified mocks will remain associated after the update. |
| monitors | array | – | Array of monitor UIDs to associate with this workspace. Replaces all existing monitors—only specified monitors will remain associated after the update. |
| name | string | – | The display name for the workspace. |
| workspace_id | string | yes | The unique identifier of the workspace to update. |
No output schema declared.
No examples provided.
How do I install the com.mcparmory/postman MCP server?
com.mcparmory/postman runs locally as a PyPI package, launched with uvx mcparmory-postman. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-postman
claude mcp add com-mcparmory-postman -- uvx mcparmory-postman
What is the com.mcparmory/postman MCP server?
com.mcparmory/postman is an MCP server listed in the public MCP registry as com.mcparmory/postman. Create, organize, and manage API collections, specifications, and team workspaces. This page covers its PyPI package (mcparmory-postman).
Is the com.mcparmory/postman MCP server safe to use?
com.mcparmory/postman scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/postman MCP server expose?
com.mcparmory/postman exposes 55 tools: list_apis, create_api, get_api, update_api, delete_api, and 50 more. Their descriptions and schemas cost roughly 5,740 tokens of context every time the server is loaded.
Is the com.mcparmory/postman MCP server still maintained?
com.mcparmory/postman is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mcparmory/postman MCP server under?
com.mcparmory/postman declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.