Loppee

com.loppeePublished by loppee.comOfficial publisherv0.1.4Updated Oct 26, 2026

Agent-first US business trust registry with neutral Trust Cards and published evidence.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Read-only remote access to Loppee's US business trust registry: look up businesses, read Trust Cards and reviews, and compare them.

What you can do
  • Look up a named business and get exact or prefix matches with stable ids and coarse public city/state
  • Read a business's public Trust Card with status, disclosure, public facts and review context
  • Read paginated public customer reviews with star-rating filters and masked reviewer identity
  • Explain why a published business is or is not recommendable, with its published basis and citation
  • Compare two to twenty known business ids side by side, listing unresolved ids rather than inventing them
When to use it
Useful when an assistant needs neutral, cited background on a US business before recommending or discussing it, or when a user asks whether a named business is verified, listed or trustworthy on Loppee. It is a narrow research surface, not a directory search by category or location.
Requirements
A remote Streamable HTTP endpoint; no authentication, API key, header or environment variable is required. The client must support remote HTTP MCP servers.
Before you install
All five tools are declared read-only and non-destructive, and the schemas accept no address or location input. Results are limited to businesses already published in the Loppee registry, and missing records stay unresolved. Authenticated consumer, business-owner and back-office products are separate and not exposed here.

Installation

In SourceWeft

  1. Open Loppee in the dashboard and add it to a workspace.
  2. 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.loppee%2Floppee/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.

{
  "mcpServers": {
    "loppee": {
      "type": "http",
      "url": "https://loppee.com/mcp/discovery"
    }
  }
}

README

Loppee MCP

Public metadata for Loppee's narrow, no-auth MCP discovery surface.

Connect

Configure the URL above as a remote HTTP MCP server in a compatible client. This repository does not contain credentials and does not require an API key.

Claude custom connector

Add Loppee to Claude prefills Claude's custom-connector dialog. Claude still asks the signed-in user to review and confirm the name and URL; the link does not publish a directory listing or grant permissions.

The canary and directory-review packet is in distribution/claude-connectors-directory.md.

Cursor

Copy the following official Cursor MCP install link into a browser with Cursor installed. Cursor shows the decoded remote-server configuration and asks the user to confirm before installation:

text
cursor://anysphere.cursor-deeplink/mcp/install?name=loppee&config=eyJ1cmwiOiJodHRwczovL2xvcHBlZS5jb20vbWNwL2Rpc2NvdmVyeSJ9

The decoded configuration is exactly:

json
{  "url": "https://loppee.com/mcp/discovery"}

For manual or project setup, use mcp.json. The candidate Cursor Marketplace manifest is .cursor-plugin/plugin.json. Neither file contains an account, header, credential, key, or local command. The Marketplace preflight is in distribution/cursor-marketplace.md.

OpenClaw

The metadata-only Agent Plugins Bundle source is in clawhub/loppee-discovery. It contains no skill, runtime code, credential, header, key, customer data, owner tool, write tool, or location input.

The current ClawHub CLI incorrectly requires a native openclaw.plugin.json from compatible bundles. Loppee will preserve the narrower Agent Plugins Bundle instead of changing it into a native plugin or publishing it as a Skill. The live admission blocker and reproduction are tracked in openclaw/clawhub#3513. See distribution/openclaw-clawhub.md for the verified package boundary and publication gate.

Public tool boundary

The endpoint exposes exactly five read-only named-business research tools:

ToolPurpose
lookup_businessFind pay-independent exact or genuine-prefix matches for a named business.
get_trust_cardRead the published Trust Card for an identified Loppee business.
get_business_reviewsRead paginated public reviews and their published disclosures.
explain_recommendationRead the published recommendation basis for an identified business.
compare_businessesCompare two to twenty identified published Loppee businesses.

Every tool is declared read-only, non-destructive, and closed-world. This surface exposes no category discovery, address or location input, pricing, checkout, customer account, business-owner, write, or Back Office authority.

Privacy and neutrality

  • The tool schemas accept no address, city, state, ZIP, coordinates, location handoff, or device-location input.
  • The endpoint returns no private customer or owner data.
  • Payment does not change lookup, comparison, verification, reviews, evidence, or recommendation explanation on this surface.
  • Missing or unresolved records must remain unresolved rather than fabricated.

