Company filing and CVE evidence snapshots
MCPB · FISHNET-COMPANY-CVE-MCP-0.2.0.MCPB · 2 COMPONENTS
Company filing/CVE snapshots, status and optional feedback. Remote MCP or local stdio. Free Phase A.
Last scanned (18 hours ago)
Scores higher than 74% of MCPB servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency39
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Maintenance history not yet determined.Unverified
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability50
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 735 tokens (~245/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (9)
- Source repository
- License
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (7)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Provenance in Provenance & TransparencyBuild provenance not yet verified.
- Maintenance in Provenance & TransparencyMaintenance history not yet determined.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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 −4
- Provenance: fail → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Stability: pass → 0.80 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 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 · Analysed mcpb/https://github.com/Stavros65/fishnet-company-cve/releases/download/v0.2.0/fishnet-company-cve-mcp-0.2.0.mcpb
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | mcpb |
| Reason | Check deferred |
Background: How many MCP packages publish verified provenance →
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 ~225
Returns current company filing-event evidence packet for a ticker. No earnings transcript or extracted financial statements.
| 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 ~247
Returns current CVE evidence packet with NVD status, CISA catalog membership, EPSS and vendor-advisory links. No asset applicability analysis.
| 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.
How do I install the Company filing and CVE evidence snapshots MCP server?
Company filing and CVE evidence snapshots ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · fishnet-company-cve-mcp-0.2.0.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
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 MCPB bundle (https://github.com/Stavros65/fishnet-company-cve/releases/download/v0.2.0/fishnet-company-cve-mcp-0.2.0.mcpb).
Is the Company filing and CVE evidence snapshots MCP server safe to use?
Company filing and CVE evidence snapshots scores 43 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 735 tokens of context every time the server is loaded.
What licence is the Company filing and CVE evidence snapshots MCP server under?
Company filing and CVE evidence snapshots declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Company filing and CVE evidence snapshots MCP server?
VerifyMCP ran 9 checks on Company filing and CVE evidence snapshots, covering Source repository, License, Schema quality, Stability and 5 more. 7 items could not be completed, a gap on our side rather than a finding about Company filing and CVE evidence snapshots: Malware scan, Known CVEs, Install scripts, Dependency health and 3 more. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.