soofi-website-grader
https://grader.soofidigital.com
Registry code: ebd3e481d1a81559
Use audit_website when the user wants a website audited, graded or reviewed for SEO, speed, trust or lead capture; share the score, the most important problems with their fixes, and the full report link. Use request_help only if the user asks for someone to fix the site for them and gives their contact details for that purpose.
- endpoint
- https://grader.soofidigital.com/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 soofi-website-grader live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is soofi-website-grader free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does soofi-website-grader have?
- 2 tools: request_help, audit_website.
- Is soofi-website-grader 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 100%· all time 100%
last good check
of 2 tools
- unknown → live
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
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
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.
request_help unknown never probed
Sends the user's request for help fixing their website to Soofi Digital's team, who will contact them by email or WhatsApp. Only use when the user explicitly asks for help or for Soofi Digital to contact them, and only with contact details the user has given you for this purpose. Confirm the details with the user before sending.
{ "type": "object", "required": [ "name", "email", "website" ], "properties": { "name": { "type": "string", "description": "The user's name" }, "email": { "type": "string", "description": "The user's email address" }, "phone": { "type": "string", "description": "Optional WhatsApp/phone number with country code, e.g. +1 555 123 4567" }, "message": { "type": "string", "description": "Optional: what they want help with, in their words" }, "website": { "type": "string", "description": "The website they want help with" }, "business": { "type": "string", "description": "Optional business name" } }, "additionalProperties": false }arguments 35 linesaudit_website unknown 1h ago
Grades a public website out of 100 (A–F) across speed & mobile (including Google's live PageSpeed mobile test), Google visibility (SEO), trust & security, and lead capture. Returns every problem ranked by impact with a plain-English fix, what already works, and a link to a shareable full report. Use when the user asks to audit, grade, check, review or analyse a website, its SEO, speed or conversion. Takes 10–40 seconds.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The website address, e.g. example.com or https://example.com/page" } }, "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 idebd3e481d1a81559.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ebd3e481d1a81559/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ebd3e481d1a81559?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.