GlockApps — Inbox Placement Testing

com.glockappsv1.0.0更新於 Sep 29, 2026

Inbox placement tests across Gmail, Outlook, Yahoo and 30+ providers.

已驗證Streamable HTTP可網頁執行Data & Analytics Business & Commerce Communication & Collaboration

概覽

AI 產生的概覽

執行 GlockApps 收件匣投放測試，讓助理提供種子位址、讀取結果並診斷垃圾郵件過濾問題。

功能: 將助理連接到 GlockApps 代管的收件匣投放測試服務。助理可以列出專案、服務商與歷史測試，建立新測試並回傳種子位址與標記，等待結果，然後讀取各信箱的收件匣與垃圾郵件投放情形，並取得優先修復建議。它也能比較測試、取得內容分析、查詢剩餘額度並刪除測試。此連接器本身不寄送郵件，活動郵件由使用者從自己的平台寄出。
適用情境: 適合電子郵件行銷人員、送達率工程師與代理商，希望在對話助理中檢查 Gmail、Outlook、Yahoo 及其他 30 多家服務商的收件匣與垃圾郵件投放情形。當你已在使用 GlockApps 測試，並想讓助理啟動測試、解讀結果並提出修復建議而不必切換到網頁應用時，值得加入。
執行需求: 遠端 HTTP 端點 API 存取權限的 GlockApps 帳戶、來自 Account → API / MCP 的 API 金鑰，以及測試額度（每次測試消耗一個）。不支援 OAuth 的用戶端可透過 Authorization Bearer 標頭傳送金鑰。需要能存取 GlockApps API 的網路。

安裝前請注意

建立測試會消耗一個額度；若寄送時缺少必要的標記，測試將無法配對，額度仍會被消耗，直到刪除該測試。刪除測試會移除測試及其結果，且僅在尚無結果送達時退還額度。API 金鑰屬於憑證；在靜態標頭方式下會保存在用戶端設定中，重新產生金鑰會終止這些連線。權限範圍限於 inbox_placement:read 與 inbox_placement:write。

安裝

在 SourceWeft 中

開啟儀表板中的 GlockApps — Inbox Placement Testing，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://api.glockapps.com/mcp"
    }
  }
}

README

GlockApps MCP

Run real inbox placement tests from your AI assistant. Ask it to start a test, and it hands you the seed addresses to send to; ask again once you have sent, and it tells you who put you in the inbox, who put you in spam, and what to fix first.

The seed network is live mailboxes at Gmail, Outlook, Yahoo, AOL, Zoho, corporate Exchange and 30+ other providers.

This repository is documentation and the registry manifest. The server itself is hosted by GlockApps — there is nothing here to install or run.

What you need

A GlockApps account with API access on the plan. Your API key is on Account → API / MCP.
Test credits. Every test costs one, whether it is started here or in the GlockApps web app.

Quick connect

Claude.ai, Claude Desktop

Settings → Connectors → Add custom connector. Paste the address above and leave Client ID and Client Secret empty. Select Connect: a GlockApps page opens and asks for your API key once.

Claude Code

Then /mcp in the session, and authenticate in the browser window it opens.

ChatGPT

Turn on developer mode (Settings → Security and login), then Plugins → + → Create app → Create MCP App. Paste the address, leave Authentication on OAuth, select Create, and paste your API key on the GlockApps page that opens. Developer mode is required while the connector is not yet in the ChatGPT directory.

Cursor, Windsurf, Continue and other clients

Clients that cannot do OAuth can send the API key directly. Copy a config from configs/ and put your key in it:

json

{    "mcpServers": {        "glockapps": {            "url": "https://api.glockapps.com/mcp",            "headers": { "Authorization": "Bearer YOUR_GLOCKAPPS_API_KEY" }        }    }}

{    "mcpServers": {        "glockapps": {            "url": "https://api.glockapps.com/mcp",            "headers": { "Authorization": "Bearer YOUR_GLOCKAPPS_API_KEY" }        }    }}

Full per-client instructions: docs/connect.md.

How a test works

The one thing to understand before you start: this connector cannot send your email. It gives you addresses to send to, and it reads what arrives.

list_projects — resolves the project everything else needs.
create_test — costs 1 credit. Returns the seed addresses and a marker.
You send. Send the campaign you want to test, from the platform you are testing, to every seed address, with the marker included — either the X-API-Campaign-id header or the id: ... line in the body.
wait_for_test — results are usually usable about 10 minutes after sending.
get_results, then diagnose for what to fix, worst first.

A send without the marker never matches the test. Nothing arrives, the test never finishes, and the credit is still spent. If that happens, ask your assistant to delete the test: the credit comes back while no result has arrived.

Some providers accept mail slowly, so a test that has not "finished" after an hour is normal, not broken.

Things to ask it

"Start an inbox placement test on my main project."
"Has the test finished? What is the inbox rate?"
"Why did this campaign land in spam?"
"Compare this test with yesterday's. Did the fix work?"
"Which providers are filtering us, and what should I change first?"

Tools

Fifteen tools, thirteen of them read-only. Full reference with parameters: docs/tools.md.


Read	`list_projects` `list_folders` `list_providers` `list_tests` `get_balance` `get_seed_list` `get_test_status` `wait_for_test` `get_results` `diagnose` `get_content_analysis` `compare_tests` `get_shared_link`
Write	`create_test` — costs 1 credit
Destructive	`delete_test` — removes the test and its results; refunds the credit only while no result has arrived

Security

Scopes. inbox_placement:read and inbox_placement:write. The connector cannot see or change your password, billing details or sending accounts.
It never sends email. Your campaign is sent by you, from your own platform.
Your key is not shared with the AI provider. In the OAuth flow it is exchanged on a GlockApps page for a token scoped to this connector; it stays on your GlockApps account.
Regenerating your key does not break an OAuth connection. The connector records which account it is linked to, not the key, and picks up the current one on each call. It does end any connection using the static-key method above.
Rate limits. Test creation is capped per hour and per day on top of your credit balance. get_balance reports the effective number.

Troubleshooting

"No test credits left" — top up in GlockApps, or run the test from the web app. get_balance tells you what is left before you start.

The test never finishes and shows nothing — almost always a send without the marker. Delete the test to get the credit back, start a fresh one, and follow its sending instructions exactly.

Some results missing after an hour — usually fine; slower providers take hours. Nothing at all within ten minutes of sending means the marker was missing.

"Shareable report links are unavailable" — not part of every subscription. Your assistant can still read per-mailbox results directly.

Connecting fails with "API key not recognised" — copy it again from Account → API / MCP; API access has to be enabled on your plan.

Support

Open an issue or email [email protected].

Setup guide: https://glockapps.com/mcp-setup/
About the connector: https://glockapps.com/mcp/
Privacy policy: https://glockapps.com/privacy-policies/

來源：README.md，提交 050ed62

工具

工具後設資料尚未被收錄。

版本歷史

v1.0.0最新Sep 29, 2026