mcp-registry/org.omenz.www/agent-tools · registry v1.2.1 · server reports v1.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs 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.
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
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 →
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 →
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 →
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
{
"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)"
}{
"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"
}{
"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 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.
dispute_packet ~410 tokensguard ~397 tokenscheckout_open ~379 tokensspend_receipt ~365 tokensbudget_delegate ~348 tokensStatic 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Forg.omenz.www%2Fagent-tools?ref=badge)
<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>
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.
Compare: most reliable other servers · most reliable finance servers · most reliable payments servers · most reliable knowledge servers · most reliable security servers
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.
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"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
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.
OMENZ agent tools MCP server advertises 122 tools, including agent_ready, alive, allowance, authorize, authorize_get.
Point your MCP client at this streamable-http endpoint: https://www.omenz.org/mcp
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.
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.