Home / MCP registry index / now.shiply/shiply

Shiply

now.shiply/shiply in the official MCP registry. Endpoint https://shiply.now/mcp.

The registry describes it as: Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.

Connect it

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

claude mcp add --transport http shiply https://shiply.now/mcp

{
  "mcpServers": {
    "shiply": {
      "url": "https://shiply.now/mcp"
    }
  }
}

code --add-mcp '{"name":"shiply","type":"http","url":"https://shiply.now/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.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

publish_site site_status verify_site list_sites get_site delete_site rollback_site list_versions pull_site set_handle duplicate_site promote_site set_link set_site_access get_site_access export_account whoami get_account_status list_drives create_drive drive_list_files drive_put_file drive_delete_file publish_from_drive set_profile feature_site set_variable list_variables delete_variable attach_variable detach_variable list_site_variables list_databases create_database delete_database attach_database data_list_collections data_query data_insert data_export_collection add_domain add_custom_domain add_subdomain set_primary_subdomain list_custom_domains connect_provider sync_dns check_custom_domain remove_custom_domain list_domains check_domain remove_domain get_analytics create_test list_tests get_test_status send_broadcast resend_confirmation verify_claim list_inbox and 54 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 711426e7af9c50c1. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

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

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.

Related

Database MCP servers · Email MCP servers