Loppee
REMOTE · LOPPEE.COM
Agent-first US business trust registry with neutral Trust Cards and published evidence.
Available components
Last scanned (11 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 661 tokens (~132/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −1
- “lookup_business” added an optional parameter “worth_it_meter” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 25 Oct 26 0
- Schema quality: pass → fail ▼ functional
- “lookup_business” added an optional parameter “verified” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Server version: 0.1.3 → 0.1.4 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://loppee.com/mcp/discovery
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=loppee.com | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 56d3bfbdc0e0813d1323c8c9290fd95b |
| SANs: loppee.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of loppee.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| loppee.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; img-src 'self' https: data:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://www.googletagmanager.com; connect-src 'self' https://loppee.com https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://*.google-analytics.com https://*.analytics.google.com; frame-src 'self' https://js.stripe.com https://hooks.stripe.com; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), camera=(), geolocation=(self), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loppee.com/mcp/discovery | Verified | 200 | |
| http (plaintext) | http://loppee.com/mcp/discovery | HTTPS enforced | 301 | https://loppee.com/mcp/discovery |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_businesses Compare Businesses ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_ids | array | yes | Two to twenty Loppee business ids to compare. Duplicates are de-duplicated. |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| data | object | – | – |
| error | object | – | – |
| ok | boolean | yes | – |
No examples provided.
explain_recommendation Explain Recommendation ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | Loppee business id of a published Trust Card. |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| data | object | – | – |
| error | object | – | – |
| ok | boolean | yes | – |
No examples provided.
get_business_reviews Get Business Reviews (paginated) ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| data | object | – | – |
| error | object | – | – |
| ok | boolean | yes | – |
No examples provided.
get_trust_card Get Trust Card ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | – | Loppee business id. |
| domain_key | string | – | Normalized domain key such as example-com. |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| data | – | – | – |
| error | object | – | – |
| ok | boolean | yes | – |
No examples provided.
lookup_business Lookup Business ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Business name to look up through the universal, pay-independent name lane. |
| verified | boolean | – | Return only Verified businesses on this bounded page. The response counts this page, not all matching businesses. |
| worth_it_meter | string | – | Only when the customer asks, for example "fair-priced plumber". Keeps rows customers rated this way, in their existing order, and drops unrated rows. It removes rows and never reorders them. |
| Name | Type | Req | Description |
|---|---|---|---|
| contract_version | string | yes | – |
| data | object | – | – |
| error | object | – | – |
| ok | boolean | yes | – |
No examples provided.
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.
remote · loppee.com
claude mcp add --transport http com-loppee-loppee 'https://loppee.com/mcp/discovery'
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 587 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Loppee MCP server?
VerifyMCP ran 13 checks on Loppee, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.