Proof Inbox

com.proofinboxv0.1.1Updated Oct 28, 2026

Prepaid email-verify credits for MCP agents via Stripe Link.

The publisher's own server: Proof Holdings

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant verify email addresses using prepaid credits purchased through Stripe Link.

What you can do
  • The listing gives no tool list, so capabilities are inferred from the one-line description.
  • Verify email addresses on behalf of an assistant, drawing on prepaid credits.
  • Buy or top up verification credits through Stripe Link.
  • Connect over a hosted streamable HTTP endpoint rather than a local install.
When to use it
Consider it when an assistant needs to check whether email addresses are valid and you are willing to pay per use with prepaid credits, rather than running a local verification tool.
Requirements
A remote MCP endpoint at mcp.proofinbox.com over streamable HTTP; no local runtime, package, environment variables or headers are declared. A Stripe Link payment method is implied by the description for buying prepaid credits.
Before you install
The description indicates paid, prepaid credits purchased via Stripe Link, so using it involves spending money. No authentication method is declared in the manifest, so how credits are tied to your account is unclear. Email addresses submitted for verification are sent to a third-party service.

Installation

In SourceWeft

  1. Open Proof Inbox in the dashboard and add it to a workspace.
  2. 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.proofinbox%2Fverify/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.

{
  "mcpServers": {
    "proof-inbox": {
      "type": "http",
      "url": "https://mcp.proofinbox.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Proof integrations