3D-MeshWeaver

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Mesh spatial optimizer reducing geometric overhead in 3D assets.

VerifiedSSEWeb executableMedia & Design

Overview

AI-generated overview

A remote MCP endpoint that optimizes 3D mesh geometry to reduce spatial and geometric overhead in 3D assets.

What you can do
3D-MeshWeaver is a remote MCP server described as a mesh spatial optimizer that reduces geometric overhead in 3D assets. The registry description is brief and no tool list or README is provided, so the exact operations it exposes are not documented. It is reached over SSE at a hosted endpoint rather than installed locally.
When to use it
Consider it when an assistant needs to process or simplify 3D mesh assets and you are comfortable sending those assets to a third-party hosted service. Because no tool list is published, verify the available operations before relying on it in a pipeline.
Requirements
A remote SSE endpoint at no local package or runtime is declared. No authentication is declared, but a payment-signature header is listed as a secret, described as a Base64-encoded EIP-3009 TransferWithAuthorization signature required for premium settlement. Network access is required.
Before you install
The server expects a payment-signature header carrying a signed transfer authorization, which can authorize a payment; treat it as sensitive and understand what it permits before supplying it. No tool list is published, so what the server does with submitted 3D assets is unclear, and assets are sent to a third-party hosted endpoint.

Installation

In SourceWeft

  1. Open 3D-MeshWeaver in the dashboard and add it to a workspace.
  2. 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%2F3d-meshweaver/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "3d-meshweaver": {
      "type": "sse",
      "url": "https://3d-meshweaver-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.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.