Company filing and CVE evidence snapshots
REMOTE · AGENT-RESEARCH-FISHNET.WALSH-DATASCIENCE.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 21
Company filing/CVE snapshots, status and optional feedback. Remote MCP or local stdio. Free Phase A.
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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Company filing and CVE evidence snapshots MCP server?
Company filing and CVE evidence snapshots is a hosted endpoint at https://agent-research-fishnet.walsh-datascience.workers.dev/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 · agent-research-fishnet.walsh-datascience.workers.dev
claude mcp add --transport http stavros65-fishnet-company-cve 'https://agent-research-fishnet.walsh-datascience.workers.dev/mcp'
{
"mcpServers": {
"stavros65-fishnet-company-cve": {
"url": "https://agent-research-fishnet.walsh-datascience.workers.dev/mcp"
}
}
} {
"servers": {
"stavros65-fishnet-company-cve": {
"type": "http",
"url": "https://agent-research-fishnet.walsh-datascience.workers.dev/mcp"
}
}
} [mcp_servers.stavros65-fishnet-company-cve] url = "https://agent-research-fishnet.walsh-datascience.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stavros65-fishnet-company-cve": {
"type": "remote",
"url": "https://agent-research-fishnet.walsh-datascience.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add stavros65-fishnet-company-cve --url 'https://agent-research-fishnet.walsh-datascience.workers.dev/mcp' --transport streamable-http
mcp_servers:
stavros65-fishnet-company-cve:
url: "https://agent-research-fishnet.walsh-datascience.workers.dev/mcp" {
"McpServers": {
"stavros65-fishnet-company-cve": {
"Transport": "http",
"Url": "https://agent-research-fishnet.walsh-datascience.workers.dev/mcp"
}
}
} assistant mcp add stavros65-fishnet-company-cve -t streamable-http -u 'https://agent-research-fishnet.walsh-datascience.workers.dev/mcp'
{
"mcpServers": {
"stavros65-fishnet-company-cve": {
"type": "http",
"url": "https://agent-research-fishnet.walsh-datascience.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 16 Sept 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +44
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Tool “cve_snapshot” rewrote its description, which is the text the model reads security
- Tool “company_snapshot” rewrote its description, which is the text the model reads security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.07 ▲ functional
- 11 Sept 26 −43
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 10 Sept 26 61
First indexed and scored.
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 21 Sept 2026 · Probed https://agent-research-fishnet.walsh-datascience.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=walsh-datascience.workers.dev | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e00f9715fe78be1b1317198aab790e2d |
| SANs: walsh-datascience.workers.dev, *.walsh-datascience.workers.dev | ||||||
| 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 agent-research-fishnet.walsh-datascience.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-research-fishnet.walsh-datascience.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://agent-research-fishnet.walsh-datascience.workers.dev/mcp | Inconclusive | 404 |
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_snapshot ~251
Use for current SEC filing-event state for a known ticker. Returns issuer/CIK, filing dates and source links with explicit source timestamps, coverage and expiry. Not financial-statement extraction, earnings transcripts or broad equity research.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_since | string | – | With view=status: a previous facts.state_hash. Compares selected state, not timestamp history. Unknown on source failures. |
| compare_sources | string | – | true requests unsupported comparative source reconciliation. |
| desired_fields | string | – | Comma-separated allowlisted field names; at most four. Preference only; supported requests still return the complete packet. Supported: issuer_identity, latest_filing, recent_filing_events, filing_so… |
| history_days | integer | – | Positive history depth is an unsupported-capability signal, not implemented history. |
| max_age | integer | – | Alias for max_age_seconds; no forced refresh. |
| max_age_seconds | integer | – | Optional declared maximum age. Too-old evidence returns 409; does not force upstream refresh. |
| ticker | string | yes | – |
| view | string | – | status returns selected fields from the same cached source packet; Phase A is free. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string|null | yes | – |
| available_capability | – | – | – |
| buyer_assent | object | yes | – |
| changes | object | yes | – |
| coverage | object | yes | – |
| data_hash | string | yes | – |
| facts | object | yes | – |
| feedback_request | – | – | – |
| generated_at | string | yes | – |
| methodology_hash | string | yes | – |
| packet_key | string|null | yes | – |
| packet_version | string | – | – |
| product_mode | – | yes | – |
| query | object|null | yes | – |
| requested_capabilities | array | – | – |
| requested_capability | string | – | – |
| result_hash | string | yes | – |
| schema_version | – | yes | – |
| sources | array | yes | – |
| status | – | – | – |
| terms_hash | string | yes | – |
| terms_version | string | yes | – |
| valid_until | string | yes | – |
| validation_metrics | array | yes | – |
No examples provided.
cve_snapshot ~261
Use for current evidence on a known CVE ID. Returns NVD status, CISA KEV membership, FIRST EPSS and advisory links with explicit source timestamps, coverage and expiry. Not asset applicability or validated remediation.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_since | string | – | With view=status: a previous facts.state_hash. Compares selected state, not timestamp history. Unknown on source failures. |
| compare_sources | string | – | true requests unsupported comparative source reconciliation. |
| cve | string | yes | – |
| desired_fields | string | – | Comma-separated allowlisted field names; at most four. Preference only; supported requests still return the complete packet. Supported: nvd_status, nvd_dates, cvss, cisa_kev, epss, vendor_advisory_li… |
| history_days | integer | – | Positive history depth is an unsupported-capability signal, not implemented history. |
| max_age | integer | – | Alias for max_age_seconds; no forced refresh. |
| max_age_seconds | integer | – | Optional declared maximum age. Too-old evidence returns 409; does not force upstream refresh. |
| view | string | – | status returns selected fields from the same cached source packet; Phase A is free. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string|null | yes | – |
| available_capability | – | – | – |
| buyer_assent | object | yes | – |
| changes | object | yes | – |
| coverage | object | yes | – |
| data_hash | string | yes | – |
| facts | object | yes | – |
| feedback_request | – | – | – |
| generated_at | string | yes | – |
| methodology_hash | string | yes | – |
| packet_key | string|null | yes | – |
| packet_version | string | – | – |
| product_mode | – | yes | – |
| query | object|null | yes | – |
| requested_capabilities | array | – | – |
| requested_capability | string | – | – |
| result_hash | string | yes | – |
| schema_version | – | yes | – |
| sources | array | yes | – |
| status | – | – | – |
| terms_hash | string | yes | – |
| terms_version | string | yes | – |
| valid_until | string | yes | – |
| validation_metrics | array | yes | – |
No examples provided.
submit_fishnet_feedback ~263
Optionally submit what you would have done next without enough Fishnet evidence. Use the packet feedback token and bounded schema. Writes feedback telemetry only; no payment, trading or other action. Never submitted automatically. Free text is classified then discarded; omit personal data and prompts.
| Name | Type | Req | Description |
|---|---|---|---|
| desired_capabilities | array | – | – |
| desired_capability | string | – | – |
| desired_fields | array | – | – |
| desired_freshness_seconds | integer | – | – |
| desired_history_days | integer | – | – |
| expected_calls_per_day | integer | – | Self-reported future frequency; not measured use. |
| feedback_type | string | yes | – |
| importance | integer | – | – |
| max_acceptable_price_usd | number | – | Self-reported price, at most six decimal places; never payment evidence. |
| next_action_without_fishnet | string | – | – |
| packet_endpoint | string | yes | – |
| packet_key | string | yes | – |
| packet_version | string | yes | – |
| schema_version | – | yes | – |
| short_request_text | string | – | At most 240 UTF-8 bytes; no personal data, URLs, credentials or full prompts. Classified coarsely then discarded. |
| token | string | yes | – |
| usage_reason | string | – | – |
No output schema declared.
No examples provided.
What is the Company filing and CVE evidence snapshots MCP server?
Company filing and CVE evidence snapshots is an MCP server listed in the public MCP registry as io.github.Stavros65/fishnet-company-cve. Company filing/CVE snapshots, status and optional feedback. Remote MCP or local stdio. Free Phase A. This page covers its hosted endpoint (https://agent-research-fishnet.walsh-datascience.workers.dev/mcp).
Is the Company filing and CVE evidence snapshots MCP server safe to use?
Company filing and CVE evidence snapshots scores 18 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 Company filing and CVE evidence snapshots MCP server expose?
Company filing and CVE evidence snapshots exposes 3 tools: company_snapshot, cve_snapshot, submit_fishnet_feedback. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.
Does the Company filing and CVE evidence snapshots MCP server require authentication?
No. We connected to Company filing and CVE evidence snapshots without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Company filing and CVE evidence snapshots MCP server still maintained?
Company filing and CVE evidence snapshots is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.