MCP QUEEN
com.loppee/loppee A
Agent-first US business trust registry with neutral Trust Cards and local search.
Web & Searchv0.1.1streamable-httploppee.com repository
Grade evidence — probed 2026-07-13 03:30 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 217ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo loppee-agent-api@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 43 tools e.g. "get_agent_capabilities"; 43/43 described, 43/43 fully-typed schemas, median description 717 chars |
| latency | 10 / 10 | initialize round-trip 217ms |
| provenance | 15 / 15 | description present; repository linked; version 0.1.1; namespace com.loppee matches endpoint/repo |
Score 100/100 · latency 217ms · 43 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http loppee https://loppee.com/mcp
Generic MCP client config:
{ "mcpServers": { "loppee": { "type": "http", "url": "https://loppee.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.loppee/loppee · referral link https://mcpqueen.com/go/com.loppee/loppee (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.loppee/loppee)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 03:30 | A | 100 | 217ms |