Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.michaelyousrie/mailpal

NPM · MAILPAL-MCP

List, inspect, and run saved HTTP requests from MailPal collections; write tools on Pro

Available components

0 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 369 tokens (~36/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_request" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/mailpal-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~369 tokens

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 →

Tool Tokens
create_collection ~26

Create a new empty collection in the workspace. Pro.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

create_or_update_request ~51

Create a request in a collection, or update it when requestId is given. Pro.

NameTypeReqDescription
collectionIdstringyes–
requestobjectyes–
requestIdstring––

No output schema declared.

No examples provided.

generate_tests ~36

Add baseline assertions to a request (expected status from its latest run, else 200). Pro.

NameTypeReqDescription
requestIdstringyes–

No output schema declared.

No examples provided.

get_history_recent ~25

List recent request executions (newest first).

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

get_request ~27

Get the full definition of one saved request by id.

NameTypeReqDescription
requestIdstringyes–

No output schema declared.

No examples provided.

list_collections ~25

List all API collections in the workspace with their folders and request names/ids.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_variables ~32

List each collection's variables. Secret variables appear as {"secret": "NAME"} references; secret values are never returned.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run_request ~58

Execute a saved request. {{VAR}} placeholders resolve from the owning collection's variables. Returns status, headers, timing and body (truncated to 50KB). Secret values are resolved internally and never returned.

NameTypeReqDescription
requestIdstringyes–

No output schema declared.

No examples provided.

scaffold_test_suite ~36

Add a baseline status assertion to every request in a collection that has no tests yet. Pro.

NameTypeReqDescription
collectionIdstringyes–

No output schema declared.

No examples provided.

set_collection_variable ~53

Set a NON-SECRET variable on a collection. Secret-referenced variables cannot be written through MCP. Pro.

NameTypeReqDescription
collectionIdstringyes–
keystringyes–
valuestringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.michaelyousrie/mailpal MCP server?

io.github.michaelyousrie/mailpal runs locally as an npm package, launched with npx -y mailpal-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mailpal-mcp

# add to Claude Code
claude mcp add michaelyousrie-mailpal -- npx -y mailpal-mcp
Common questions

What is the io.github.michaelyousrie/mailpal MCP server?

io.github.michaelyousrie/mailpal is an MCP server listed in the public MCP registry as io.github.michaelyousrie/mailpal. List, inspect, and run saved HTTP requests from MailPal collections; write tools on Pro. This page covers its npm package (mailpal-mcp).

Is the io.github.michaelyousrie/mailpal MCP server safe to use?

io.github.michaelyousrie/mailpal scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.michaelyousrie/mailpal MCP server expose?

io.github.michaelyousrie/mailpal exposes 10 tools: list_collections, get_request, run_request, get_history_recent, list_variables, and 5 more. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.

Is the io.github.michaelyousrie/mailpal MCP server still maintained?

io.github.michaelyousrie/mailpal is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.michaelyousrie/mailpal MCP server under?

io.github.michaelyousrie/mailpal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.michaelyousrie/mailpal MCP server?

VerifyMCP ran 16 checks on io.github.michaelyousrie/mailpal, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.