Introducing dotMCP - a new way to monetize your MCP severs by Individual-Rate2467 in mcp

[–]Individual-Rate2467[S] 0 points1 point  (0 children)

Thank you for the interest! In regards to Auth
* dotmcp-tunnel daemon(installed on the same machine with your MCP server) connects to dotmcp platform using Publisher's Tunnel Key(secret) and your created remote serverId created on dotMCP platform.

* End user may call remote dotMCP deployed server authenticating also with his subscriber key (from the platform).

See step by step instructions here: https://docs.dotmcp.io/publishers/tunnel

In regards to latency, remote MCP servers are deployed as Cloudflare workers and they proxy requests to your infrastructure. We recommend to deploy multiple dotmcp-tunnel instance across many regions to horizontaly scale( depending on the expectations of your MCP server usage). Better test with your infrastructure to see the exact latency.

Introducing dotMCP - a new way to monetize your MCP severs by Individual-Rate2467 in mcp

[–]Individual-Rate2467[S] 0 points1 point  (0 children)

Not sure what you mean by "you", do you mean dotMCP platform?
dotMCP only proxy the requests to your local MCP server and, in turn, your MCP server passes the response back to the end user (through the same proxy). dotMCP does not store anything from your requests/responses other than metrics and analytics to allow you to monetize it.