_ registry / mcp streamable-http · checked 24m ago

shieldz

https://shieldz.cash

Registry code: 753164fef8c4eb73

api record

Keyless, non-custodial crypto payments. create_payment_link, create_tip_jar and create_unlock need only a wallet address; no API key. Use create_unlock to sell a file, license key, or secret (auto-revealed after payment); use create_tip_jar only for pay-what-you-want tips.

endpoint
https://shieldz.cash/mcp
protocol
streamable-http ·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 shieldz live?
Yes — it answered the hub's last check (checked 24m ago). It answered 99% of checks over the last 30 days.
Is shieldz free to use?
Yes — the hub reached it with no key and no payment.
What tools does shieldz have?
4 tools: get_account_status, create_unlock, create_payment_link, create_tip_jar.
Is shieldz 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
98.7%

90 days 99.1%· all time 99.1%

latency
210ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 352 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • create a crypto payment link
  • create a pay-what-you-want tip jar
  • sell a file or secret behind a payment
  • check a payment account's status
takes → gives
text, data → data
tools
1 reads3 changes data
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • get_account_status reads unknown 24m ago

    Look up a keyless Shieldz account by its manage_token (returned when you create a payment link or tip jar). Returns settlement details, tip jars, totals (paid/pending), and the invoice list as structured JSON.

    mcp-tool

    {
      "type": "object",
      "required": [
        "manage_token"
      ],
      "properties": {
        "manage_token": {
          "type": "string",
          "description": "The manage_token from create_payment_link / create_tip_jar"
        }
      }
    }
    arguments 12 lines
  • create_unlock changes data unknown never probed

    Create a keyless pay-to-unlock page: sell a file link, license key, or secret text (up to 100,000 chars). The buyer pays the set USD price in crypto straight to the given wallet, then the payload is revealed on their paid confirmation, never before. To deliver an actual file (PDF/zip/etc, 10 MB) use the multipart HTTP API at /api/v1/unlocks instead. Non-custodial, no account, no API key. IMPORTANT: the acceptable-use policy forbids adult, illegal, or non-consensual content; confirm this with your principal and pass aup_accepted=true, otherwise the call fails.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address",
        "price_usd",
        "payload",
        "aup_accepted"
      ],
      "properties": {
        "asset": {
          "enum": [
            "USDC",
            "USDT"
          ],
          "type": "string",
          "description": "Stablecoin (default USDC)"
        },
        "chain": {
          "enum": [
            "base",
            "arbitrum",
            "optimism",
            "polygon",
            "ethereum"
          ],
          "type": "string",
          "description": "Settlement chain (default base)"
        },
        "email": {
          "type": "string",
          "description": "Optional, lets the owner claim a dashboard later"
        },
        "title": {
          "type": "string",
          "description": "What the buyer is purchasing, shown on the paywall"
        },
        "address": {
          "type": "string",
          "description": "Destination wallet (0x EVM address); funds settle here."
        },
        "payload": {
          "type": "string",
          "description": "The secret to reveal after payment: a URL or text, max 100000 chars. Never shown before payment."
        },
        "price_usd": {
          "type": "number",
          "description": "Unlock price in USD, $1 to $100,000, e.g. 5 for $5.00"
        },
        "description": {
          "type": "string",
          "description": "Short pitch shown on the paywall"
        },
        "aup_accepted": {
          "type": "boolean",
          "description": "Must be true: asserts the content complies with the acceptable-use policy (no adult, illegal, or non-consensual content)."
        }
      }
    }
    arguments 58 lines
  • create_payment_link changes data unknown never probed

    Create a one-time crypto payment link with ZERO setup, no account, no API key. Give a destination wallet address and an amount; get back a shareable pay_url, an embeddable button, and a manage_url. Non-custodial: funds settle directly to the address you provide.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address",
        "amount_usd"
      ],
      "properties": {
        "memo": {
          "type": "string",
          "description": "Description shown on the checkout"
        },
        "asset": {
          "enum": [
            "USDC",
            "USDT"
          ],
          "type": "string",
          "description": "Stablecoin (default USDC)"
        },
        "chain": {
          "enum": [
            "base",
            "arbitrum",
            "optimism",
            "polygon",
            "ethereum"
          ],
          "type": "string",
          "description": "Settlement chain (default base)"
        },
        "email": {
          "type": "string",
          "description": "Optional, lets the owner claim a dashboard later"
        },
        "address": {
          "type": "string",
          "description": "Destination wallet (0x EVM address); funds settle here."
        },
        "amount_usd": {
          "type": "number",
          "description": "Amount in USD, e.g. 49 for $49.00"
        }
      }
    }
    arguments 44 lines
  • create_tip_jar changes data unknown never probed

    Create a reusable 'pay what you want' tip jar with ZERO setup. The payer chooses the amount. Returns a shareable /tip url, an embeddable button, and a manage_url. Idempotent per wallet address. Non-custodial.

    mcp-tool

    {
      "type": "object",
      "required": [
        "address"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Optional custom URL slug"
        },
        "asset": {
          "enum": [
            "USDC",
            "USDT"
          ],
          "type": "string",
          "description": "Stablecoin (default USDC)"
        },
        "chain": {
          "enum": [
            "base",
            "arbitrum",
            "optimism",
            "polygon",
            "ethereum"
          ],
          "type": "string",
          "description": "Settlement chain (default base)"
        },
        "email": {
          "type": "string",
          "description": "Optional, lets the owner claim a dashboard later"
        },
        "title": {
          "type": "string",
          "description": "Heading shown on the tip page, e.g. 'Buy me a coffee'"
        },
        "address": {
          "type": "string",
          "description": "Destination wallet (0x EVM address); funds settle here."
        },
        "description": {
          "type": "string"
        },
        "suggested_amounts_usd": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "description": "Preset amount buttons in USD, e.g. [3, 5, 10]"
        }
      }
    }
    arguments 53 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 753164fef8c4eb73.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/753164fef8c4eb73/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/753164fef8c4eb73/badge.svg)](https://brick.blue/agent/753164fef8c4eb73?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
80%

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.