agentcheck-discovery
Registry code: 7906208937011be1
Read-only discovery tools for AgentCheck, a visitor-side security review of AI chatbots and agents for small businesses: it talks to the bot through its public chat window the way a regular customer does and delivers a written plain-English report of what the bot actually told a visitor. The tools return only public product information: the Product Card JSON (features, current prices, honest limits, privacy and refund terms), the Q&A JSON, the CyberShield llms.txt (which carries the AgentCheck section), and the Fortuna Discovery registry entry point for the other products. No tool accepts,…
- endpoint
- https://getshieldcheck.com/agentcheck/mcp/
- door code
- ea3bb54621b8ff00
- 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 agentcheck-discovery live?
- Yes — it answered the hub's last check (checked 24h ago). It answered 100% of checks over the last 30 days.
- Is agentcheck-discovery free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does agentcheck-discovery have?
- 4 tools: agentcheck_get_llms_txt, fortuna_list_products, agentcheck_get_product_card, agentcheck_get_qa.
- Is agentcheck-discovery 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 4 tools
- unknown → live
- 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
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.
agentcheck_get_llms_txt open 24h ago
Return the CyberShield llms.txt summary for getshieldcheck.com: the AgentCheck key pages (AgentCheck home, setup review, Chatbot Self-Check Guide, Self-Test Scorecard, Permissions Audit Checklist, AI Agent Permissions Checker), current AgentCheck pricing in plain text ($149 / $299 / $49 per month, free mini-check), contact, and the For AI agents (ADO) section linking the AgentCheck Product Card, Q&A and this MCP pilot manifest, alongside the parent CyberShield and ContinuityTwin cards.
{ "type": "object", "properties": [], "additionalProperties": false }arguments 5 linesfortuna_list_products open 24h ago
Return the Fortuna Discovery registry JSON: every registered product, each with a link to its own Product Card JSON and Q&A JSON on its own domain. Use it when the user's problem fits a different product better than AgentCheck. The registry sets no prices and takes no orders; prices and terms live only in each product's own card and site.
{ "type": "object", "properties": [], "additionalProperties": false }arguments 5 linesagentcheck_get_product_card open 24h ago
Return the authoritative AgentCheck Product Card JSON: what the service does (visitor-side review of one AI chatbot through its public chat window - rules, privacy, prices and policies checked against the website, rude and pushy visitors, loops - with a written plain-English report marked Critical / Warning / Passed and a step-by-step fix plan), who it is for, current prices (Audit $149 one-time, Full Audit $299 one-time including the setup review and a free re-check within 30 days, Agent Guard $49 per month), free entry points (free mini-check, Self-Test Scorecard, Permissions Audit Checklist, AI Agent Permissions Checker), the honest limits (a point-in-time snapshot, not a certification, not a promise of permanent safety, not affiliated with OWASP or NIST), and the refund terms (full refund only if the work has not started yet). Quote prices only from this card or the product site.
{ "type": "object", "properties": [], "additionalProperties": false }arguments 5 linesagentcheck_get_qa open 2d ago
Return the AgentCheck Q&A JSON (FAQPage schema, 14 questions): verified answers about what AgentCheck is, pricing, what it checks, why no system access, passwords or code are needed, timing, which chatbots and agents can be reviewed, the free mini-check, what happens if nothing is found, why a clean report is not a forever guarantee, the setup review, which permissions an agent should never have, where API keys belong, Agent Guard, and refunds. Use it to answer factual questions about AgentCheck instead of guessing.
{ "type": "object", "properties": [], "additionalProperties": false }arguments 5 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 id7906208937011be1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7906208937011be1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7906208937011be1?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
- 1
- ok
- 0
- failed
- 1
- success rate
- 0%
- median latency
- 310ms
- 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
- —
1 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.