Is the OMENZ agent tools MCP server down?

mcp-registry/org.omenz.www/agent-tools · registry v1.2.1 · server reports v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:34 UTC · handshake 206ms

As of 2026-11-22 16:34 UTC, the OMENZ agent tools MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
706
outages (90d)
0
tools
122

For agents that pay: Authorize (OFAC screen), Guard, Send Check, Checkout, Rescue, budgets, x402.

Point your MCP client at this streamable-http endpoint: https://www.omenz.org/mcp

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 4 warning(s) across 122 tool(s); ~24,770 tokens of tool definitions.
Scores higher than 24% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~24,770 tokens per session — more than 95% of servers.
88 → 80 since 2026-11-17
no tool-poisoning patterns
Schemas79
Descriptions89
Safety hints100
Token cost35
Client compatibility70
Protocol100
Reliability100
Stability88

What to fix (6)

122 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

28 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: checkout_close, context_diet, contract_accept, dedupe, delivery_check and 23 more

5 parameter(s) across 1 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: omenz_tell_us_what_you_need

Loading this server's tool list costs an agent ~24,770 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

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 →

In the last 30 days: 0 tool(s) removed and 3 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 28 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Forg.omenz.www%2Fagent-tools/fixes

checkout_close 1 change
{
  "name": "checkout_close",
  "description": "OMENZ Checkout (close): ONE call after paying. Send checkout_id + the tx hash (or PAYMENT-RESPONSE header) + the response you got. Verifies settlement on Base against the authorized payee and amount, checks delivery against the seller's advertised output, returns a signed Spend Receipt (GOOD_BUY / PAID_NOT_DELIVERED / PAYMENT_NOT_CONFIRMED), gives the money back to the Shared Budget if you never paid, and updates the seller's track record. High volume: checkout/close/credit at 1% (min $0.0002). ",
  "inputSchema": {
    "type": "object",
    "required": [
      "checkout_id"
    ],
    "properties": {
      "schema": {
        "type": "object",
        "description": "schema"
      },
      "tx_hash": {
        "type": "string",
        "description": "tx hash"
      },
      "not_paid": {
        "type": "boolean",
        "description": "not paid"
      },
      "delivered": {
        "description": "delivered",
        "type": "string"
      },
      "checkout_id": {
        "type": "string",
        "description": "checkout id"
      },
      "payment_response": {
        "type": "string",
        "description": "payment response"
      },
      "release_if_unconfirmed": {
        "type": "boolean",
        "description": "release if unconfirmed"
      }
    }
  },
  "annotations": {
    "title": "OMENZ Checkout (close)",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  },
  "title": "OMENZ Checkout (close)"
}
context_diet 1 change
{
  "name": "context_diet",
  "description": "Context Diet: shrink a packet before it fills your context: drops empty fields, dedupes lists, cuts long strings to a head + sha256 pointer, caps list length, always keeps required fields; reports bytes and approximate tokens saved. By OMENZ. (MCP calls run in AYNE, the free playzone; production: POST https://www.omenz.org/api/tollbooth/v1/context-diet, $0.002 via x402.)",
  "inputSchema": {
    "type": "object",
    "required": [
      "packet"
    ],
    "properties": {
      "packet": {
        "description": "packet",
        "type": "string"
      },
      "required": {
        "type": "array",
        "description": "required"
      },
      "max_list_items": {
        "type": "integer",
        "description": "max list items"
      },
      "max_string_chars": {
        "type": "integer",
        "description": "max string chars"
      }
    }
  },
  "annotations": {
    "title": "Context Diet",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  },
  "title": "Context Diet"
}
contract_accept 1 change
{
  "name": "contract_accept",
  "description": "Acceptance Test as a Service + escrow verdict: a neutral party runs the contract's tests on what was delivered. PASS/FAIL per test, escrow_verdict RELEASE/REFUND (OMENZ never holds funds: the payer acts on it), and a signed attestation that feeds the seller's Reputation Receipts. By OMENZ. (MCP calls run in AYNE, the free playzone; production: POST https://www.omenz.org/api/tollbooth/v1/contract/accept, $0.005 via x402.)",
  "inputSchema": {
    "type": "object",
    "required": [
      "token",
      "delivered"
    ],
    "properties": {
      "token": {
        "type": "string",
        "description": "token"
      },
      "delivered": {
        "description": "delivered",
        "type": "string"
      }
    }
  },
  "annotations": {
    "title": "Acceptance Test as a Service + escrow verdict",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  },
  "title": "Acceptance Test as a Service + escrow verdict"
}

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/org.omenz.www/agent-tools"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.omenz.www/agent-tools"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Forg.omenz.www%2Fagent-tools.svg)](https://glimind.com/server/mcp-registry%2Forg.omenz.www%2Fagent-tools?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Forg.omenz.www%2Fagent-tools?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Forg.omenz.www%2Fagent-tools.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a3baf8f5722418c9…, first seen 2026-11-22, included at leaf 384272 of 384,618. Version history · verify what your client received.

Tools (122)

Compare: most reliable other servers · most reliable finance servers · most reliable payments servers · most reliable knowledge servers · most reliable security 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the OMENZ agent tools MCP server down right now?

As of 2026-11-22 16:34 UTC, the OMENZ agent tools MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does OMENZ agent tools MCP server provide?

OMENZ agent tools MCP server advertises 122 tools, including agent_ready, alive, allowance, authorize, authorize_get.

How do I install OMENZ agent tools MCP server?

Point your MCP client at this streamable-http endpoint: https://www.omenz.org/mcp

Is the OMENZ agent tools MCP server safe to connect to an AI agent?

Glimind scanned all 122 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 OMENZ agent tools 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.

Feedback
Help us improve