com.dropwatchhq/sec-intel
REMOTE · FILINGS.DROPWATCHHQ.COM
Fresh SEC filing intel: 8-K events, Form 4 insider activity, risk-language, filing velocity, watch.
Available components
Last scanned (11 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 507 tokens (~101/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 39% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://filings.dropwatchhq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dropwatchhq.com | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2dfe2c8f366438a132acfba5c38edae |
| SANs: dropwatchhq.com, filings.dropwatchhq.com, *.filings.dropwatchhq.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 filings.dropwatchhq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| dropwatchhq.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://filings.dropwatchhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://filings.dropwatchhq.com/mcp | Served over HTTP | 200 |
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 →
company_watch ~56
Given a company CIK, return recent filings, insider activity, and a filing-velocity stat (last-90 vs prior-90 days). Live-backfilled from EDGAR so it works day one.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | – |
No output schema declared.
No examples provided.
filing_digest ~104
Digest for a filter over the last N days: material 8-K events, insider (Form 4) activity, new registrations, and periodic reports. Best summary signal for a desk.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | – |
| company | string | – | – |
| days | number | – | Lookback days (default 7). |
| form | array | – | – |
| item | string | – | – |
| minEventScore | number | – | – |
| ticker | string | – | – |
No output schema declared.
No examples provided.
insider_activity ~62
Recent Form 4/3/5 insider transactions with insider-cluster detection (multiple insiders filing on the same issuer). Optionally filter by ticker/CIK.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | – |
| days | number | – | – |
| ticker | string | – | – |
No output schema declared.
No examples provided.
search_filings ~94
Direct live search of SEC EDGAR full-text for the latest filings of a form type in a date range. Use for ad-hoc lookups.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | – |
| form | string | – | Form type, e.g. '8-K'. |
| limit | number | – | Default 50, max 100. |
| q | string | – | Optional full-text query. |
| start | string | – | – |
No output schema declared.
No examples provided.
whats_new_since ~191
Return SEC filings that are NEW since a cursor token (your bookmark). Pass the cursor from a prior call to get only filings since then. Filter by form type, ticker, CIK, 8-K item code, and minimum event severity. This is the fresh-filing delta feed's core lock-in primitive. Monitoring/research over public EDGAR data — not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | – |
| cursor | string | – | Opaque cursor from a previous response; omit for first call. |
| form | array | – | Form types, e.g. ['8-K','4']. |
| item | string | – | 8-K item code, e.g. '5.02'. |
| limit | number | – | Max filings to return (default 100). |
| minEventScore | number | – | Severity floor 1-10 (material events only). |
| ticker | string | – | – |
No output schema declared.
No examples provided.
How do I install the com.dropwatchhq/sec-intel MCP server?
com.dropwatchhq/sec-intel is a hosted endpoint at https://filings.dropwatchhq.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 · filings.dropwatchhq.com
claude mcp add --transport http com-dropwatchhq-sec-intel 'https://filings.dropwatchhq.com/mcp'
What is the com.dropwatchhq/sec-intel MCP server?
com.dropwatchhq/sec-intel is an MCP server listed in the public MCP registry as com.dropwatchhq/sec-intel. Fresh SEC filing intel: 8-K events, Form 4 insider activity, risk-language, filing velocity, watch. This page covers its hosted endpoint (https://filings.dropwatchhq.com/mcp).
Is the com.dropwatchhq/sec-intel MCP server safe to use?
com.dropwatchhq/sec-intel scores 67 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 com.dropwatchhq/sec-intel MCP server expose?
com.dropwatchhq/sec-intel exposes 5 tools: whats_new_since, filing_digest, company_watch, insider_activity, search_filings. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.
Does the com.dropwatchhq/sec-intel MCP server require authentication?
No. We connected to com.dropwatchhq/sec-intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.dropwatchhq/sec-intel MCP server still maintained?
com.dropwatchhq/sec-intel 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.
What did VerifyMCP test on the com.dropwatchhq/sec-intel MCP server?
VerifyMCP ran 12 checks on com.dropwatchhq/sec-intel, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.dropwatchhq/sec-intel: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.