collectsea
Registry code: 8855f33c1c047d49
CollectSEA finds documented real-world software, security and AI-agent failures that resemble a proposed design or existing app. For existing apps, inspect the available repository, summarize observed behavior and call analyze_existing_app with relevant text files. Do not infer deployed permissions or safeguards from missing evidence. Call analyze_design before implementing features that move money, delete or migrate data, change permissions, run generated code, push configuration widely, or let an agent act on untrusted content. Follow the returned safeguards and cite precedents by their…
- endpoint
- https://collectsea.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 collectsea live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is collectsea free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does collectsea have?
- 6 tools: analyze_design, search_incidents, get_safeguards, analyze_existing_app, get_incident, list_failure_patterns.
- Is collectsea 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 6 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
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.
list_failure_patterns open 1h ago
The 14 recurring failure patterns with triggers, warning signs and engineering principles.
{ "type": "object", "properties": {} }arguments 4 linesanalyze_design unknown never probed
Profile a proposed feature, system or AI-agent workflow and return documented incidents from systems that behaved similarly, their failure patterns, and the safeguards to build in. Use before writing code for anything that moves money, deletes data, changes permissions, runs code, or acts on external content.
{ "type": "object", "required": [ "proposal" ], "properties": { "proposal": { "type": "string", "description": "Two to five sentences: what the system does, what it can change, what data it reads, which services it calls." }, "max_results": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1 } } }arguments 18 linessearch_incidents unknown never probed
Keyword search over documented incidents and security advisories (company, technology, CVE, failure mode). Returns titles, summaries, evidence labels and URLs.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "e.g. \"idempotency\", \"Redis tenant\", \"prompt injection\", \"CVE-2021-44228\"" }, "cursor": { "type": "string", "description": "Pagination cursor from a previous call" }, "max_results": { "type": "integer", "default": 8, "maximum": 25, "minimum": 1 }, "include_advisories": { "type": "boolean", "default": true } } }arguments 26 linesget_safeguards unknown never probed
Return ready-to-save rules (AGENTS.md by default; also CLAUDE.md, Cursor rule or Copilot instructions) for a proposed design, each rule citing the incidents behind it.
{ "type": "object", "required": [ "proposal" ], "properties": { "mode": { "enum": [ "design", "existing_app" ], "type": "string", "default": "design" }, "format": { "enum": [ "agents", "claude", "cursor", "copilot" ], "type": "string", "default": "agents" }, "proposal": { "type": "string" } } }arguments 29 linesanalyze_existing_app unknown 1h ago
Analyze an existing app using observed behavior, README, architecture notes, configuration or source snippets. Provide a public GitHub repository_url to import selected context, or inspect a private repository locally and submit relevant text. Code is never executed and the running app is not scanned. Returns source context, behavior signals, historical precedents and safeguards to verify.
{ "type": "object", "anyOf": [ { "required": [ "proposal" ] }, { "required": [ "files" ] }, { "required": [ "repository_url" ] } ], "properties": { "files": { "type": "array", "items": { "type": "object", "required": [ "name", "content" ], "properties": { "name": { "type": "string", "maxLength": 160 }, "content": { "type": "string", "maxLength": 25000 } } }, "maxItems": 10, "description": "Relevant text files. Description plus file contents must fit within 25,000 characters and the 32 KB request limit. Remove credentials and personal data." }, "proposal": { "type": "string", "maxLength": 25000, "description": "Observed app behavior, integrations, data flows, permissions and deployment context. Optional when files are supplied." }, "max_results": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1 }, "repository_url": { "type": "string", "description": "Public GitHub repository home URL, e.g. https://github.com/owner/app. Imports a small selection of docs, config and source at one commit." } } }arguments 59 linesget_incident unknown 1h ago
Full record for one incident by ID (e.g. SEA-POST-005): what happened, source, failure pattern, safeguards and review status.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string" } } }arguments 11 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 id8855f33c1c047d49.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8855f33c1c047d49/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8855f33c1c047d49?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.