# io.github.AlexanderLawson17/revettr-mcp (remote · revettr.com)

Counterparty risk scoring for agentic commerce via x402 micropayments.

- Trust score: 61/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `revettr.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/alexanderlawson17-revettr-mcp/revettr.md), [page](https://verifymcp.io/servers/alexanderlawson17-revettr-mcp/revettr)
- pypi · `revettr`: 36/100, [markdown](https://verifymcp.io/servers/alexanderlawson17-revettr-mcp/revettr-2.md), [page](https://verifymcp.io/servers/alexanderlawson17-revettr-mcp/revettr-2)

## Channel facts

- Endpoint: `https://revettr.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.3`

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

- **Endpoint Security**: 63/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 3 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 47/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 428 tokens (~142/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http alexanderlawson17-revettr-mcp https://revettr.com/mcp
```

### Codex

```toml
[mcp_servers.alexanderlawson17-revettr-mcp]
url = "https://revettr.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alexanderlawson17-revettr-mcp": {
      "type": "remote",
      "url": "https://revettr.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alexanderlawson17-revettr-mcp --url https://revettr.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  alexanderlawson17-revettr-mcp:
    url: "https://revettr.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "alexanderlawson17-revettr-mcp": {
      "type": "http",
      "url": "https://revettr.com/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-03 (score 61, +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-08-01 (score 60, +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-07-31 (score 59, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 55, +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-07-27 (score 54, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (3)

### `score_counterparty` (~83 tokens)

Score a counterparty before sending money. Returns risk score 0-100.

Accepts EVM wallets (0x...), Stellar wallets (G...), domains, IPs, and company names.

Input parameters:

- `chain` (string)
- `company_name`
- `domain`
- `ip`
- `stellar_wallet`
- `wallet_address`

### `verify_issuer` (~103 tokens)

Get an advisory risk verdict for a validated MCP issuer (iss).

Attach this at your MCP `iss` validation step: identity is your job, this
adds risk. Returns the same signed RiskCheckResult as POST /v1/iss-verdict.
Advisory and non-blocking — you decide based on the tier.

Input parameters:

- `chain` (string)
- `iss` (string, required)
- `iss_kind` (string)
- `wallet_address`

### `export_audit_bundle` (~186 tokens)

Export a JWS-signed audit-trail bundle of scoring decisions for a wallet.

MCP equivalent of GET /v1/audit/export. Compliance artifact for EU AI Act
Article 12 logging / NYDFS certification / debanking-defense. Because audit
data covers arbitrary wallets, this tool is operator-gated: pass the
operator's ``admin_token`` (checked against ``REVETTR_ADMIN_TOKEN``).
Disabled when that env var is unset. Note: ``admin_token`` travels in the
MCP request payload, so operators should treat MCP transcripts/logs as
sensitive. Verify the returned ``bundle_jws``
against /.well-known/jwks.json; the schema is in docs/audit-trail-export.md.

Input parameters:

- `admin_token` (string, required)
- `end`
- `start`
- `wallet_address` (string, required)

## Diagnostics

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

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 56
- 2026-07-29: 55
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 53

## Links

- Remote endpoint: https://revettr.com/mcp
- Repository: https://github.com/AlexanderLawson17/revettr-python
- Changelog RSS feed: https://verifymcp.io/servers/alexanderlawson17-revettr-mcp/revettr/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/alexanderlawson17-revettr-mcp/revettr/changelog.json
- HTML version of this page: https://verifymcp.io/servers/alexanderlawson17-revettr-mcp/revettr