# Xynthera AI — JSON invoice, OpenAPI and event checks (remote · pfxxzsnboehxsefyajml.supabase.co)

Signed deterministic checks for supplied JSON invoices, OpenAPI API contracts and JSON events.

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

## Components

- remote · `pfxxzsnboehxsefyajml.supabase.co`: 71/100 (this document), [markdown](https://verifymcp.io/servers/site-chatgpt-toasty-seal-8877-xynthera-ai-xynthera-ai-prepaid/functions-v1-xynthera-ai-payg-mcp-mcp.md), [page](https://verifymcp.io/servers/site-chatgpt-toasty-seal-8877-xynthera-ai-xynthera-ai-prepaid/functions-v1-xynthera-ai-payg-mcp-mcp)

## Channel facts

- Endpoint: `https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2026.10.14`

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

- **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 6 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**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 915 tokens (~152/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Xynthera AI — JSON invoice, OpenAPI and event checks MCP server?

Xynthera AI — JSON invoice, OpenAPI and event checks is a hosted endpoint at https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/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 site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe 'https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe": {
      "url": "https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe": {
      "type": "http",
      "url": "https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe]
url = "https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe": {
      "type": "remote",
      "url": "https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe --url 'https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe:
    url: "https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe": {
      "Transport": "http",
      "Url": "https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe -t streamable-http -u 'https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp'
```

### Other

```json
{
  "mcpServers": {
    "site-chatgpt-toasty-seal-8877-xynthera-ai-xynthe": {
      "type": "http",
      "url": "https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/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-03 (score 71, +1)

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

### 2026-11-01 (score 70, +1)

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

### 2026-10-30 (score 69, +1)

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

### 2026-10-28 (score 68, +1)

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

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

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

### 2026-10-24 (score 66, +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-10-22 (score 65, +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-19 (score 64, +1)

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

## MCP tools (6)

### `get_budget_status` (~85 tokens)

Read authenticated prepaid balance and state; free, with no debit. Before funding, the buyer manually purchases a budget at https://xynthera-ai.toasty-seal-8877.chatgpt.site/payg.html. Requires a private budget code in Authorization: Bearer; no OAuth. The initial purchase amount is the hard server-side total spending limit. No automatic recharge.

### `reconcile_invoice` (~120 tokens)

Paid EUR 0.005 excluding tax per new, successful signed invoice consistency check. Supply the entire documented JSON input and a stable unique request_id. Analysis of supplied data only, no bank validation. Exact same-body retries avoid a second debit; report reconstruction lasts 30 days, so retain reports.

Input parameters:

- `history` (array)
- `invoice` (object, required)
- `payments` (array)
- `purchase_order` (object)
- `receipts` (array)
- `request_id` (string, required)
- `supplier_profile` (object)

### `check_contract` (~137 tokens)

Paid EUR 0.010 excluding tax per new signed consistency report for a supplied OpenAPI JSON API contract only, with optional supplied offer/observation comparisons. No legal contract analysis, runtime endpoint testing, security audit or full OpenAPI standard certification. Identical request_id and body avoid a second debit. Report reconstruction is available for 30 days; save the original report. After that the request may be refused, never automatically retried with a new ID.

Input parameters:

- `document` (object, required)
- `observations` (array)
- `offer` (object)
- `published_offer` (object)
- `request_id` (string, required)

### `check_events` (~93 tokens)

Paid EUR 0.002 excluding tax per signed event batch of up to 200 supplied events, no actual delivery attestation. Identical request_id and body avoid a second debit. Report reconstruction lasts 30 days; retain the returned report. No automatic retries.

Input parameters:

- `events` (array, required)
- `request_id` (string, required)
- `require_contiguous` (boolean)
- `same_clock` (boolean)

### `effect_guard` (~123 tokens)

Guard one logical external effect. The prepare operation costs 390 micro-EUR excluding tax only when a new logical decision is successfully created; exact prepare replays and get/claim/settle/reconcile/cancel are free. This service grants one opaque execution authority but never performs the external action. Before settle, register the tenant-scoped ES256 outcome verifier described by the hosted OpenAPI. Reuse the same logical_identity and exact body after an unknown transport outcome; changed content conflicts. Keep claim capabilities private and never retry with a new identity merely because a response was lost.

### `spend_truth` (~145 tokens)

Create/read a resource budget and reserve or reconcile an agent action against it. A successful new reserve costs 290 micro-EUR excluding tax; exact reserve replays and create_budget/get_budget/get_reservation/begin/settle/release/mark_unknown/reconcile are free. Reservation is the only billable operation and performs no provider action. Each budget accepts at most 128 reservations; a 129th new logical reservation is rejected before billing. Before settle, register the tenant-scoped ES256 outcome verifier described by the hosted OpenAPI. Reuse logical_identity and the exact body after an unknown outcome; keep capabilities private and use the stable provider idempotency key returned by begin.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/site-chatgpt-toasty-seal-8877-xynthera-ai-xynthera-ai-prepaid/functions-v1-xynthera-ai-payg-mcp-mcp#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65
- 2026-10-22: 65
- 2026-10-21: 64
- 2026-10-20: 64
- 2026-10-19: 64
- 2026-10-18: 63
- 2026-10-17: 63
- 2026-10-16: 62
- 2026-10-15: 62
- 2026-10-14: 61

## Common questions

### What is the Xynthera AI — JSON invoice, OpenAPI and event checks MCP server?

Xynthera AI — JSON invoice, OpenAPI and event checks is an MCP server listed in the public MCP registry as site.chatgpt.toasty-seal-8877.xynthera-ai/xynthera-ai-prepa…. Signed deterministic checks for supplied JSON invoices, OpenAPI API contracts and JSON events. This page covers its hosted endpoint (https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp).

### Is the Xynthera AI — JSON invoice, OpenAPI and event checks MCP server safe to use?

Xynthera AI — JSON invoice, OpenAPI and event checks scores 71 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 Xynthera AI — JSON invoice, OpenAPI and event checks MCP server expose?

Xynthera AI — JSON invoice, OpenAPI and event checks exposes 6 tools: get_budget_status, reconcile_invoice, check_contract, check_events, effect_guard, spend_truth. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.

### Does the Xynthera AI — JSON invoice, OpenAPI and event checks MCP server require authentication?

No. We connected to Xynthera AI — JSON invoice, OpenAPI and event checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Xynthera AI — JSON invoice, OpenAPI and event checks MCP server still maintained?

Xynthera AI — JSON invoice, OpenAPI and event checks is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://pfxxzsnboehxsefyajml.supabase.co/functions/v1/xynthera-ai-payg-mcp/mcp
- Authorisation metadata: https://pfxxzsnboehxsefyajml.supabase.co/.well-known/oauth-protected-resource/functions/v1/xynthera-ai-payg-mcp/mcp
- Website: https://xynthera-ai.toasty-seal-8877.chatgpt.site/ai-connect.html
- Changelog RSS feed: https://verifymcp.io/servers/site-chatgpt-toasty-seal-8877-xynthera-ai-xynthera-ai-prepaid/functions-v1-xynthera-ai-payg-mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-chatgpt-toasty-seal-8877-xynthera-ai-xynthera-ai-prepaid/functions-v1-xynthera-ai-payg-mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/site-chatgpt-toasty-seal-8877-xynthera-ai-xynthera-ai-prepaid/functions-v1-xynthera-ai-payg-mcp-mcp