mcp-registry/now.shiply/shiply · v0.1.0
As of 2026-10-18 05:23 UTC, the Shiply MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.
Claude Code
claude mcp add --transport http shiply-mcp-server https://shiply.now/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"shiply-mcp-server": {
"type": "http",
"url": "https://shiply.now/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
114 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 →
32 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 →
2 parameter(s) across 1 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 →
Loading this server's tool list costs an agent ~18,456 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~3,850 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.
54 of 114 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fnow.shiply%2Fshiply/fixes
{
"name": "add_custom_domain",
"description": "Register a registrable domain (e.g. example.com) the user owns and detect its DNS provider. Returns the provider and whether one-click connect is available. Then attach sites with add_subdomain.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "registrable domain you own, e.g. example.com"
}
}
},
"annotations": {
"openWorldHint": true,
"idempotentHint": false,
"readOnlyHint": false,
"destructiveHint": false
},
"title": "Register a custom domain"
}{
"name": "add_domain",
"description": "Serve a site on a domain the user owns. Returns the CNAME to add (hostname → cname.shiply.now); the certificate issues automatically once DNS resolves. Poll with check_domain.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hostname",
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "owned site slug to serve there"
},
"hostname": {
"type": "string",
"description": "full hostname to serve, e.g. www.example.com"
}
}
},
"annotations": {
"openWorldHint": true,
"idempotentHint": false,
"readOnlyHint": false,
"destructiveHint": false
},
"title": "Connect a custom domain"
}{
"name": "add_sending_domain",
"description": "Register a domain the user owns for outbound demand-test sends. Returns DNS records (SPF, DKIM, MX) to add at the DNS provider. After DNS propagates, call verify_sending_domain. Cannot be a shiply.now subdomain.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "e.g. mail.yourbrand.com"
}
}
},
"annotations": {
"openWorldHint": true,
"idempotentHint": false,
"readOnlyHint": false,
"destructiveHint": false
},
"title": "Add a sending domain"
}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/now.shiply/shiply"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/now.shiply/shiply"}) over MCP.
publish_site ~664 tokensset_mailbox ~425 tokenscreate_listing ~362 tokensforward_thread ~360 tokenscreate_project ~347 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fnow.shiply%2Fshiply?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fnow.shiply%2Fshiply?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fnow.shiply%2Fshiply.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fnow.shiply%2Fshiply.svg :target: https://glimind.com/server/mcp-registry%2Fnow.shiply%2Fshiply?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a68914955ec59e38…, first seen 2026-10-17, included at leaf 14212 of 20,469. Version history · verify what your client received.
Compare: most reliable other servers · most reliable web servers · most reliable communication servers · most reliable email servers · most reliable productivity servers
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.
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"
}
}
}
As of 2026-10-18 05:23 UTC, the Shiply MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 3 minutes.
Shiply MCP server advertises 114 tools, including add_custom_domain, add_domain, add_sending_domain, add_subdomain, add_suppression.
Point your MCP client at this streamable-http endpoint: https://shiply.now/mcp
Glimind scanned all 114 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.
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.