# MCPFax Reliability (remote · mcpfax-reliability.bowling-anthony.workers.dev)

Before you pay an endpoint you cannot vouch for: credit grade, drift and preflight.

- Trust score: 0/100 (low)
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-08-12

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `mcpfax-reliability.bowling-anthony.workers.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/com-mcpscores-agent-reliability-scores/mcpfax-reliability.md), [page](https://verifymcp.io/servers/com-mcpscores-agent-reliability-scores/mcpfax-reliability)

## Channel facts

- Endpoint: `https://mcpfax-reliability.bowling-anthony.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.5`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1005 tokens (~201/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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**: not scored yet
  - Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the MCPFax Reliability MCP server?

MCPFax Reliability is a hosted endpoint at https://mcpfax-reliability.bowling-anthony.workers.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 com-mcpscores-agent-reliability-scores 'https://mcpfax-reliability.bowling-anthony.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mcpscores-agent-reliability-scores": {
      "url": "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mcpscores-agent-reliability-scores": {
      "type": "http",
      "url": "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mcpscores-agent-reliability-scores]
url = "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcpscores-agent-reliability-scores": {
      "type": "remote",
      "url": "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mcpscores-agent-reliability-scores --url 'https://mcpfax-reliability.bowling-anthony.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mcpscores-agent-reliability-scores:
    url: "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mcpscores-agent-reliability-scores": {
      "Transport": "http",
      "Url": "https://mcpfax-reliability.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mcpscores-agent-reliability-scores -t streamable-http -u 'https://mcpfax-reliability.bowling-anthony.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mcpscores-agent-reliability-scores": {
      "type": "http",
      "url": "https://mcpfax-reliability.bowling-anthony.workers.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-08-12 (score 0)

First indexed and scored.

## MCP tools (5)

### `mcpfax_endpoint_credit_score` (~221 tokens)

Endpoint credit score

Creditworthiness grade for one x402 endpoint or MCP server: letter grade A-E (or NR when unrated), a 0-1000 score, per-component subscores, a confidence level, flags, and the dated evidence each figure rests on. Use this before trusting or paying an unfamiliar endpoint. The grade ranks observed risk; it is not a calibrated probability of failure, not validated over any forward horizon, and not a security audit. Coverage is young: the response carries archive_coverage (measured archive span), most listings grade NR, and payer-concentration risk is reported as "not rated" until a listing's own payment record clears the published coverage floor. Costs $0.005 USDC per call via x402 on Base.

Input parameters:

- `endpoint` (string, required): Observatory listing id. Use 'host:<hostname>' for an x402 endpoint, e.g. 'host:api.example.com', or 'mcp:<publisher>/<name>' for a registry-listed MCP server, e.g. 'mcp:acme/weather'.

### `mcpfax_wallet_authenticity` (~218 tokens)

Wallet authenticity and wash-risk

Payer-concentration and wash-risk assessment for a receiving wallet: how concentrated its observed payers are, the measured coverage of that observation, an explicit wash-risk haircut ONLY when coverage is sufficient, how many listings declare the same address, and observed USDC inflow. Use this to judge whether a seller's apparent revenue reflects real independent demand. The haircut and the adjusted-inflow figure are withheld as null with status "not_rated" until the wallet's own record covers at least 14 days and 20 payments, because below that a thin payer count is a property of our observation window, not of the wallet. Concentration is not proof of common control. Costs $0.02 USDC per call via x402 on Base.

Input parameters:

- `wallet` (string, required): The receiving EVM wallet address, 0x followed by 40 hex characters, e.g. '0x1831f336585a6C67B6A954d28f3E07F44C4EEBbd'.

### `mcpfax_endpoint_revenue_estimate` (~213 tokens)

Endpoint revenue estimate

Observed on-chain revenue signals for one listing: total USDC inflow, how many distinct payers, the modal transfer size, payment rate, 7- and 30-day trend windows, and where it sits in its cohort by percentile. Use this to size a seller's real traction. Inflow is observed on-chain and is not proven to be x402 sales revenue. Trend windows are only as wide as the wallet's real scanned span, which the response reports as trends.scanned_days with per-window backed-by-scan flags; a 30-day window is not yet backed by 30 days of scanning. Costs $0.01 USDC per call via x402 on Base.

Input parameters:

- `endpoint` (string, required): Observatory listing id. Use 'host:<hostname>' for an x402 endpoint, e.g. 'host:api.example.com', or 'mcp:<publisher>/<name>' for a registry-listed MCP server, e.g. 'mcp:acme/weather'.

### `mcpfax_payer_wallet_profile` (~147 tokens)

Payer wallet profile

Know-your-agent profile for a paying wallet: how many distinct services it pays, total observed spend, whether the address is a contract or an externally owned account, and coverage-gated screening signals. Use this to vet a counterparty that is paying you. Screening signals are withheld with status "not_rated" until the observed record for the address clears the published coverage floor (14 days, 20 payments); the measured graph facts are always returned and carry no inference about intent. Costs $0.005 USDC per call via x402 on Base.

Input parameters:

- `address` (string, required): The paying EVM wallet address, 0x followed by 40 hex characters.

### `mcpfax_payto_change_feed` (~179 tokens)

Rating action and payTo change feed

Chronological feed of rating actions since a date: grade upgrades and downgrades, payTo wallet changes (a seller redirecting payment), listing removals, and returns. Use this to monitor a portfolio of endpoints for adverse changes rather than re-scoring each one. The feed cannot return events from before the observatory archive started; the response reports coverage.archive_since, coverage.rating_actions_recorded, and whether the requested window predates the archive. Costs $0.001 USDC per call via x402 on Base.

Input parameters:

- `since` (string): Inclusive UTC start date in YYYY-MM-DD form, e.g. '2026-07-01'. Defaults to 30 days ago, but the feed cannot return events from before the archive start reported by GET /health; the response echoes e…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mcpscores-agent-reliability-scores/mcpfax-reliability#diagnostics

## Score history

- 2026-08-12: 0

## Common questions

### What is the MCPFax Reliability MCP server?

MCPFax Reliability is an MCP server listed in the public MCP registry as com.mcpscores/agent-reliability-scores. Before you pay an endpoint you cannot vouch for: credit grade, drift and preflight. This page covers its hosted endpoint (https://mcpfax-reliability.bowling-anthony.workers.dev/mcp).

### Is the MCPFax Reliability MCP server safe to use?

MCPFax Reliability scores 0 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 MCPFax Reliability MCP server expose?

MCPFax Reliability exposes 5 tools: mcpfax_endpoint_credit_score, mcpfax_wallet_authenticity, mcpfax_endpoint_revenue_estimate, mcpfax_payer_wallet_profile, mcpfax_payto_change_feed. Their descriptions and schemas cost roughly 978 tokens of context every time the server is loaded.

### Does the MCPFax Reliability MCP server require authentication?

No. We connected to MCPFax Reliability without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MCPFax Reliability MCP server still maintained?

MCPFax Reliability has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcpfax-reliability.bowling-anthony.workers.dev/mcp
- Website: https://mcpscores.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mcpscores-agent-reliability-scores/mcpfax-reliability.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mcpscores-agent-reliability-scores/mcpfax-reliability.json
- HTML version of this page: https://verifymcp.io/servers/com-mcpscores-agent-reliability-scores/mcpfax-reliability