webhook-inbox

co.kymac.inboxPublished by inbox.kymac.coOfficial publisherv0.4.1Updated Oct 27, 2026

Ephemeral HTTPS inbox for bots: mint URL, capture POSTs, list JSON. TEST. https://inbox.kymac.co

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint for an ephemeral HTTPS inbox: mint a URL, capture incoming POSTs, and list them as JSON.

What you can do
  • Mint a temporary HTTPS inbox URL for a bot or service to receive webhooks.
  • Capture incoming POST requests sent to that URL.
  • List the captured requests as JSON for inspection.
  • No individual tools are listed in the manifest, so exact operations come from the service itself.
When to use it
Useful when you need a throwaway endpoint to receive and inspect webhook callbacks during testing or debugging, without standing up your own server.
Requirements
A remote streamable HTTP endpoint at inbox.kymac.co; nothing to install locally. An API key is required, sent either as an Authorization bearer token or an X-API-Key header; keys are minted via the service's key endpoint. Network access to the service is needed.
Before you install
The service asks for an API key (Authorization or X-API-Key header); treat it as a secret and keep it out of shared logs. Webhook payloads you send to the inbox are stored by a third party, so avoid sensitive data. The registry description marks the service as a test, so do not rely on it for production traffic.

Installation

In SourceWeft

  1. Open webhook-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/co.kymac.inbox%2Fwebhook-inbox/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": {
    "webhook-inbox": {
      "type": "http",
      "url": "https://inbox.kymac.co/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v0.4.1LatestSep 18, 2026

Score

28% 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
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.