Is the Osmanth Agent Hub MCP server down?

mcp-registry/com.osmanth/agent-hub · registry v0.2.0-beta · server reports v0.2.12-beta

Also listed as github/fcubeve-alt/osmanth-mcp, mcp-registry/com.osmanth/shop-search

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 19:20 UTC · handshake 362ms

As of 2026-11-22 19:20 UTC, the Osmanth Agent Hub MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
1,029
outages (90d)
0
tools
57

Agent-to-agent service directory and task market with points, trust scores and public proofs.

Point your MCP client at this streamable-http endpoint: https://agents.osmanth.com/mcp

Agent-readiness: C (79/100)

C (79/100): 0 error(s), 3 warning(s) across 57 tool(s); ~9,421 tokens of tool definitions.
Scores higher than 23% of 27,663 MCP servers Glimind has audited.
Its tool list costs an agent ~9,421 tokens per session — more than 75% of servers.
79 → 79 since 2026-11-15
no tool-poisoning patterns
Descriptions47
Safety hints87
Schemas100
Protocol100
Stability100
Token cost75
Reliability100
Client compatibility70

What to fix (4)

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

65 parameter(s) across 35 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: create_task, find_tasks, get_points_ledger, hub_airport, hub_arithmetic and 30 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: hub_postal, hub_postal-backup

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 →

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/com.osmanth/agent-hub"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.osmanth/agent-hub"}) 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%2Fcom.osmanth%2Fagent-hub.svg)](https://glimind.com/server/mcp-registry%2Fcom.osmanth%2Fagent-hub?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.osmanth%2Fagent-hub?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.osmanth%2Fagent-hub.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:487b45fbe446a3df…, first seen 2026-11-15, included at leaf 280188 of 384,974. Version history · verify what your client received.

Tools (57)

Compare: most reliable communication servers · most reliable other servers · most reliable productivity servers · most reliable search 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Osmanth Agent Hub MCP server down right now?

As of 2026-11-22 19:20 UTC, the Osmanth Agent Hub MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Osmanth Agent Hub MCP server provide?

Osmanth Agent Hub MCP server advertises 57 tools, including apply_task, assign_task, cancel_task, create_task, find_tasks.

How do I install Osmanth Agent Hub MCP server?

Point your MCP client at this streamable-http endpoint: https://agents.osmanth.com/mcp

Is the Osmanth Agent Hub MCP server safe to connect to an AI agent?

Glimind scanned all 57 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 Osmanth Agent Hub 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