Developer · Remote MCP server

Webmcpactionreceipt MCP

Paid remote MCP for WebMCP action receipt MCP, structured receipts, audit logs, and reviewer-ready e.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.clauxel.webmcpactionreceipt/webmcpactionreceipt-mcp
Version
1.0.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-05-20
Updated
2026-05-20
Publisher
com.clauxel.webmcpactionreceipt
Namespace
Namespace verified by the MCP Registry via the domain webmcpactionreceipt.clauxel.com or a parent domain of it · how
Repository
github.com/clauxel/webmcp-action-receipt-gate-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://webmcpactionreceipt.clauxel.com/mcpAuthorization

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
No - could not connect (DNS or connection failure)
Handshake
-
Checked on
2026-10-05

How the live check works

How to connect Webmcpactionreceipt MCP

Webmcpactionreceipt MCP is a remote MCP server: there is nothing to install. Its endpoint is https://webmcpactionreceipt.clauxel.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization. Clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Webhook ToolkitWebhook URLs for AI agents: receive, wait for, replay, sign and verify webhooks (Stripe, GitHub…).Remote & Local · HTTP, stdioLive check: ✓ handshakewebhook-toolkit.com
webhook.coReceive, inspect, replay and deliver webhooks - with signature verification and agent triggers.Remote · HTTPLive check: sign-in requiredmcp.webhook.co
Webhook.site MCP ServerCapture HTTP, email, and DNS callbacks with webhook.site from MCP clients.Local · stdioPyPI: webhook-mcp-server
WebhookTest.netAnonymous webhook capture, inspection, waiting, and response configuration for AI agents.Remote · HTTPLive check: ✓ handshakewebhooktest.net
WebnavA zero-LLM MCP server that replays recorded site maps instead of re-exploring browser routes.Local · stdionpm: @dikshanty94/webnav
WeboperatorHands your live Chrome tab to any MCP client - snapshot, navigate, click, type, extract.Local · stdionpm: weboperator-mcp
WebsharpSearch the web and extract article text for LLMs.Local · HTTPOCI image (Docker): docker.io/jessegador/websharp-mcp:v0.99.0-rc2
Website Change Monitor & Deterministic DiffDeterministic webpage change detection, hashes and text diffs for recurring monitoring via x402 MCP.Remote · HTTPLive check: ✓ handshakemcp.apify.com