
Execute depth-map-estimator-mcp
io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 25, 2026
Premium agentic endpoint for depth-map-estimator-mcp.
Overview
A remote MCP endpoint that provides a depth-map estimator service, paid per call through an x402 crypto payment signature.
- What you can do
- Connects an assistant to a hosted depth-map-estimator service over SSE so it can request depth-map estimates for images or scenes, based on the server's name and description. No tool list is published, so the exact operations are not documented. Access is gated by a per-request payment rather than an account login.
- When to use it
- Consider it when you need depth-map estimation from an assistant and are willing to pay each call in USDC on Base Mainnet. It is not a good fit if you need a documented tool list, free access, or a local, self-hosted estimator.
- Requirements
- A remote SSE endpoint at the provider's host; no local runtime or package is needed. Each request must carry a Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, costing $0.35 USDC. A compatible crypto wallet and network access are required.
Installation
In SourceWeft
- Open Execute depth-map-estimator-mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. 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/io.github.Evozim%2Fdepth-map-estimator-mcp/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"execute-depth-map-estimator": {
"type": "sse",
"url": "https://api.m2mcent.com/depth-map-estimator-mcp/sse"
}
}
}Tools
0Version history
1- v2.0.0LatestSep 16, 2026
Score
67% 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
- Auth declaredRequired10 pts
- Tools listedRequired15 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.
- 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.