Claim MCP profile: mailkite/mailkite-mcp

[bucabay]

TensorBlock profile URL or server id: github-mailkite-mailkite-mcp-19d44f39 · https://tensorblock.co/mcp/servers/github-mailkite-mailkite-mcp-19d44f39

Project URL: https://github.com/mailkite/mailkite-mcp

Maintainer handle: @bucabay

Maintainer proof:
I (@bucabay) hold admin permission on the mailkite GitHub org that owns this repo. Verification: https://github.com/mailkite/mailkite-mcp (owner mailkite; this account is listed as a maintainer in the repo's glama.json).

Metadata to display:

• Name: MailKite
• Tagline: Give any AI agent its own real email inbox
• Category: Communication / Email
• Remote endpoint: https://mcp.mailkite.dev/mcp (Streamable HTTP)
• Auth: OAuth 2.0 (dynamic client registration, /.well-known discovery) · API key (mk_live_…)
• License: MIT
• Docs: https://mailkite.dev/docs/ai-agents
• Homepage: https://mailkite.dev
• Install: claude mcp add --transport http mailkite https://mcp.mailkite.dev/mcp

[tensorblock-mcp-automation]

Thanks for claiming this MCP profile in #2012.
What happens next:

• If the profile id and project URL match the index, automation will draft a metadata PR for maintainer review.
• After that PR is merged and deployed, the profile can show the requested maintainer handle as a claimed profile.
• Claiming is separate from TensorBlock verification; stronger verification signals can be added later through metadata updates.
• If the profile also needs install/auth/docs updates, include them here or open a metadata PR.
  Profile links:
• We could not normalize a server id from the submitted profile field yet. Paste the full TensorBlock profile URL or API profile URL if you have it.

Profile claim checklist:

• The submitted project URL matches the indexed profile source or official project docs.
• The maintainer handle is the GitHub/package/org handle you want displayed on the profile.
• Optional proof links can be added as supporting context, but claim metadata can be accepted without them.
• TensorBlock verification is tracked separately from the claimed profile status.

Useful links:

• Contribution guide: https://github.com/TensorBlock/awesome-mcp-servers/blob/main/docs/index-alpha/contribution-guide.md
• Hosted MCP Index API: https://mcp-index.tensorblock.co
• TensorBlock Discord: https://discord.com/invite/Ej5NmeHFf2

If the index is useful for your project, starring the repo helps more MCP builders discover it.

[tensorblock-mcp-automation]

I could not create a claim-profile metadata PR yet.

What needs attention:

• A valid TensorBlock profile URL or server id is required.
• Indexed profile not found for server id "".
• Project URL is required.
• Maintainer handle is required.

Update this issue with the corrected profile id, matching project URL, and maintainer handle. Optional proof links can still be added as supporting context. The automation will try again when the issue is edited.