Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ShortlistLens

REMOTE · SHORTLISTLENS-MCP.STREAMING22BOX.WORKERS.DEV

Structured website and review evidence for AI-assisted local-business shortlisting.

0 this week 74 Trust /100

Last scanned (17 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 427 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.Pass
  • 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
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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 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
  • 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
  • 20 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 2026 · Probed https://shortlistlens-mcp.streaming22box.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=streaming22box.workers.dev CN=WE1,O=Google Trust Services,C=US 19 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 5f369b5840f19ff213bfdf8455a464f9
SANs: streaming22box.workers.dev, *.streaming22box.workers.dev
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 shortlistlens-mcp.streaming22box.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://shortlistlens-mcp.streaming22box.workers.dev/mcp Verified 200
http (plaintext) http://shortlistlens-mcp.streaming22box.workers.dev/mcp Inconclusive 405
MCP tools · 5 exposed · ~427 tokens

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 →

Tool Tokens
compare_shortlist_candidates ~58

Compare two to six businesses after the user has gathered website and review scores. Calculates a transparent shortlist score using 60% review trust and 40% website evaluability.

NameTypeReqDescription
candidatesarrayyesTwo to six businesses using comparable evidence.

No output schema declared.

No examples provided.

generate_paid_scope ~103

Turn a ShortlistLens result into a concise fixed-scope implementation brief for a Buyer-Readiness Scorecard or a 72-hour AI Buyer-Readiness Sprint.

NameTypeReqDescription
business_namestringyesThe business to scope.
priority_gapsarrayyesTop gaps identified by the diagnostic.
review_trust_scorenumberyesReview-trust score from supplied evidence.
website_evaluability_scorenumberyesWebsite score from the diagnostic.

No output schema declared.

No examples provided.

inspect_website ~84

Fetch a public business website page and return structured, accessible facts for a buyer-readiness review. It only examines the supplied public URL and does not scrape review platforms or private systems.

NameTypeReqDescription
target_servicestring–Optional service the buyer is researching, such as pool renovation or roof replacement.
website_urlstringyesA public HTTP or HTTPS page URL to evaluate.

No output schema declared.

No examples provided.

organize_review_evidence ~97

Organize user-supplied public review excerpts into transparent positive, risk, owner-response, and corrective-action signals. The tool does not fetch reviews itself and does not adjudicate any claim.

NameTypeReqDescription
excerptsarrayyesOne to fifty user-supplied public review excerpts.
overall_ratingnumber–Optional public overall rating supplied by the user.
review_countinteger–Optional public review count supplied by the user.

No output schema declared.

No examples provided.

score_website_evaluability ~85

Inspect a public business website and score how easily a buyer can identify the business, understand a target service, verify proof, and take the next step. Returns an explainable 0–100 rubric and priorities.

NameTypeReqDescription
target_servicestring–Optional service the buyer is researching.
website_urlstringyesA public HTTP or HTTPS page URL to evaluate.

No output schema declared.

No examples provided.

Install

How do I install the ShortlistLens MCP server?

ShortlistLens is a hosted endpoint at https://shortlistlens-mcp.streaming22box.workers.dev/mcp, 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 · shortlistlens-mcp.streaming22box.workers.dev

# add to Claude Code
claude mcp add --transport http cleandev-fix-shortlistlens 'https://shortlistlens-mcp.streaming22box.workers.dev/mcp'
Common questions

What is the ShortlistLens MCP server?

ShortlistLens is an MCP server listed in the public MCP registry as io.github.CleanDev-Fix/shortlistlens. Structured website and review evidence for AI-assisted local-business shortlisting. This page covers its hosted endpoint (https://shortlistlens-mcp.streaming22box.workers.dev/mcp).

Is the ShortlistLens MCP server safe to use?

ShortlistLens scores 74 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 ShortlistLens MCP server expose?

ShortlistLens exposes 5 tools: inspect_website, score_website_evaluability, organize_review_evidence, compare_shortlist_candidates, generate_paid_scope. Their descriptions and schemas cost roughly 427 tokens of context every time the server is loaded.

Does the ShortlistLens MCP server require authentication?

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

Is the ShortlistLens MCP server still maintained?

ShortlistLens is still listed as active in the MCP registry. We last reached this channel on 21 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 ShortlistLens MCP server?

VerifyMCP ran 11 checks on ShortlistLens, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about ShortlistLens: Authorization and HTTPS. 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.