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