Checkout Cod

lat.oktopusPublished by oktopus.latOfficial publisherv0.1.0Updated Oct 27, 2026

Riel de pago contra entrega (COD) para LATAM: crea órdenes y cobra con Dropi vía MCP.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for LATAM cash-on-delivery checkout that lets an assistant create orders and collect payment through Dropi.

What you can do
  • Create cash-on-delivery (COD) orders for LATAM through the connected service.
  • Collect payment for those orders via Dropi.
  • No individual tools are listed in the registry entry, so the exact operations an assistant can call are not documented here.
When to use it
Consider it when an assistant needs to place or manage cash-on-delivery orders in Latin America and take payment through Dropi, for example in a sales or fulfillment workflow.
Requirements
A remote MCP endpoint at the provider's site, reached over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
It handles real orders and payments, so assistant actions can create orders and move money; confirm amounts and recipients before use. Access is granted through OAuth, so review which account and permissions you authorize. Order and customer data is sent to the provider and to Dropi.

Installation

In SourceWeft

  1. Open Checkout Cod in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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/lat.oktopus%2Fcheckout-cod/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "checkout-cod": {
      "type": "http",
      "url": "https://www.oktopus.lat/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% 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 listed15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.