Vigil

com.appnaryPublished by appnary.comOfficial publisherv0.1.0Updated Oct 26, 2026

Shopify store security: find risky scripts and apps, and turn them off from your AI agent.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for Shopify store security: it lets an AI assistant find risky scripts and apps in a store and turn them off.

What you can do
  • Inspect a Shopify store's installed scripts and apps and identify ones flagged as risky.
  • Disable risky scripts or apps directly from the assistant.
  • No tool list is published, so the exact set of actions is not documented; the description centers on finding and turning off risky scripts and apps.
When to use it
Useful when you run a Shopify store and want an assistant to audit which scripts and apps are installed and to switch off ones that look risky, without opening the admin manually.
Requirements
A remote endpoint at cp.appnary.com over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared. A Shopify store connected to the service is implied by the description but not documented.
Before you install
The server can turn off scripts and apps, which changes a live storefront and may break store functionality; confirm before letting an assistant disable anything. It requires OAuth access to your store data, and the scope of that access is not documented here.

Installation

In SourceWeft

  1. Open Vigil in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.appnary%2Fvigil/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "vigil": {
      "type": "http",
      "url": "https://cp.appnary.com/api/vigil/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 19, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.