Free instant HTML hosting API. Deploy HTML pages, upload files, or extract ZIP archives with automatic TTL expiry and delete tokens. No API keys required.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
fork_sitebatch_deploydeploy_html4 fields changedInput schema / properties / html / descriptionPrevious value: -"HTML content to deploy"New value: +"HTML content to deploy (use this OR markdown, not both)"Input schema / properties / markdownAdded value: +{
+ "description": "Markdown content to deploy — auto-rendered to a styled HTML page (use this OR html, not both)",
+ "type": "string"
+}Input schema / properties / titleAdded value: +{
+ "description": "Page title for markdown rendering (auto-detected from first # heading if omitted)",
+ "type": "string"
+}Input schema / requiredRemoved value: -[
- "html"
-]update_site4 fields changedInput schema / properties / html / descriptionPrevious value: -"New HTML content"New value: +"New HTML content (use this OR markdown, not both)"Input schema / properties / markdownAdded value: +{
+ "description": "New Markdown content — auto-rendered to styled HTML (use this OR html, not both)",
+ "type": "string"
+}Input schema / properties / titleAdded value: +{
+ "description": "Page title for markdown rendering (auto-detected from first # heading if omitted)",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "siteId",
- "deleteToken",
- "html"
-]New value: +[
+ "siteId",
+ "deleteToken"
+]get_site_analyticsbatch_deletedeploy_html1 field changedInput schema / properties / passwordExpiryAdded value: +{
+ "description": "Password cookie expiry in hours (1-720, default 24). Only applies when password is set.",
+ "type": "number"
+}deploy_html1 field changedInput schema / properties / passwordAdded value: +{
+ "description": "Optional password to protect the page. Visitors must enter this password to view the content.",
+ "type": "string"
+}update_site1 field changedInput schema / properties / passwordAdded value: +{
+ "description": "Set or update password protection. Empty string removes password.",
+ "type": "string"
+}deploy_html3 fields changedInput schema / properties / ogDescriptionAdded value: +{
+ "description": "Open Graph description for social media previews (max 500 chars)",
+ "type": "string"
+}Input schema / properties / ogImageAdded value: +{
+ "description": "URL to Open Graph image for social media previews (1200x630px recommended)",
+ "type": "string"
+}Input schema / properties / ogTitleAdded value: +{
+ "description": "Open Graph title for social media previews (max 200 chars)",
+ "type": "string"
+}update_site3 fields changedInput schema / properties / ogDescriptionAdded value: +{
+ "description": "Open Graph description for social media previews (max 500 chars)",
+ "type": "string"
+}Input schema / properties / ogImageAdded value: +{
+ "description": "URL to Open Graph image for social media previews (1200x630px recommended)",
+ "type": "string"
+}Input schema / properties / ogTitleAdded value: +{
+ "description": "Open Graph title for social media previews (max 200 chars)",
+ "type": "string"
+}deploy_html2 fields changedInput schema / properties / slugAdded value: +{
+ "description": "Custom vanity slug for the URL (e.g. \"my-project\" → /s/my-project)",
+ "type": "string"
+}Input schema / properties / ttl / descriptionPrevious value: -"Time-to-live in days (null = never expires)"New value: +"Time-to-live in days (omit = never expires)"update_sitedelete_sitedeploy_htmlget_site_infoClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose targeting specific operations in the site deployment lifecycle. Tools like deploy_html, batch_deploy, fork_site, update_site, delete_site, batch_delete, get_site_info, and get_site_analytics all address unique actions with no functional overlap, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case formatting throughout. The naming convention is perfectly uniform, using clear action verbs (deploy, delete, fork, get, update) paired with specific nouns (html, site, analytics, info), creating a predictable and readable toolset.
With 8 tools, this server is well-scoped for its site deployment and management domain. The count is ideal, covering core operations without bloat, and each tool serves a distinct, necessary function in the workflow from creation to deletion and analytics.
The toolset provides complete CRUD and lifecycle coverage for site management, including creation (deploy_html, batch_deploy), reading (get_site_info, get_site_analytics), updating (update_site), deletion (delete_site, batch_delete), and forking (fork_site). There are no obvious gaps, enabling agents to handle all typical workflows without dead ends.