Gmail Postmaster Tools
MCPB · GMAIL-POSTMASTER-TOOLS.MCPB
Gmail Postmaster Tools v2 — domains, traffic metrics, and compliance via your own Google OAuth.
Available components
Last scanned (6 hours ago)
Scores higher than 91% of MCPB servers
Category Marketing and SEO
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 Security13
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
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 105 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 571 tokens (~81/item across 7 items; 7 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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; "gpt_sign_out" implies "delete" 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 7 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
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Maintenance: unverified → pass ▲ functional
- Stability: pass → 0.97 functional
- 18 Oct 26 −1
- Maintenance: pass → unverified ▼ functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
- 14 Oct 26 +1
- Stability: 0.97 → 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 mcpb/https://github.com/optipub/gmail-postmaster-tools-mcp/releases/download/v1.0.1/gmail-postmaster-tools.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
get_compliance_status ~84
Get the sender compliance status for a domain — verdicts for SPF, DKIM, DMARC, alignment, message formatting, DNS records, encryption, user-reported spam rate, and one-click / honored unsubscribe. Calls GET /v2/domains/{domain}/complianceStatus.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Fully-qualified domain name, e.g. example.com. |
No output schema declared.
No examples provided.
get_domain ~51
Get metadata for a single registered domain (verification state, permission, timestamps). Calls GET /v2/domains/{domain}.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Fully-qualified domain name, e.g. mail.example.com. |
No output schema declared.
No examples provided.
gpt_auth_status ~28
Check whether you are signed in to Gmail Postmaster Tools and when the access token expires.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gpt_authenticate ~70
Sign in to Gmail Postmaster Tools. Opens your browser for a Google account login (OAuth 2.0 authorization-code + PKCE over a 127.0.0.1 loopback) using the Google OAuth client you configured, and caches the tokens. Run this once before fetching data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gpt_sign_out ~19
Delete the cached Google tokens (sign out).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_domains ~72
List the domains registered in your Gmail Postmaster Tools account, with verification state and your permission level. Calls GET /v2/domains.
| Name | Type | Req | Description |
|---|---|---|---|
| pageSize | number | – | Optional max number of domains (default 10, max 200). |
| pageToken | string | – | Optional page token from a previous call. |
No output schema declared.
No examples provided.
query_domain_stats ~247
Query Gmail traffic metrics for a domain over a date range. Metrics include SPAM_RATE, AUTH_SUCCESS_RATE (filter auth_type=spf|dkim|dmarc), TLS_ENCRYPTION_RATE (filter traffic_direction=inbound|outbound), DELIVERY_ERROR_RATE/COUNT (optional filter error_type=...), FEEDBACK_LOOP_SPAM_RATE/ID. Defaults to SPAM_RATE over the last ~7 days, daily. Calls POST /v2/domains/{domain}/domainStats:query.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Fully-qualified domain name, e.g. example.com. |
| end_date | string | – | End date yyyy-MM-dd (inclusive). Defaults to yesterday. |
| granularity | string | – | DAILY (per-day) or OVERALL (totals for the period). Default DAILY. |
| metrics | array | – | Metrics to fetch. Each item is either a standard metric name (string) or an object { standardMetric, filter, name }. Metrics like AUTH_SUCCESS_RATE and TLS_ENCRYPTION_RATE require a filter. Defaults… |
| start_date | string | – | Start date yyyy-MM-dd (inclusive). Defaults to ~8 days ago. |
No output schema declared.
No examples provided.
How do I install the Gmail Postmaster Tools MCP server?
Gmail Postmaster Tools ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · gmail-postmaster-tools.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the Gmail Postmaster Tools MCP server?
Gmail Postmaster Tools is an MCP server listed in the public MCP registry as io.github.optipub/gmail-postmaster-tools. Gmail Postmaster Tools v2, domains, traffic metrics, and compliance via your own Google OAuth. This page covers its MCPB bundle (https://github.com/optipub/gmail-postmaster-tools-mcp/releases/download/v1.0.1/gmail-postmaster-tools.mcpb).
Is the Gmail Postmaster Tools MCP server safe to use?
Gmail Postmaster Tools scores 57 out of 100 on VerifyMCP. 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 Gmail Postmaster Tools MCP server expose?
Gmail Postmaster Tools exposes 7 tools: gpt_authenticate, gpt_auth_status, gpt_sign_out, list_domains, get_domain, and 2 more. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
What licence is the Gmail Postmaster Tools MCP server under?
Gmail Postmaster Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.