AhaSignals Evidence
MCPB · AHASIGNALS-EVIDENCE-MCP-0.2.0.MCPB
Read-only financial evidence: disclosure cutoffs, operating changes and cash calculations.
Available components
Last scanned (21 hours ago)
Scores higher than 76% of MCPB 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 Security13
- 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
- No install/post-install scripts declared.Pass
- 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 & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 549 tokens (~61/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 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.
- 27 Oct 26 +1
- Schema quality: 431 → 549 ▼ functional
- Tool coverage: 42% → 47% ▲ functional
- Stability: unverified → 0.07 ▲ functional
- 26 Oct 26 +1
- Maintenance: unverified → pass ▲ functional
- 25 Oct 26 40
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 4 Nov 2026 · Analysed mcpb/https://github.com/AhaSignals/evidence-mcp/releases/download/v0.2.0/ahasignals-evidence-mcp-0.2.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
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 →
check_cash_bridge ~58
Recompute a reviewed operating-pilot cash calculation with exact decimals. Requires matching period, unit and scope.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | ISO timestamp with explicit timezone. Admission uses capture and review clocks. |
| recordId | string | yes | – |
No output schema declared.
No examples provided.
check_compute_cash_bridge ~62
Recompute a selected company cash bridge, preserving source, period, scope and units. Does not establish contract cash payments.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | ISO timestamp with explicit timezone. Admission uses capture and review clocks. |
| bridgeId | string | yes | – |
No output schema declared.
No examples provided.
get_coverage ~31
Read fixed package coverage, review clocks and source-health snapshot. Start here; different tools cover different company sets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_operating_changes ~87
List admitted operating annotations for CRM, ADBE, INTU or PYPL. A newly admitted record is not necessarily a new business change.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | ISO timestamp with explicit timezone. Admission uses capture and review clocks. |
| issuer | string | – | – |
| previousAsOf | string | – | ISO timestamp with explicit timezone. Admission uses capture and review clocks. |
No output schema declared.
No examples provided.
query_compute_commitments ~56
Read reviewed compute contract terms, payment conditions, linked claims and source clocks. Selected counterparty case; overlapping obligations cannot be summed.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | ISO timestamp with explicit timezone. Admission uses capture and review clocks. |
No output schema declared.
No examples provided.
query_disclosure_evidence ~57
Query retained and reviewed global AI disclosure evidence at a cutoff. Does not certify first-public availability.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | ISO timestamp with explicit timezone. Admission uses capture and review clocks. |
| entity | string | – | – |
No output schema declared.
No examples provided.
replay_evidence ~50
Verify and recompute a saved packet using this exact bundled snapshot. Supply packet text and its separately saved SHA-256.
| Name | Type | Req | Description |
|---|---|---|---|
| packetSha256 | string | yes | – |
| packetText | string | yes | – |
No output schema declared.
No examples provided.
review_claim ~36
Review cash evidence for the historical 12-company cash cohort. Does not cover all expanded global issuers.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | – |
No output schema declared.
No examples provided.
trace_claim ~55
Trace an operating record to its source, capture and review clocks. Missing successor evidence stays unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | ISO timestamp with explicit timezone. Admission uses capture and review clocks. |
| recordId | string | yes | – |
No output schema declared.
No examples provided.
How do I install the AhaSignals Evidence MCP server?
AhaSignals Evidence 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. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25; the commands to do that are on this page. If it does not match, do not open it.
mcpb · ahasignals-evidence-mcp-0.2.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25
macOS / Linux
echo "d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25 ahasignals-evidence-mcp-0.2.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\ahasignals-evidence-mcp-0.2.0.mcpb).Hash -eq "d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the AhaSignals Evidence MCP server?
AhaSignals Evidence is an MCP server listed in the public MCP registry as com.ahasignals/evidence. Read-only financial evidence: disclosure cutoffs, operating changes and cash calculations. This page covers its MCPB bundle (https://github.com/AhaSignals/evidence-mcp/releases/download/v0.2.0/ahasignals-evidence-mcp-0.2.0.mcpb).
Is the AhaSignals Evidence MCP server safe to use?
AhaSignals Evidence scores 46 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 AhaSignals Evidence MCP server expose?
AhaSignals Evidence exposes 9 tools: get_coverage, query_disclosure_evidence, get_operating_changes, trace_claim, check_cash_bridge, and 4 more. Their descriptions and schemas cost roughly 492 tokens of context every time the server is loaded.
What licence is the AhaSignals Evidence MCP server under?
AhaSignals Evidence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.