Execute container-ship-router-mcp

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

Premium agentic endpoint for container-ship-router-mcp.

The publisher's own server: 370.ai — AI Gateway: 100+ Chat Models, Image & Speech Generation

VerifiedSSEWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for container-ship-router-mcp that requires a paid x402 payment signature header before use.

What you can do
The listing provides no tool list, so the assistant-facing capabilities are not documented beyond the server being a premium agentic endpoint for container-ship-router-mcp. Access is gated by a payment signature supplied in a request header. No description, instructions or README explains what actions the tools perform.
When to use it
Only worth considering if you already know the container-ship-router-mcp service and want to reach it through a hosted endpoint that settles per-request payments in USDC on Base Mainnet. Without documentation of its tools, it is hard to justify adding it for general use.
Requirements
A remote SSE endpoint at the provider's host; no local package or runtime is needed. Each request needs a Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, priced at $0.25 USDC. A wallet able to produce that signature is therefore required.
Before you install
Using it costs money: each call is settled in USDC on Base Mainnet, so a funded wallet and spending limits matter. The Payment-Signature header is a cryptographic authorization tied to your wallet; treat it as sensitive. The server's tools and data handling are undocumented, so what it does with your inputs and what third parties receive cannot be verified.

Installation

In SourceWeft

  1. Open Execute container-ship-router-mcp 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%2Fcontainer-ship-router-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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "execute-container-ship-router": {
      "type": "sse",
      "url": "https://api.m2mcent.com/container-ship-router-mcp/sse"
    }
  }
}

Tools

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

Version history

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

Other Router integrations