Is the Awning MCP server down?

mcp-registry/help.awning/awning · v0.1.0

healthy
Last checked 2026-10-18 13:39 UTC · handshake 587ms

As of 2026-10-18 13:39 UTC, the Awning 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
3,099
outages (90d)
0
tools
36

Find and book local services, classes and rentals; businesses set up and manage their pages.

Install Awning MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http awning-mcp-server https://api.awning.help/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "awning-mcp-server": {
      "type": "http",
      "url": "https://api.awning.help/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 4 warning(s) across 36 tool(s); ~8,304 tokens of tool definitions.
Scores higher than 12% of 15,375 MCP servers Glimind has audited.
Its tool list costs an agent ~8,304 tokens per session — more than 65% of servers.
75 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints88
Token cost89
Client compatibility70
Protocol100
Reliability85
Stability64

What to fix (6)

1 tool definition(s) exceed ~1,200 tokens each (largest: owner_setup, ~1,325).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~725 tokens every session. How to fix →

Tools: owner_setup · saves ~725 tokens/session

86 parameter(s) across 32 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: cancel_booking, create_booking, create_hold, get_availability, get_booking and 27 more

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

Handshake + tools/list takes ~2,446 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 →

In the last 30 days: 0 tool(s) removed and 9 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 →

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

Agents: watch_tool({"toolId": "mcp-registry/help.awning/awning"}) 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%2Fhelp.awning%2Fawning.svg)](https://glimind.com/server/mcp-registry%2Fhelp.awning%2Fawning?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fhelp.awning%2Fawning?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fhelp.awning%2Fawning.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fhelp.awning%2Fawning.svg
   :target: https://glimind.com/server/mcp-registry%2Fhelp.awning%2Fawning?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:ccd43f4db3d10644…, first seen 2026-10-17, included at leaf 1008 of 22,126. Version history · verify what your client received.

Tools (36)

Compare: most reliable calendar servers · most reliable knowledge servers · most reliable security servers · most reliable profile servers · most reliable analytics 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 Awning MCP server down right now?

As of 2026-10-18 13:39 UTC, the Awning 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 Awning MCP server provide?

Awning MCP server advertises 36 tools, including cancel_booking, create_booking, create_hold, get_availability, get_booking.

How do I install Awning MCP server?

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

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

Glimind scanned all 36 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 Awning 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.