_ registry / mcp http-sse · checked 1h ago

well-011-sharescan

https://well-011-sharescan.mmelnyk2000.workers.dev

Registry code: 7fc2c620e9bd6997

api record

Pre-share scan: check text or a https URL against caller terms (plain or salted-hash) plus secret/PII detectors. x402 pay-per-call, $0.005 USDC on Base. MCP tool sharescan. Stateless; nothing stored.

from a public catalogue that lists it, not from the operator

endpoint
https://well-011-sharescan.mmelnyk2000.workers.dev/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is well-011-sharescan live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is well-011-sharescan free to use?
No — it charges per call, from 0.005 USDC, quoted in its own 402 answers.
What tools does well-011-sharescan have?
1 tool: sharescan.
Is well-011-sharescan safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
947ms

last good check

priced tools
1

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 1 tools
1 paid 1 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • sharescan 0.005 USDC paid 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "url": {
          "type": "string",
          "description": "https URL of a text resource. http/file/data/localhost/private IPs rejected."
        },
        "text": {
          "type": "string",
          "description": "Text to scan (max 10 MB). Use this or url."
        },
        "terms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Plain terms to keep out (max 2000). Whole word/phrase, case- and accent-insensitive."
        },
        "hashed": {
          "type": "object",
          "required": [
            "salt",
            "hashes"
          ],
          "properties": {
            "salt": {
              "type": "string"
            },
            "format": {
              "type": "string"
            },
            "hashes": {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            "max_words": {
              "type": "integer",
              "maximum": 9007199254740991,
              "minimum": -9007199254740991
            }
          },
          "description": "Salted-hash list: hash = sha256_hex(salt + '\\x00' + normalized_term). Sent per call, never stored."
        },
        "detectors": {
          "type": "boolean",
          "description": "Leak-shaped string detectors (email, keys, tokens, IPs, coordinates). Default true."
        }
      }
    }
    arguments 52 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7fc2c620e9bd6997.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7fc2c620e9bd6997/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7fc2c620e9bd6997/badge.svg)](https://brick.blue/agent/7fc2c620e9bd6997?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.