# AhaSignals Evidence (mcpb · ahasignals-evidence-mcp-0.2.0.mcpb)

Read-only financial evidence: disclosure cutoffs, operating changes and cash calculations.

- Trust score: 46/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `ahasignals-evidence-mcp-0.2.0.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/com-ahasignals-evidence/ahasignals-evidence-mcp.md), [page](https://verifymcp.io/servers/com-ahasignals-evidence/ahasignals-evidence-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/AhaSignals/evidence-mcp/releases/download/v0.2.0/ahasignals-evidence-mcp-0.2.0.mcpb`
- Transport: `stdio`
- SHA-256: `d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 13/100
  - 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 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).
  - No install/post-install scripts declared.
  - 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 & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 549 tokens (~61/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 47% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

- Download bundle: `https://github.com/AhaSignals/evidence-mcp/releases/download/v0.2.0/ahasignals-evidence-mcp-0.2.0.mcpb`
- SHA-256: `d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25`

### Verify on macOS / Linux

```bash
echo "d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25  ahasignals-evidence-mcp-0.2.0.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\ahasignals-evidence-mcp-0.2.0.mcpb).Hash -eq "d3ead277bf98bc1f832acd837f16d0a3448c654dd3325cfc44b7c8411bce8f25"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 46, +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.

### 2026-11-02 (score 45, +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.

### 2026-10-31 (score 44, +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.

### 2026-10-29 (score 43, +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.

### 2026-10-27 (score 42, +1)

- [functional regression] Schema quality: 431 → 549
- [functional improvement] Tool coverage: 42% → 47%
- [functional improvement] Stability: unverified → 0.07

### 2026-10-26 (score 41, +1)

- [functional improvement] Maintenance: unverified → pass

### 2026-10-25 (score 40)

First indexed and scored.

## MCP tools (9)

### `get_coverage` (~31 tokens)

Read fixed package coverage, review clocks and source-health snapshot. Start here; different tools cover different company sets.

### `query_disclosure_evidence` (~57 tokens)

Query retained and reviewed global AI disclosure evidence at a cutoff. Does not certify first-public availability.

Input parameters:

- `asOf` (string, required): ISO timestamp with explicit timezone. Admission uses capture and review clocks.
- `entity` (string)

### `get_operating_changes` (~87 tokens)

List admitted operating annotations for CRM, ADBE, INTU or PYPL. A newly admitted record is not necessarily a new business change.

Input parameters:

- `asOf` (string, required): 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.

### `trace_claim` (~55 tokens)

Trace an operating record to its source, capture and review clocks. Missing successor evidence stays unknown.

Input parameters:

- `asOf` (string, required): ISO timestamp with explicit timezone. Admission uses capture and review clocks.
- `recordId` (string, required)

### `check_cash_bridge` (~58 tokens)

Recompute a reviewed operating-pilot cash calculation with exact decimals. Requires matching period, unit and scope.

Input parameters:

- `asOf` (string, required): ISO timestamp with explicit timezone. Admission uses capture and review clocks.
- `recordId` (string, required)

### `review_claim` (~36 tokens)

Review cash evidence for the historical 12-company cash cohort. Does not cover all expanded global issuers.

Input parameters:

- `request` (object, required)

### `query_compute_commitments` (~56 tokens)

Read reviewed compute contract terms, payment conditions, linked claims and source clocks. Selected counterparty case; overlapping obligations cannot be summed.

Input parameters:

- `asOf` (string, required): ISO timestamp with explicit timezone. Admission uses capture and review clocks.

### `check_compute_cash_bridge` (~62 tokens)

Recompute a selected company cash bridge, preserving source, period, scope and units. Does not establish contract cash payments.

Input parameters:

- `asOf` (string, required): ISO timestamp with explicit timezone. Admission uses capture and review clocks.
- `bridgeId` (string, required)

### `replay_evidence` (~50 tokens)

Verify and recompute a saved packet using this exact bundled snapshot. Supply packet text and its separately saved SHA-256.

Input parameters:

- `packetSha256` (string, required)
- `packetText` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/com-ahasignals-evidence/ahasignals-evidence-mcp#diagnostics

## Score history

- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 45
- 2026-11-02: 45
- 2026-11-01: 44
- 2026-10-31: 44
- 2026-10-30: 43
- 2026-10-29: 43
- 2026-10-28: 42
- 2026-10-27: 42
- 2026-10-26: 41
- 2026-10-25: 40

## Common questions

### 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.

## Links

- Repository: https://github.com/AhaSignals/evidence-mcp
- Website: https://ahasignals.com/research/company-kpi-history/#agent-connection
- Changelog RSS feed: https://verifymcp.io/servers/com-ahasignals-evidence/ahasignals-evidence-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ahasignals-evidence/ahasignals-evidence-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-ahasignals-evidence/ahasignals-evidence-mcp