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

assurly

https://assurly.dev

Registry code: 9b662e08763d63b8

api record

MCP server that gives Cursor, Claude Code, VS Code and Windsurf a pre-deploy ship gate. Five tools: scan a path or files, explain a rule, read a hosted verdict, and audit the agent stack itself (MCP config and instruction files).

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

endpoint
https://assurly.dev/api/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 assurly live?
Yes — it answered the hub's last check (checked 27m ago). It answered 99% of checks over the last 30 days.
Is assurly free to use?
Yes — the hub reached it with no key and no payment.
What tools does assurly have?
1 tool: check_live_app.
Is assurly 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.6%

90 days 99.3%· all time 99.3%

latency
1,562ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 280 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
security & compliance threat & vulnerability
used for
  • scan a live web app for security issues
  • find leaked secrets on a deployed app
takes → gives
web pages → data
tools
1 reads
_ 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 1 tools
1 never probed 0 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.

  • check_live_app reads unknown 9h ago

    Security scan of a live, deployed web app, seen from the outside the way a stranger on the internet sees it. Finds leaked secret keys in the page or its JavaScript (Stripe, AWS, Google and Supabase service-role keys), a Supabase database reachable with the public key, missing security headers (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options) and deployments that are down. Returns a ship verdict (ready, review or blocked), a Ship Score from 0 to 100, and for each problem what it means and how to fix it. Use when the user asks whether a live app or website is secure or safe to launch, wants it checked for security issues or leaked API keys before going live, or wants to confirm a fix after redeploying. Works for any public URL, including apps built with Lovable, Bolt, v0, Replit or Cursor. Passive: it loads the public page and scripts like a browser; it never logs in, submits data or reads the database.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "Public URL of the deployed app, e.g. https://my-app.lovable.app"
    }
  },
  "additionalProperties": false
}
    arguments 16 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 9b662e08763d63b8.

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