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.

well-011-sharescan

REMOTE · WELL-011-SHARESCAN.MMELNYK2000.WORKERS.DEV

Pre-share scan of text for your terms and secrets/PII. x402 $0.005 USDC, Base. As is, no warranty.

67 Trust /100

Last scanned (21 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Security

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 250 tokens (~250/item across 1 items; 1 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
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.

  • 17 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Oct 26 66

    First indexed and scored.

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 18 Oct 2026 · Probed https://well-011-sharescan.mmelnyk2000.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=mmelnyk2000.workers.dev CN=WE1,O=Google Trust Services,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA256 85c0681b81111130e12f2b1ecc10533
SANs: mmelnyk2000.workers.dev, *.mmelnyk2000.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 well-011-sharescan.mmelnyk2000.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent 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://well-011-sharescan.mmelnyk2000.workers.dev/mcp Verified 200
http (plaintext) http://well-011-sharescan.mmelnyk2000.workers.dev/mcp Inconclusive 406
MCP tools · 1 exposed · ~250 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
sharescan ~250

Pre-share leak check ($0.005 USDC via x402). Scan text or an https text URL for your own terms (plain list, or salted-hash list sent per call, never stored) plus leak-shaped strings: emails, coordinates, IPs, AWS/GitHub/Slack/sk- keys, private keys, JWTs. Binary URLs are listed as unscanned. Max 10 MB, https only. Returns JSON hits with line numbers. A clean scan is not a clearance. As is, no warranty. Nothing stored.

NameTypeReqDescription
detectorsboolean–Leak-shaped string detectors (email, keys, tokens, IPs, coordinates). Default true.
hashedobject–Salted-hash list: hash = sha256_hex(salt + '\x00' + normalized_term). Sent per call, never stored.
termsarray–Plain terms to keep out (max 2000). Whole word/phrase, case- and accent-insensitive.
textstring–Text to scan (max 10 MB). Use this or url.
urlstring–https URL of a text resource. http/file/data/localhost/private IPs rejected.

No output schema declared.

No examples provided.

Install

How do I install the well-011-sharescan MCP server?

well-011-sharescan is a hosted endpoint at https://well-011-sharescan.mmelnyk2000.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 · well-011-sharescan.mmelnyk2000.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-mmelnyk2000-well-011-sharescan-share 'https://well-011-sharescan.mmelnyk2000.workers.dev/mcp'
Common questions

What is the well-011-sharescan MCP server?

well-011-sharescan is an MCP server listed in the public MCP registry as dev.workers.mmelnyk2000.well-011-sharescan/sharescan. Pre-share scan of text for your terms and secrets/PII. x402 $0.005 USDC, Base. As is, no warranty. This page covers its hosted endpoint (https://well-011-sharescan.mmelnyk2000.workers.dev/mcp).

Is the well-011-sharescan MCP server safe to use?

well-011-sharescan scores 67 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 well-011-sharescan MCP server expose?

well-011-sharescan exposes 1 tool: sharescan. Their descriptions and schemas cost roughly 250 tokens of context every time the server is loaded.

Does the well-011-sharescan MCP server require authentication?

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

Is the well-011-sharescan MCP server still maintained?

well-011-sharescan is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.