Is the Swerve Hoe Ozma MCP server down?

mcp-registry/io.github.swerve-hoe/ozma · v0.1.0

unknown
Last checked 2026-10-14 03:06 UTC

As of 2026-10-14 03:06 UTC, the Swerve Hoe Ozma MCP server is unknown with a Glimind reliability score of 62/100 (grade C). Over the last 30 days it answered 80% of Glimind's liveness checks.

uptime (30d checks)
80%
checks observed
10
outages (90d)
0
tools
13

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

Point your MCP client at this streamable-http endpoint: https://mcp.ozma.app/mcp

Agent-readiness: D (58/100)

D (58/100): 1 error(s), 4 warning(s) across 13 tool(s); ~1,185 tokens of tool definitions.
Scores higher than 0% of 15,364 MCP servers Glimind has audited.
Its tool list costs an agent ~1,185 tokens per session — lighter than 70% of servers.
no tool-poisoning patterns
Schemas100
Descriptions31
Safety hints8
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (6)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

13 of 13 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: call_api, create_checkout, discover_tools, get_api_details, get_balance and 8 more

28 parameter(s) across 11 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: call_api, create_checkout, discover_tools, get_api_details, get_leaderboard and 6 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: run_probe, set_budget

Handshake + tools/list takes ~2,386 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 11 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.swerve-hoe%2Fozma/fixes

create_checkout 1 change 
{
  "name": "create_checkout",
  "description": "Create a Stripe Checkout session to buy prepaid credits",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "pack": {
        "type": "string"
      },
      "amount_cents": {
        "type": "integer",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
get_api_details 1 change 
{
  "name": "get_api_details",
  "description": "Get full details for an API listing by slug",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_balance 1 change 
{
  "name": "get_balance",
  "description": "Get prepaid credit balance and billing status for the current org",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.swerve-hoe/ozma"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.swerve-hoe/ozma"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.swerve-hoe%2Fozma.svg)](https://glimind.com/server/mcp-registry%2Fio.github.swerve-hoe%2Fozma?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.swerve-hoe%2Fozma?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.swerve-hoe%2Fozma.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.swerve-hoe%2Fozma.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.swerve-hoe%2Fozma?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:86e9d16b25505e18…, first seen 2026-10-17, included at leaf 8535 of 21,589. Version history · verify what your client received.

Tools (13)

Compare: most reliable other servers · most reliable payments servers · most reliable search servers · most reliable data servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Swerve Hoe Ozma MCP server down right now?

As of 2026-10-14 03:06 UTC, the Swerve Hoe Ozma MCP server is unknown with a Glimind reliability score of 62/100 (grade C). Over the last 30 days it answered 80% of Glimind's liveness checks.

How many tools does Swerve Hoe Ozma MCP server provide?

Swerve Hoe Ozma MCP server advertises 13 tools, including call_api, create_checkout, discover_tools, get_api_details, get_balance.

How do I install Swerve Hoe Ozma MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.ozma.app/mcp

Is the Swerve Hoe Ozma MCP server safe to connect to an AI agent?

Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Swerve Hoe Ozma MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.