# Gateway Price Disclosure Check (mcpb · gateway-price-check-mcp.mcpb)

Checks whether an OpenAI-compatible endpoint publishes model prices without an account or key.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- mcpb · `gateway-price-check-mcp.mcpb`: 39/100 (this document), [markdown](https://verifymcp.io/servers/happy520ai-gateway-price-check/gateway-price-check-mcp.md), [page](https://verifymcp.io/servers/happy520ai-gateway-price-check/gateway-price-check-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/happy520ai/gateway-price-check/releases/download/v0.5.8/gateway-price-check-mcp.mcpb`
- Transport: `stdio`
- SHA-256: `459cf932f7de85d751b7108e79fdc16668a83b0ce8cefac0941b05199fdffe7d`

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

- **Supply Chain Security**: 0/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).
  - Install-script risk not yet assessed.
  - 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 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 253 tokens (~126/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_price_disclosure" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

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

## Install

### How do I install the Gateway Price Disclosure Check MCP server?

Gateway Price Disclosure Check 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, 459cf932f7de85d751b7108e79fdc16668a83b0ce8cefac0941b05199fdffe7d; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/happy520ai/gateway-price-check/releases/download/v0.5.8/gateway-price-check-mcp.mcpb`
- SHA-256: `459cf932f7de85d751b7108e79fdc16668a83b0ce8cefac0941b05199fdffe7d`

### Verify on macOS / Linux

```bash
echo "459cf932f7de85d751b7108e79fdc16668a83b0ce8cefac0941b05199fdffe7d  gateway-price-check-mcp.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\gateway-price-check-mcp.mcpb).Hash -eq "459cf932f7de85d751b7108e79fdc16668a83b0ce8cefac0941b05199fdffe7d"
```

## 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-10-23 (score 39, +1)

- [security regression] Provenance: unverified → fail

### 2026-10-22 (score 38, 0)

- [security regression] Provenance: fail → unverified

### 2026-10-21 (score 38, +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-19 (score 37, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 36)

First indexed and scored.

## MCP tools (2)

### `check_price_disclosure` (~120 tokens)

Sends exactly one unauthenticated GET to an OpenAI-compatible /v1/models endpoint and reports whether model prices are published before you sign up. Verdicts: YES, NO, AUTH, ERR, UNKNOWN — ERR/UNKNOWN are statements about the probe, not the vendor. Never sends a key, never sends a completion request, so it does not assess model fidelity.

Input parameters:

- `name` (string): Display label for the reading
- `url` (string, required): https base URL (…/v1) or full …/v1/models URL

### `latest_archive_readings` (~67 tokens)

Returns the readings this repository's CI archived (today by default, or a given UTC+08 date YYYY-MM-DD) across all monitored gateways, as published — no re-probing.

Input parameters:

- `date` (string): Archive day, e.g. 2026-10-17

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/happy520ai-gateway-price-check/gateway-price-check-mcp#diagnostics

## Score history

- 2026-10-23: 39
- 2026-10-22: 38
- 2026-10-21: 38
- 2026-10-20: 37
- 2026-10-19: 37
- 2026-10-18: 36
- 2026-10-17: 36

## Common questions

### What is the Gateway Price Disclosure Check MCP server?

Gateway Price Disclosure Check is an MCP server listed in the public MCP registry as io.github.happy520ai/gateway-price-check. Checks whether an OpenAI-compatible endpoint publishes model prices without an account or key. This page covers its MCPB bundle (https://github.com/happy520ai/gateway-price-check/releases/download/v0.5.8/gateway-price-check-mcp.mcpb).

### Is the Gateway Price Disclosure Check MCP server safe to use?

Gateway Price Disclosure Check scores 39 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 Gateway Price Disclosure Check MCP server expose?

Gateway Price Disclosure Check exposes 2 tools: check_price_disclosure, latest_archive_readings. Their descriptions and schemas cost roughly 187 tokens of context every time the server is loaded.

### What licence is the Gateway Price Disclosure Check MCP server under?

Gateway Price Disclosure Check 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/happy520ai/gateway-price-check
- Changelog RSS feed: https://verifymcp.io/servers/happy520ai-gateway-price-check/gateway-price-check-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/happy520ai-gateway-price-check/gateway-price-check-mcp.json
- HTML version of this page: https://verifymcp.io/servers/happy520ai-gateway-price-check/gateway-price-check-mcp