Loppee Personal, authenticated consumer MCP, Loppee Business, and Back Office are separate products with different authorization boundaries. They are not published through this repository.

Registry metadata

server.json records published version 0.1.4 of the existing com.loppee/loppee Official MCP Registry listing (published 2026-09-26T13:41:56.310498Z, the latest version). It changed metadata only: the source repository (https://github.com/loppee-ai/loppee-mcp, after the GitHub owner rename from 4dwebspro-cell to loppee-ai) and agent_docs_url. The /mcp/discovery remote, tools and policies are unchanged from 0.1.3 (published 2026-08-24T18:33:32.121626Z), which the Registry still reports as active. Versions 0.1.0 through 0.1.2 are retained as deprecated history. Registry versions are immutable after publication.

Design note: repository links this public metadata repository

Starting with 0.1.4, the manifest's repository field intentionally points to this public repository (https://github.com/loppee-ai/loppee-mcp, stable GitHub repository id 1345142388). Versions 0.1.0–0.1.3 omitted the field because the Registry schema describes repository as the server's source code, and Loppee's production source repository is private. We now link this repository deliberately: it is the canonical, public, inspectable home of the listing's metadata, connection documentation and security contact, and the stable repository id lets clients detect a deleted-and-recreated repository. It does not contain, and does not claim to contain, the server implementation.

Official MCP Registry publication and GitHub MCP Registry curation are separate gates. Loppee's GitHub Registry onboarding request was submitted on 2026-08-28; submission is not inclusion. See distribution/github-mcp-registry-onboarding.md for the public request and the remaining verification gate.

Verification

Before any future Registry release or downstream directory submission, Loppee validates server.json with the official mcp-publisher; checks the live MCP initialize capabilities, tools/list, resources/list, and prompts/list; verifies the exact five-tool catalog and annotations with no resource or prompt capability; and exercises the read-only tools. Those release checks run from Loppee's private product repository and CI; no backend source, credentials, workflows, or operational runbooks are published here.

The 0.1.3 production canary completed at 2026-08-24T18:36:20Z on build e09c360f1d29269a72a1d9e272b1ead29c101c0e: exactly five tools were listed, resources, resource templates, and prompts were unsupported, all five tool calls succeeded, the public-output privacy scan and text/structured-content parity checks passed, and anonymous access to the separate /mcp surface returned 401.

Links

Source and license

This public repository intentionally contains metadata and documentation only. It does not contain the Loppee backend, private application source, scripts, workflows, secrets, credentials, or customer data.

No LICENSE file is included. Public visibility does not grant an open-source license.

Source: README.md at commit dd714af

Tools

5

lookup_business

Lookup Business

Use this when the user names a business and wants its Loppee Registry match. Returns exact and genuine-prefix name matches with stable ids, coarse public city/state, and truthful Verified, Listed, or Registry disclosure. It does not perform category discovery, accept or return caller location, or return a street address or ZIP.

Parametersnamerequiredlimitcursor

get_trust_card

Get Trust Card

Use this when a business is already identified and the user wants its public Loppee Trust Card. Returns the exact business status, disclosure, coarse public city/state, public facts, review context, and citation without account authority, street address, ZIP, or signed media links.

Parametersdomain_keybusiness_id

get_business_reviews

Get Business Reviews (paginated)

Use this when the user wants the public customer reviews for one Loppee business id. Supports pagination and star-rating filters, preserves reviewer and interaction labels, masks reviewer identity, and changes nothing.

Parameterspagelimitratingsbusiness_idrequired

explain_recommendation

Explain Recommendation

Use this when the user asks why a known published business is or is not recommendable on Loppee. Returns the published class, disclosure, recommendation basis, commercial-neutrality statement, and citation without exposing private weighting.

Parametersbusiness_idrequired

compare_businesses

Compare Businesses

Use this when the user wants a side-by-side comparison of two to twenty known published Loppee business ids. Returns each business's exact class, disclosure, review context, and citation; unknown or unavailable ids are listed as unresolved rather than fabricated.

Parametersbusiness_idsrequired

Version history

2
  1. v0.1.4LatestSep 26, 2026
  2. v0.1.3Sep 16, 2026

Score

90% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.