Laurel

com.checklaurelPublished by checklaurel.comOfficial publisherv1.0.0Updated Oct 24, 2026

Find products vetted for low-tox materials, from Laurel's curated catalog.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search Laurel's curated catalog for products vetted for low-tox materials.

What you can do
The server exposes Laurel's curated product catalog to an assistant, so it can look up items that have been vetted for low-tox materials. The manifest lists no individual tools, and the description covers only finding such products.
When to use it
Use it when a user wants product suggestions or catalog lookups focused on low-tox materials and prefers results from Laurel's vetted selection rather than general web search. It is a narrow catalog search aid, not a general shopping or price-comparison tool.
Requirements
A remote streamable HTTP endpoint at checklaurel.com, reachable over the network. OAuth authentication is required; no environment variables or headers are declared. A Laurel account is presumably needed to complete the OAuth flow.
Before you install
Access requires OAuth authorization, so the assistant acts under a Laurel account and the provider can see the queries made through it. The description does not state whether the server can change account data, place orders, or share queries with third parties; confirm this before connecting.

Installation

In SourceWeft

  1. Open Laurel 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.checklaurel%2Flaurel/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": {
    "laurel": {
      "type": "http",
      "url": "https://checklaurel.com/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 15, 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.