Ecomhint

com.ecomhintPublished by ecomhint.comOfficial publisherv1.0.0Updated Oct 27, 2026

Ecommerce store audits: read findings with evidence and fix steps, track tasks, run new audits.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Ecomhint ecommerce store audits: read findings with evidence and fix steps, track tasks, and run new audits.

What you can do
  • Read audit findings, including the evidence behind each one and suggested fix steps
  • Track audit tasks and their status
  • Run new audits for an ecommerce store
  • Access is through a hosted endpoint rather than a local package
When to use it
Useful when you work on an ecommerce store and want an assistant to pull up existing audit findings, explain what to fix, follow up on remediation tasks, or kick off a fresh audit without leaving the chat.
Requirements
A remote MCP endpoint at ecomhint.com over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared, and no local package is needed.
Before you install
OAuth grants the server access to your Ecomhint account, so review the scopes requested at sign-in. Running new audits and updating tasks change data in your account. Audit results and store details are handled by a third-party service.

Installation

In SourceWeft

  1. Open Ecomhint 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.ecomhint%2Fstore-audit/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": {
    "ecomhint": {
      "type": "http",
      "url": "https://ecomhint.com/api/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. v1.0.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.