# Stake (remote · stake.clawhard.com)

Is the domain free? Live registry (RDAP) checks across .com .io .ai .dev, with expiry and registrar.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `stake.clawhard.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-clawhard-stake/stake.md), [page](https://verifymcp.io/servers/com-clawhard-stake/stake)

## Channel facts

- Endpoint: `https://stake.clawhard.com/mcp`
- 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-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**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 757 tokens (~252/item across 3 items; 1 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Stake MCP server?

Stake is a hosted endpoint at https://stake.clawhard.com/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-clawhard-stake 'https://stake.clawhard.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-clawhard-stake": {
      "url": "https://stake.clawhard.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-clawhard-stake": {
      "type": "http",
      "url": "https://stake.clawhard.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-clawhard-stake]
url = "https://stake.clawhard.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-clawhard-stake --url 'https://stake.clawhard.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-clawhard-stake:
    url: "https://stake.clawhard.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-clawhard-stake": {
      "Transport": "http",
      "Url": "https://stake.clawhard.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-clawhard-stake -t streamable-http -u 'https://stake.clawhard.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-clawhard-stake": {
      "type": "http",
      "url": "https://stake.clawhard.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-11-21 (score 69, +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.

### 2026-11-19 (score 68, +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-11-17 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 66)

First indexed and scored.

## MCP tools (1)

### `stake_check_domains` (~562 tokens)

Check whether domain names are available to register (live registry lookup)

Use when the user asks whether a domain is available or taken, wants product, startup, app or project name ideas with a free domain, or is about to put a domain into a plan, README, config or launch post (signals: "is the .com taken", "domain available", "name ideas with a .com", "which of these names has a free domain", ".io or .ai", "who owns this domain", "when does it expire"). Asks each ending's own registry through RDAP (the official successor to WHOIS; IANA's server list plus the registries of .io, .me, .sh, .ac, .us, .so, .de, .ch that are not in it), and returns per domain: available, registered, registered_expiring (redemption or pending delete), likely_available (DNS only: for endings with no public RDAP such as .co, .gg, .eu, .it, or when a registry's RDAP server refuses or rate-limits the check), unknown or invalid; for taken names the registration and expiry dates, days to expiry, registrar, status codes and nameservers, and a flag when the nameservers belong to a parking or domain-marketplace service (Afternic, Dan.com, Sedo, Atom and others: the owner may sell it). Pass full domains, or names plus endings: {"names":["tidewell","brightloop"],"tlds":["com","io","ai"]} or {"domains":["tidewell.com","münchen.de","foo.co.uk"]}. Default endings when only names are given: com, io, ai, dev, app, co, net, org. Up to 20 domains per call. Call it before presenting name ideas as available instead of guessing. Cannot see prices, premium or reserved status, trademarks, or social handles; "available" is not a reservation.

Input parameters:

- `domains` (array): Full domain names to check, e.g. ["tidewell.com", "tidewell.io"]. International names (münchen.de) and suffixes such as co.uk are fine; a URL or subdomain is reduced to the registrable domain. Up to…
- `names` (array): Bare names without an ending, e.g. ["tidewell"]; each is checked with every entry in tlds. Up to 10 names (and 20 domains in total).
- `tlds` (array): Endings to try with names, e.g. ["com","io","ai","dev"] (a leading dot is fine; co.uk works). Default: com, io, ai, dev, app, co, net, org.

## Diagnostics

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

## Score history

- 2026-11-21: 69
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 66

## Common questions

### What is the Stake MCP server?

Stake is an MCP server listed in the public MCP registry as com.clawhard/stake. Is the domain free? Live registry (RDAP) checks across .com .io .ai .dev, with expiry and registrar. This page covers its hosted endpoint (https://stake.clawhard.com/mcp).

### Is the Stake MCP server safe to use?

Stake scores 69 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 Stake MCP server expose?

Stake exposes 1 tool: stake_check_domains. Their descriptions and schemas cost roughly 562 tokens of context every time the server is loaded.

### Does the Stake MCP server require authentication?

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

### Is the Stake MCP server still maintained?

Stake 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 Stake MCP server?

VerifyMCP ran 14 checks on Stake, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://stake.clawhard.com/mcp
- Website: https://stake.clawhard.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-clawhard-stake/stake.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-clawhard-stake/stake/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-clawhard-stake/stake.json
- HTML version of this page: https://verifymcp.io/servers/com-clawhard-stake/stake
