Is the Aeroz MCP server down?

mcp-registry/io.aeroz/aeroz · v0.2.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:39 UTC · handshake 926ms

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

uptime (30d checks)
100%
checks observed
888
outages (90d)
0
tools
47

Prove a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody.

Point your MCP client at this streamable-http endpoint: https://api.aeroz.io/mcp

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 3 warning(s) across 47 tool(s); ~8,596 tokens of tool definitions.
Scores higher than 35% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~8,596 tokens per session — more than 75% of servers.
84 → 84 since 2026-11-16
no tool-poisoning patterns
Descriptions68
Safety hints100
Schemas89
Protocol100
Stability100
Token cost75
Reliability100
Client compatibility70

What to fix (4)

47 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 →

63 parameter(s) across 15 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: bind_graded_item, create_product, create_shipment, find_unit, graded_item and 10 more

1 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: record_ai_decision

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: 1 corrected tool definition

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

record_ai_decision 1 change
{
  "name": "record_ai_decision",
  "description": "Append a decision (or an incident) to an AI system's signed, append-only record, by the rules of POST /v1/ai/systems/{id}/records. Send the input and output text or their SHA-256: only the hash is kept, never the text. Nothing recorded can be edited or removed, so record what actually happened, not a guess.",
  "inputSchema": {
    "type": "object",
    "required": [
      "system_id"
    ],
    "properties": {
      "kind": {
        "enum": [
          "decision",
          "incident"
        ],
        "type": "string"
      },
      "note": {
        "type": "string",
        "description": "Required for an incident."
      },
      "input": {
        "description": "The input, as text or JSON. Hashed, then dropped.",
        "type": "string"
      },
      "output": {
        "description": "The output, as text or JSON. Hashed, then dropped.",
        "type": "string"
      },
      "ref_id": {
        "type": "string",
        "description": "For an incident: the decision (air_…) it is about."
      },
      "subject": {
        "type": "string",
        "description": "What it was about: a unit, GTIN + serial, case id."
      },
      "system_id": {
        "type": "string",
        "description": "aisys_…, from list_ai_systems."
      },
      "confidence": {
        "type": "number",
        "description": "0 to 1."
      },
      "input_sha256": {
        "type": "string"
      },
      "output_label": {
        "type": "string",
        "description": "A short readable label, e.g. suspect, clear."
      },
      "model_version": {
        "type": "string"
      },
      "output_sha256": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "title": "record_ai_decision",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": true
  },
  "title": "record_ai_decision"
}

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.aeroz/aeroz"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.aeroz/aeroz"}) 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%2Fio.aeroz%2Faeroz.svg)](https://glimind.com/server/mcp-registry%2Fio.aeroz%2Faeroz?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.aeroz%2Faeroz?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.aeroz%2Faeroz.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:e51dcc4f8061409b…, first seen 2026-11-16, included at leaf 292427 of 384,622. Version history · verify what your client received.

Tools (47)

Compare: most reliable communication servers · most reliable knowledge servers · most reliable other servers · most reliable retrieval servers · most reliable database 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 Aeroz MCP server down right now?

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

How many tools does Aeroz MCP server provide?

Aeroz MCP server advertises 47 tools, including agent_conversation, ask_agent, bind_graded_item, business_brief, chain_readiness.

How do I install Aeroz MCP server?

Point your MCP client at this streamable-http endpoint: https://api.aeroz.io/mcp

Is the Aeroz MCP server safe to connect to an AI agent?

Glimind scanned all 47 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 Aeroz 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