GlockApps — Inbox Placement Testing

com.glockappsPublished by glockapps.comOfficial publisherv1.0.0Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableCommunication & CollaborationData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

GlockApps MCP runs email inbox placement tests across Gmail, Outlook, Yahoo and 30+ providers, letting an assistant start tests, read results and diagnose…

What you can do
  • Start and manage inbox placement tests: create a test, get seed addresses and a marker, wait for completion, delete a test.
  • Read results and diagnostics: per-mailbox results, inbox versus spam placement, content analysis, and worst-first fix suggestions.
  • Compare tests over time to see whether a fix worked.
  • List projects, folders, providers, tests and seed lists, and check the remaining test credit balance.
  • Retrieve shareable report links where the subscription includes them.
When to use it
Useful for email marketers and deliverability teams who want to check where campaigns land across providers and get prioritized remediation advice without leaving the assistant. Also handy for comparing a test with an earlier one after changing content or sending setup.
Requirements
Remote endpoint at over streamable HTTP; nothing to install locally. A GlockApps account with API access on the plan and an API key from Account → API / MCP. OAuth is the default flow; clients without OAuth can send the key as a Bearer token in the Authorization header. Test credits are required, one per test.
Before you install
Each create_test spends one test credit, and a send without the required marker still consumes it; delete_test refunds only while no result has arrived. delete_test removes the test and its results. Test creation is rate-limited per hour and per day. The API key is a credential: with the static-key method, regenerating the key breaks the connection. The connector cannot send email itself, so you must send the campaign from your own platform.

Installation

In SourceWeft

  1. Open GlockApps — Inbox Placement Testing in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.glockapps%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "glockapps-inbox-placement-testing": {
      "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.

https://api.glockapps.com/mcp

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

bash
claude mcp add --transport http glockapps https://api.glockapps.com/mcp

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" }        }    }}

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.

  1. list_projects — resolves the project everything else needs.
  2. create_test — costs 1 credit. Returns the seed addresses and a marker.
  3. 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.
  4. wait_for_test — results are usually usable about 10 minutes after sending.
  5. 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.

Readlist_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
Writecreate_test — costs 1 credit
Destructivedelete_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].

Source: README.md at commit 050ed62

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts