cautellus
Registry code: 820045dcdf2d64ea
Cautellus scam detection for AI agents. scan_url and scan_message return a safe/warn/danger verdict with a 0-100 risk score — gate risky actions on it (danger: do not proceed; warn: confirm with a human). Each scan consumes one prepaid credit from the API key in the Authorization header. Keys and credit packs: https://cautellus.com/developers. get_usage is free and reports the remaining balance.
- endpoint
- https://cautellus.com/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 cautellus live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is cautellus free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does cautellus have?
- 3 tools: scan_url, scan_message, get_usage.
- Is cautellus 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.
90 days 99.3%· all time 99.3%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- check a url for phishing risk
- scan a message for scam indicators
- check remaining scan credits
- takes → gives
- text, web pages → data
- tools
- 3 reads
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.
through this hub
successful
what callers paid
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_usage reads auth-required 18h ago
Check the API key’s remaining prepaid scan credits, monthly plan usage, and credit expiry. Free — consumes no credits.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesscan_url reads unknown never probed
Check a URL or domain for phishing and scam risk before visiting, clicking, or transacting with it. Returns a verdict (safe | warn | danger), a 0-100 risk score, a plain-English summary, and specific findings (brand impersonation, typosquatting, community scam reports, threat-feed hits). Costs 1 scan credit.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The URL or bare domain to analyze, e.g. \"paypal-verify-login.xyz\"" } }, "additionalProperties": false }arguments 13 linesscan_message reads unknown never probed
Analyze a message, email, or text for scam indicators before acting on it (payment requests, verification codes, urgency pressure, impersonation). Returns a verdict (safe | warn | danger), a 0-100 risk score, a summary, and specific findings. Costs 1 scan credit.
{ "type": "object", "required": [ "message" ], "properties": { "message": { "type": "string", "description": "The full message text to analyze (up to 25,000 characters)" } }, "additionalProperties": false }arguments 13 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id820045dcdf2d64ea.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/820045dcdf2d64ea/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/820045dcdf2d64ea?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.