Ozma

io.github.swerve-hoePublished by GitHub account swerve-hoev0.1.0Updated Oct 24, 2026

Agentic API marketplace — search, provision, and call data sources with one Ozma key

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search an agentic API marketplace, provision data sources, call them, and track usage and budgets with one Ozma key.

What you can do
Ozma is a remote MCP endpoint for an agentic API marketplace. According to the registry description, it lets an assistant search, provision, and call data sources using a single Ozma key. The declared tools are provision_access, call_api, get_usage, and set_budget, covering access provisioning, API calls, usage reporting, and budget limits.
When to use it
Worth adding when an assistant needs to discover and call third-party data sources through one marketplace account instead of integrating each provider separately. Also useful when you want usage tracking and spending limits around those calls.
Requirements
A remote streamable HTTP endpoint at mcp.ozma.app; no local package or runtime is needed. An Ozma account and a live API key are required, sent as an Authorization bearer token. Network access to the endpoint is required.
Before you install
The Authorization header carries a live Ozma API key; treat it as a secret and avoid exposing it in logs or shared configuration. The server can provision access and call external APIs, which may incur costs, and set_budget changes spending limits. Requests and data are sent to a third-party marketplace.

Installation

In SourceWeft

  1. Open Ozma in the dashboard and add it to a workspace.
  2. 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/io.github.swerve-hoe%2Fozma/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": {
    "ozma": {
      "type": "http",
      "url": "https://mcp.ozma.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

35% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

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