
Execute ambient-occlusion-map-mcp
io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026
Premium agentic endpoint for ambient-occlusion-map-mcp.
Overview
A remote MCP endpoint that provides a premium ambient-occlusion map service, paid per request via an x402 crypto signature.
- What you can do
- The listing names no tools, so capabilities are inferred from the description only: it presents itself as a premium agentic endpoint for ambient-occlusion map work, likely generating or serving ambient-occlusion maps for 3D or rendering workflows. Access is gated by a payment signature rather than an account login. No further detail on inputs, outputs or formats is provided.
- When to use it
- Consider it only if you need ambient-occlusion map output from a hosted service and are prepared to pay per request in USDC on Base Mainnet. Without a tool list or documentation, it is hard to judge fit in advance.
- Requirements
- A remote SSE endpoint at the provider's host; no local runtime or package. Each request needs a Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, quoted at $0.15 USDC. A compatible crypto wallet and network access are implied.
Installation
In SourceWeft
- Open Execute ambient-occlusion-map-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%2Fambient-occlusion-map-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-ambient-occlusion-map": {
"type": "sse",
"url": "https://api.m2mcent.com/ambient-occlusion-map-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.