Home / MCP registry index / help.awning/awning

Awning

help.awning/awning in the official MCP registry. Endpoint https://api.awning.help/mcp.

The registry describes it as: Find and book local services, classes and rentals; businesses set up and manage their pages.

We read its 36 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "awning": {
      "url": "https://api.awning.help/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"awning","type":"http","url":"https://api.awning.help/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

search_businesses get_business get_availability create_hold create_booking get_booking cancel_booking my_bookings my_profile logout owner_import_source owner_setup owner_photos owner_remove_photos owner_preview owner_submit owner_status owner_list_bookings owner_get_schedule owner_decide_booking owner_cancel_booking owner_block_time owner_pause owner_update_business owner_set_schedule owner_update_offering owner_add_offering owner_upsert_sessions op_connect_telegram op_applications op_decide_application op_leads op_decide_lead op_analytics op_businesses op_suspend_business

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/help-awning-awning/badge.svg)](https://lazaretto.dev/mcp-registry/help-awning-awning)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.