API Tools

webhookjar.com

A webhook inbox service for creating endpoints, listing and inspecting incoming requests, and waiting for requests during API integration and testing.

1 endpoint12 known toolsFirst detected October 28, 2026Last detected October 28, 2026

ENDPOINT 1

https://webhookjar.com/mcp

No auth detected

MCP server metadata

Name: webhookjar
Version: 1.0.0

Capabilities

tools

Server instructions

Webhook Jar catches webhooks so you can see exactly what a service sent. Typical flow: create_inbox, give its post_url to the service (or send to it yourself), trigger the event, then wait_for_request and read the request it returns. get_request shows the headers, raw body and whether the signature matched the inbox's signing secret. Ids are ib_... for inboxes and rq_... for requests. Times are UTC. Full reference: https://webhookjar.com/llms.txt

Known tools 12

create_inbox

Makes a kept inbox on your account and returns its post_url (give this to the service that sends webhooks) and view_url (for a person to watch it live).

Inferred read-only

list_inboxes

Every open inbox on your account, busiest first, with its post_url, request count and last request time.

Inferred read-only

get_inbox

One inbox: its URLs, counts, what it answers senders with, and its forwarding.

Inferred read-only

wait_for_request

Holds until a request lands in the inbox, then returns it in full (headers, body, provider, event, signature check).

Inferred read-only

list_requests

An inbox's requests, newest first, without bodies: id, time, method, provider, event, a plain headline and the signature result.

Inferred read-only

send_sample

Delivers a real provider webhook into the inbox, with the provider's own headers, body and signature, so you can test a handler with no provider account.

Inferred read-only

get_request

Everything caught, as it came: method, path, query, headers, the raw body (base64 when not text), sender, event, and whether its signature matched the inbox's signing secret (verified, failed, or null with no secret set), with the checks behind it.

Inferred read-only

set_inbox_answer

Changes what the inbox sends back to senders, to test how a provider handles failures: status (200, 201, 202, 204, 400, 401, 403, 404, 409, 410, 422, 429, 500, 502, 503), body as a string, delay (0, 2, 10, 30 seconds), and challenges (answer Slack, Meta and Twitch verification for you).

Potential side effects

set_forwarding

Sends every request that lands on to your own public http or https address, exactly as it came, with retries.

Inferred read-only

replay_request

Sends one captured request to the inbox's forward address again, exactly as it came, and returns what your server answered and how long it took.

Inferred read-only

delete_inbox

Deletes the inbox and every request in it.

Inferred read-only

get_usage

Your plan, calls and captures used today and their limits, inboxes in use, history kept and when the day resets.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.webhookjar]
url = "https://webhookjar.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "webhookjar": {
      "type": "http",
      "url": "https://webhookjar.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: webhookjar
Remote MCP URL: https://webhookjar.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "webhookjar": {
      "url": "https://webhookjar.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "webhookjar": {
      "type": "http",
      "url": "https://webhookjar.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "webhookjar",
  "transport": "streamable-http",
  "url": "https://webhookjar.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.