# MoneyTools Inference Fidelity Audit (remote · fidelity.moneytools.dev)

Audit inference sellers; quick/bill check 0.005, full audit 0.02 USDC

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

## Components

- remote · `fidelity.moneytools.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-moneytools-fidelity/fidelity.md), [page](https://verifymcp.io/servers/dev-moneytools-fidelity/fidelity)

## Channel facts

- Endpoint: `https://fidelity.moneytools.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.10`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 686 tokens (~137/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MoneyTools Inference Fidelity Audit MCP server?

MoneyTools Inference Fidelity Audit is a hosted endpoint at https://fidelity.moneytools.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-moneytools-fidelity 'https://fidelity.moneytools.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-moneytools-fidelity": {
      "url": "https://fidelity.moneytools.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-moneytools-fidelity": {
      "type": "http",
      "url": "https://fidelity.moneytools.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-moneytools-fidelity]
url = "https://fidelity.moneytools.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-moneytools-fidelity": {
      "type": "remote",
      "url": "https://fidelity.moneytools.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-moneytools-fidelity --url 'https://fidelity.moneytools.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-moneytools-fidelity:
    url: "https://fidelity.moneytools.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-moneytools-fidelity": {
      "Transport": "http",
      "Url": "https://fidelity.moneytools.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-moneytools-fidelity -t streamable-http -u 'https://fidelity.moneytools.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-moneytools-fidelity": {
      "type": "http",
      "url": "https://fidelity.moneytools.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 70, +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-18 (score 69, +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-11-16 (score 68, +1)

- [security] Tool “fidelity_audit” rewrote its description, which is the text the model reads

### 2026-11-14 (score 67, +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-11-13 (score 66, 0)

- [security] Tool “fidelity_bill_check” rewrote its description, which is the text the model reads
- [security] Tool “fidelity_report” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.11 → 1.0.12

### 2026-11-11 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 65)

First indexed and scored.

## MCP tools (5)

### `fidelity_report` (~42 tokens)

Paid, read-only: probe catalog + supported Workers AI models + pricing snapshot. 0.005 USDC via x402 (strictly paid — no free tier).

### `fidelity_audit` (~207 tokens)

Audit a seller vs Cloudflare Workers AI reference. Free 2/day then 0.02 USDC. Auth header never stored.

Input parameters:

- `apiKey` (string): Unused placeholder for client compatibility; payments use x402 headers / free quota
- `authHeader` (string): Optional Authorization value for the target (Bearer …). Used in memory only; never stored or logged.
- `endpoint` (string, required): OpenAI-compatible base URL (https://…/v1) or chat completions URL
- `model` (string, required): Claimed model id. Supported: llama-3.1-8b, llama-3.2-3b, llama-3.3-70b, llama-4-scout, qwen3-30b, qwen2.5-coder-32b, gpt-oss-20b, gpt-oss-120b, gemma-4-26b, glm-4.7-flash

### `fidelity_quick_check` (~209 tokens)

1-probe indicative check of a seller vs Cloudflare Workers AI reference (cheaper than a full audit). Free 3/day then 0.005 USDC via x402 (MCP: params._meta["x402/payment"]). Auth header never stored.

Input parameters:

- `authHeader` (string): Optional Authorization value for the target. Used in memory only; never stored or logged.
- `endpoint` (string, required): OpenAI-compatible base URL (https://…/v1) or chat completions URL
- `model` (string, required): Claimed model id. Supported: llama-3.1-8b, llama-3.2-3b, llama-3.3-70b, llama-4-scout, qwen3-30b, qwen2.5-coder-32b, gpt-oss-20b, gpt-oss-120b, gemma-4-26b, glm-4.7-flash

### `fidelity_bill_check` (~145 tokens)

Recount visible tokens vs seller usage/charge. Free 5/day then 0.005 USDC.

Input parameters:

- `chargedAtomic` (number): Amount charged in USDC atomic units (1e6 = 1 USDC)
- `chargedUsd` (number): Amount charged in USDC (optional)
- `model` (string): Claimed model id (informational)
- `priceTable` (object): Optional {inputPerMTok, outputPerMTok} USD per million tokens
- `request` (object): Original request (messages) for input size estimate
- `response` (object, required): Seller response object with content and optional usage {prompt_tokens,completion_tokens}

### `fidelity_models` (~20 tokens)

List supported Workers AI reference models (free, read-only).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-moneytools-fidelity/fidelity#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 66
- 2026-11-10: 65

## Common questions

### What is the MoneyTools Inference Fidelity Audit MCP server?

MoneyTools Inference Fidelity Audit is an MCP server listed in the public MCP registry as dev.moneytools/fidelity. Audit inference sellers; quick/bill check 0.005, full audit 0.02 USDC. This page covers its hosted endpoint (https://fidelity.moneytools.dev/mcp).

### Is the MoneyTools Inference Fidelity Audit MCP server safe to use?

MoneyTools Inference Fidelity Audit scores 70 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 MoneyTools Inference Fidelity Audit MCP server expose?

MoneyTools Inference Fidelity Audit exposes 5 tools: fidelity_report, fidelity_audit, fidelity_quick_check, fidelity_bill_check, fidelity_models. Their descriptions and schemas cost roughly 623 tokens of context every time the server is loaded.

### Does the MoneyTools Inference Fidelity Audit MCP server require authentication?

No. We connected to MoneyTools Inference Fidelity Audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MoneyTools Inference Fidelity Audit MCP server still maintained?

MoneyTools Inference Fidelity Audit is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the MoneyTools Inference Fidelity Audit MCP server?

VerifyMCP ran 13 checks on MoneyTools Inference Fidelity Audit, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://fidelity.moneytools.dev/mcp
- Website: https://fidelity.moneytools.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-moneytools-fidelity/fidelity.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-moneytools-fidelity/fidelity/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-moneytools-fidelity/fidelity.json
- HTML version of this page: https://verifymcp.io/servers/dev-moneytools-fidelity/fidelity
