Ombo

cl.omboPublished by ombo.clOfficial publisherv0.1.0Updated Oct 24, 2026

Seguro contra el enojo: registra compras y tratos de una persona en Chile y reclama por ella.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant record a person's purchases and deals in Chile and file complaints on their behalf.

What you can do
Ombo is a remote MCP server reached over streamable HTTP at its provider's endpoint. According to its registry description, it records a person's purchases and dealings in Chile and files complaints for them. No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Consider it when an assistant needs to keep track of purchases or transactions made in Chile and to raise complaints about them on the user's behalf. It is aimed at consumer-side record keeping and claims rather than general data work.
Requirements
A remote streamable HTTP connection to the provider's endpoint, plus a bearer credential sent in the Authorization header. The credential is described as an agent key requested from the provider's GitHub repository. No packages, environment variables or local runtime are declared.
Before you install
The server requires a bearer secret in the Authorization header, so that credential should be treated as sensitive and scoped narrowly. It acts on the user's behalf by filing complaints, which is a write action to a third party; review what it submits before relying on it. No tool list is published, so verify the actual capabilities before installing.

Installation

In SourceWeft

  1. Open Ombo in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/cl.ombo%2Fombo/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": {
    "ombo": {
      "type": "http",
      "url": "https://ombo.cl/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestOct 13, 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.