CollectSEA
REMOTE · COLLECTSEA.COM
Find real software, security and AI-agent failures that resemble your design, with safeguards.
Available components
Last scanned (32 minutes ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 659 tokens (~109/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Server version: 2026.10.18-review-reliability → 2026.10.22-review-workspace functional
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://collectsea.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=collectsea.com | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b0d20d4d2350295d13b7b4c78015d31e |
| SANs: collectsea.com, docs.collectsea.com, *.docs.collectsea.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of collectsea.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| collectsea.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://collectsea.com/mcp | Verified | 200 | |
| http (plaintext) | http://collectsea.com/mcp | HTTPS enforced | 301 | https://collectsea.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_design Find failure precedents for a design ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| proposal | string | yes | Two to five sentences: what the system does, what it can change, what data it reads, which services it calls. |
No output schema declared.
No examples provided.
analyze_existing_app Find failure precedents for an existing app ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Relevant text files. Description plus file contents must fit within 25,000 characters and the 32 KB request limit. Remove credentials and personal data. |
| max_results | integer | – | – |
| proposal | string | – | Observed app behavior, integrations, data flows, permissions and deployment context. Optional when files are supplied. |
| repository_url | string | – | Public GitHub repository home URL, e.g. https://github.com/owner/app. Imports a small selection of docs, config and source at one commit. |
No output schema declared.
No examples provided.
get_incident Get one incident record ~46
Full record for one incident by ID (e.g. SEA-POST-005): what happened, source, failure pattern, safeguards and review status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_safeguards Get agent rules for a design ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| mode | string | – | – |
| proposal | string | yes | – |
No output schema declared.
No examples provided.
list_failure_patterns List failure patterns ~24
The 14 recurring failure patterns with triggers, warning signs and engineering principles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_incidents Search the incident database ~102
Keyword search over documented incidents and security advisories (company, technology, CVE, failure mode). Returns titles, summaries, evidence labels and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call |
| include_advisories | boolean | – | – |
| max_results | integer | – | – |
| query | string | yes | e.g. "idempotency", "Redis tenant", "prompt injection", "CVE-2021-44228" |
No output schema declared.
No examples provided.
How do I install the CollectSEA MCP server?
CollectSEA is a hosted endpoint at https://collectsea.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · collectsea.com
claude mcp add --transport http kelvin-ling-collectsea 'https://collectsea.com/mcp'
What is the CollectSEA MCP server?
CollectSEA is an MCP server listed in the public MCP registry as io.github.kelvin-ling/collectsea. Find real software, security and AI-agent failures that resemble your design, with safeguards. This page covers its hosted endpoint (https://collectsea.com/mcp).
Is the CollectSEA MCP server safe to use?
CollectSEA scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CollectSEA MCP server expose?
CollectSEA exposes 6 tools: analyze_design, analyze_existing_app, search_incidents, get_incident, list_failure_patterns, get_safeguards. Their descriptions and schemas cost roughly 532 tokens of context every time the server is loaded.
Does the CollectSEA MCP server require authentication?
No. We connected to CollectSEA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CollectSEA MCP server still maintained?
CollectSEA is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.