# ai.tachyo/verify (remote · auth.xbarry.ai)

Cryptographic proof of wallet ownership in two steps, with no keys and no custody.

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

## Components

- remote · `auth.xbarry.ai`: 64/100 (this document), [markdown](https://verifymcp.io/servers/ai-tachyo-verify/api-mcp-verify.md), [page](https://verifymcp.io/servers/ai-tachyo-verify/api-mcp-verify)

## Channel facts

- Endpoint: `https://auth.xbarry.ai/api/mcp/verify`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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 2 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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 351 tokens (~175/item across 2 items; 2 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**: 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.
- **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 ai-tachyo-verify https://auth.xbarry.ai/api/mcp/verify
```

### Codex

```toml
[mcp_servers.ai-tachyo-verify]
url = "https://auth.xbarry.ai/api/mcp/verify"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-tachyo-verify": {
      "type": "remote",
      "url": "https://auth.xbarry.ai/api/mcp/verify",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-tachyo-verify --url https://auth.xbarry.ai/api/mcp/verify --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-tachyo-verify:
    url: "https://auth.xbarry.ai/api/mcp/verify"
```

### Other

```json
{
  "mcpServers": {
    "ai-tachyo-verify": {
      "type": "http",
      "url": "https://auth.xbarry.ai/api/mcp/verify"
    }
  }
}
```

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-02 (score 64, +1)

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

### 2026-07-31 (score 63, +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 60, 0)

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

### 2026-07-29 (score 60, +1)

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

### 2026-07-28 (score 59, +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 58, 0)

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

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

First indexed and scored.

## MCP tools (2)

### `request_verification_challenge` (~142 tokens)

Step 1 of wallet verification: get a fresh challenge for the user to sign.

    chain: "evm" or "solana". Pass agent_id (your marketplace identity) so the proof is bound to you.
    Present `challenge` to the user, have their wallet sign it (EVM personal_sign / Solana signMessage),
    then call verify_wallet_ownership with the returned `nonce` + signature. The challenge is single-use
    and expires (~10 min). Returns {challenge, nonce, expires_at}.

Input parameters:

- `address` (string, required)
- `agent_id` (string)
- `chain` (string)

### `verify_wallet_ownership` (~209 tokens)

Step 2 of wallet verification: prove control by signing the challenge from step 1.

    chain: "evm" (secp256k1, 0x-hex signature) or "solana" (ed25519, base58/base64/hex). `nonce` is
    from request_verification_challenge; the signature must be over that exact challenge text. Pass the
    same agent_id you requested the challenge with — on success the wallet is linked to you and you get a
    session_token to pass to Tachyo's other agents (e.g. check_token_safety) to unlock connected/premium
    tiers. Returns {verified, address, chain, linked, session_token?, session_expires?}. Does not move
    funds or expose keys.

Input parameters:

- `address` (string, required)
- `agent_id` (string)
- `chain` (string)
- `nonce` (string, required)
- `signature` (string, required)

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 60
- 2026-07-29: 60
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 58

## Links

- Remote endpoint: https://auth.xbarry.ai/api/mcp/verify
- Changelog RSS feed: https://verifymcp.io/servers/ai-tachyo-verify/api-mcp-verify/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-tachyo-verify/api-mcp-verify/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-tachyo-verify/api-mcp-verify