Catalyst Edge Research
PYPI · CATALYST-EDGE-MCP
Source-linked market intelligence for AI agents researching public-company tickers.
Available components
Last scanned (19 hours ago)
Scores higher than 88% of PyPI servers
Category Finance and Payments
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rm0nroe/catalyst-edge-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 138 tokens (~69/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% 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 2 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −19
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.67 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.80 → pass security
- 16 Oct 26 −2
- Stability: pass → 0.80 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 · Analysed pypi/catalyst-edge-mcp@0.1.8
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | rm0nroe/catalyst-edge-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/rm0nroe/catalyst-edge-mcp/.github/workflows/publish-pypi.yml@refs/heads/main |
| Rekor log index | 2591877397 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4dedf584eaad5de1daa9da8609aab3cb80cbb881b772b170d3ad423a697ddc13 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
catalyst_edge_claim_sources Read grouped claim sources ~49
Use with a dossier claim ID to read one bounded page of its immutable source records.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_id | string | yes | – |
| cursor | integer | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | – | – |
| claim_id | string | yes | – |
| cursor | integer | yes | – |
| next_cursor | – | – | – |
| sources | array | – | – |
| total_sources | integer | yes | – |
No examples provided.
catalyst_edge_score Research ticker catalysts ~64
Use for ticker research to assess recent evidence, provenance, and next checks.
| Name | Type | Req | Description |
|---|---|---|---|
| include_raw_signals | boolean | – | – |
| include_sources | boolean | – | – |
| lookback_days | integer | – | – |
| risk_mode | – | – | – |
| ticker | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| attributions | array | – | – |
| data_quality | – | yes | – |
| edge | – | yes | – |
| evidence | array | yes | – |
| lookback_days | integer | yes | – |
| next_checks | array | yes | – |
| research | – | yes | – |
| summary | – | yes | – |
| ticker | string | yes | – |
No examples provided.
How do I install the Catalyst Edge Research MCP server?
Catalyst Edge Research runs locally as a PyPI package, launched with uvx catalyst-edge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · catalyst-edge-mcp
claude mcp add rm0nroe-catalyst-edge-mcp -- uvx catalyst-edge-mcp
What is the Catalyst Edge Research MCP server?
Catalyst Edge Research is an MCP server listed in the public MCP registry as io.github.rm0nroe/catalyst-edge-mcp. Source-linked market intelligence for AI agents researching public-company tickers. This page covers its PyPI package (catalyst-edge-mcp).
Is the Catalyst Edge Research MCP server safe to use?
Catalyst Edge Research scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Catalyst Edge Research MCP server expose?
Catalyst Edge Research exposes 2 tools: catalyst_edge_score, catalyst_edge_claim_sources. Their descriptions and schemas cost roughly 113 tokens of context every time the server is loaded.
Is the Catalyst Edge Research MCP server still maintained?
Catalyst Edge Research 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 licence is the Catalyst Edge Research MCP server under?
Catalyst Edge Research 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 Catalyst Edge Research MCP server?
VerifyMCP ran 16 checks on Catalyst Edge Research, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.