# 404KIN FIELD Transaction Intent (remote · field-404kin.cv5gyqnshz.chatgpt.site)

Token intent checks; no simulation/signing. Free trial ends 2026-09-25. No NFT required.

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

## Components

- remote · `field-404kin.cv5gyqnshz.chatgpt.site`: 69/100 (this document), [markdown](https://verifymcp.io/servers/site-chatgpt-cv5gyqnshz-field-404kin-transaction-intent/api-intent-check-mcp.md), [page](https://verifymcp.io/servers/site-chatgpt-cv5gyqnshz-field-404kin-transaction-intent/api-intent-check-mcp)

## Channel facts

- Endpoint: `https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/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-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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 (good).
  - Tool/resource definitions use about 182 tokens (~182/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 404KIN FIELD Transaction Intent MCP server?

404KIN FIELD Transaction Intent is a hosted endpoint at https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/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-cv5gyqnshz-field-404kin-transaction 'https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "site-chatgpt-cv5gyqnshz-field-404kin-transaction": {
      "url": "https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "site-chatgpt-cv5gyqnshz-field-404kin-transaction": {
      "type": "http",
      "url": "https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.site-chatgpt-cv5gyqnshz-field-404kin-transaction]
url = "https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-chatgpt-cv5gyqnshz-field-404kin-transaction": {
      "type": "remote",
      "url": "https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-chatgpt-cv5gyqnshz-field-404kin-transaction --url 'https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  site-chatgpt-cv5gyqnshz-field-404kin-transaction:
    url: "https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "site-chatgpt-cv5gyqnshz-field-404kin-transaction": {
      "Transport": "http",
      "Url": "https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add site-chatgpt-cv5gyqnshz-field-404kin-transaction -t streamable-http -u 'https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp'
```

### Other

```json
{
  "mcpServers": {
    "site-chatgpt-cv5gyqnshz-field-404kin-transaction": {
      "type": "http",
      "url": "https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/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-09-20 (score 69, +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-09-19 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 68)

First indexed and scored.

## MCP tools (1)

### `check_token_intent` (~135 tokens)

Compare token call with intended action

Compare supported static ERC20/ERC721/ERC1155 fields with INDEPENDENT caller expectations. Ethereum declaration only. Flags excessive allowances, wrong recipients and collection-wide approvals. Does not verify chain state, contract behavior or ownership, simulate, validate SeaDrop mint, sign or send. A matching report is not a safety verdict or execution permission. Public/synthetic inputs only. Free experiment ends 2026-09-25T03:00:00Z; no NFT required.

Input parameters:

- `chain_id` (integer, required)
- `expectations` (object, required)
- `token_standard` (string, required)
- `transaction` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/site-chatgpt-cv5gyqnshz-field-404kin-transaction-intent/api-intent-check-mcp#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68

## Common questions

### What is the 404KIN FIELD Transaction Intent MCP server?

404KIN FIELD Transaction Intent is an MCP server listed in the public MCP registry as site.chatgpt.cv5gyqnshz.field-404kin/transaction-intent. Token intent checks; no simulation/signing. Free trial ends 2026-09-25. No NFT required. This page covers its hosted endpoint (https://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp).

### Is the 404KIN FIELD Transaction Intent MCP server safe to use?

404KIN FIELD Transaction Intent 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 404KIN FIELD Transaction Intent MCP server expose?

404KIN FIELD Transaction Intent exposes 1 tool: check_token_intent. Their descriptions and schemas cost roughly 135 tokens of context every time the server is loaded.

### Does the 404KIN FIELD Transaction Intent MCP server require authentication?

No. We connected to 404KIN FIELD Transaction Intent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 404KIN FIELD Transaction Intent MCP server still maintained?

404KIN FIELD Transaction Intent is still listed as active in the MCP registry. We last reached this channel on 20 September 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://field-404kin.cv5gyqnshz.chatgpt.site/api/intent-check/mcp
- Website: https://field-404kin.cv5gyqnshz.chatgpt.site/agents/TOOLS.md
- Changelog RSS feed: https://verifymcp.io/servers/site-chatgpt-cv5gyqnshz-field-404kin-transaction-intent/api-intent-check-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-chatgpt-cv5gyqnshz-field-404kin-transaction-intent/api-intent-check-mcp.json
- HTML version of this page: https://verifymcp.io/servers/site-chatgpt-cv5gyqnshz-field-404kin-transaction-intent/api-intent-check-mcp