# Loppee (remote · loppee.com)

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

- Trust score: 88/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `loppee.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/com-loppee-loppee/mcp-discovery.md), [page](https://verifymcp.io/servers/com-loppee-loppee/mcp-discovery)

## Channel facts

- Endpoint: `https://loppee.com/mcp/discovery`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 587 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Loppee MCP server?

Loppee is a hosted endpoint at https://loppee.com/mcp/discovery, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-loppee-loppee 'https://loppee.com/mcp/discovery'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-loppee-loppee": {
      "type": "http",
      "url": "https://loppee.com/mcp/discovery"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-loppee-loppee]
url = "https://loppee.com/mcp/discovery"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-loppee-loppee": {
      "type": "remote",
      "url": "https://loppee.com/mcp/discovery",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-loppee-loppee --url 'https://loppee.com/mcp/discovery' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-loppee-loppee:
    url: "https://loppee.com/mcp/discovery"
```

### Netclaw

```json
{
  "McpServers": {
    "com-loppee-loppee": {
      "Transport": "http",
      "Url": "https://loppee.com/mcp/discovery"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-loppee-loppee -t streamable-http -u 'https://loppee.com/mcp/discovery'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `lookup_business` (~135 tokens)

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.

Input parameters:

- `cursor` (string): Opaque cursor returned in next_cursor by the previous v3 search page. Omit for the first page.
- `limit` (integer): Maximum result count from 1 to 50.
- `name` (string, required): Business name to look up through the universal, pay-independent name lane.

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error` (object)
- `ok` (boolean)

### `get_trust_card` (~92 tokens)

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.

Input parameters:

- `business_id` (string): Loppee business id.
- `domain_key` (string): Normalized domain key such as example-com.

Output parameters:

- `contract_version` (string)
- `data`
- `error` (object)
- `ok` (boolean)

### `get_business_reviews` (~132 tokens)

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.

Input parameters:

- `business_id` (string, required): Loppee business id of a published business.
- `limit` (integer): Reviews per page (default 5, max 50).
- `page` (integer): 1-based page number (default 1).
- `ratings` (array): Star-rating filter: return only reviews with these ratings, e.g. [1] or [4,5]. Omit for all ratings.

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error` (object)
- `ok` (boolean)

### `explain_recommendation` (~70 tokens)

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.

Input parameters:

- `business_id` (string, required): Loppee business id of a published Trust Card.

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error` (object)
- `ok` (boolean)

### `compare_businesses` (~84 tokens)

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.

Input parameters:

- `business_ids` (array, required): Two to twenty Loppee business ids to compare. Duplicates are de-duplicated.

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error` (object)
- `ok` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-loppee-loppee/mcp-discovery#diagnostics

## Score history

- 2026-09-21: 88
- 2026-09-20: 87
- 2026-09-19: 87
- 2026-09-18: 86
- 2026-09-17: 86
- 2026-09-16: 86
- 2026-09-15: 85
- 2026-09-14: 85
- 2026-09-13: 84
- 2026-09-12: 84
- 2026-09-11: 83
- 2026-09-10: 83
- 2026-09-09: 82
- 2026-09-08: 82
- 2026-09-07: 81
- 2026-09-06: 81
- 2026-09-05: 80
- 2026-09-04: 80
- 2026-09-03: 79
- 2026-09-02: 79
- 2026-09-01: 79
- 2026-08-31: 78
- 2026-08-30: 78
- 2026-08-29: 77
- 2026-08-28: 77
- 2026-08-27: 76
- 2026-08-26: 76
- 2026-08-25: 74
- 2026-08-24: 73

## Common questions

### What is the Loppee MCP server?

Loppee is an MCP server listed in the public MCP registry as com.loppee/loppee. Agent-first US business trust registry with neutral Trust Cards and published evidence. This page covers its hosted endpoint (https://loppee.com/mcp/discovery).

### Is the Loppee MCP server safe to use?

Loppee scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Loppee MCP server expose?

Loppee exposes 5 tools: lookup_business, get_trust_card, get_business_reviews, explain_recommendation, compare_businesses. Their descriptions and schemas cost roughly 513 tokens of context every time the server is loaded.

### Does the Loppee MCP server require authentication?

No. We connected to Loppee without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Loppee MCP server still maintained?

Loppee is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://loppee.com/mcp/discovery
- Website: https://loppee.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-loppee-loppee/mcp-discovery.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-loppee-loppee/mcp-discovery.json
- HTML version of this page: https://verifymcp.io/servers/com-loppee-loppee/mcp-discovery