# Hunch (remote · mcp.checkyourhunch.com)

A calm second look on scam messages: paste a suspicious message, get the smallest safe next step.

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

## Components

- remote · `mcp.checkyourhunch.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/dekeloco-hunch/mcp.md), [page](https://verifymcp.io/servers/dekeloco-hunch/mcp)

## Channel facts

- Endpoint: `https://mcp.checkyourhunch.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.9.1`

## 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**: 71/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 364 tokens (~182/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**: 43/100
  - Stability observed for 13 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 2 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

Hunch is a hosted endpoint at https://mcp.checkyourhunch.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 dekeloco-hunch 'https://mcp.checkyourhunch.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dekeloco-hunch": {
      "url": "https://mcp.checkyourhunch.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dekeloco-hunch": {
      "type": "http",
      "url": "https://mcp.checkyourhunch.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dekeloco-hunch]
url = "https://mcp.checkyourhunch.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dekeloco-hunch --url 'https://mcp.checkyourhunch.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dekeloco-hunch:
    url: "https://mcp.checkyourhunch.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dekeloco-hunch": {
      "Transport": "http",
      "Url": "https://mcp.checkyourhunch.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dekeloco-hunch -t streamable-http -u 'https://mcp.checkyourhunch.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dekeloco-hunch": {
      "type": "http",
      "url": "https://mcp.checkyourhunch.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 74, +1)

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

### 2026-11-20 (score 73, 0)

- [functional] Server version: 3.9.16 → 3.9.17

### 2026-11-19 (score 73, +1)

- [functional] Server version: 3.9.15 → 3.9.16

### 2026-11-18 (score 72, 0)

- [functional] Server version: 3.9.13 → 3.9.15

### 2026-11-17 (score 72, +3)

- [security improvement] HSTS header: fail → pass
- [functional] Server version: 3.9.9 → 3.9.13

### 2026-11-16 (score 69, 0)

- [functional] Server version: 3.9.6 → 3.9.9

### 2026-11-15 (score 69, +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-11-14 (score 68, 0)

- [functional] Server version: 3.9.3 → 3.9.6

## MCP tools (2)

### `check_message` (~151 tokens)

Check a message

Paste or forward a suspicious message. Hunch reads only the words you give it, using the same engine as the Hunch extension and site (running on our server), and tells you in plain language what stands out and the smallest next step you can take. It never tells you a message is trustworthy and never calls anyone a scammer. Your text is analyzed, not stored.

Input parameters:

- `sender` (string): Optional: who it is from (email address or domain). If absent, Hunch says it cannot verify the sender.
- `subject` (string): Optional: the subject line, for emails.
- `text` (string, required): The message text to check (required). Paste the words, not a screenshot.

### `check_official_channel` (~146 tokens)

Check an official channel

Ask whether a phone number, domain, email, or app is a channel an organization publishes on its own site. Hunch answers only from a public-source list (facts taken from each organization's own pages, with a source link and date, not confirmed to Hunch): anything not on it is reported as 'not listed', never as 'unofficial'. Absence is never evidence against a channel.

Input parameters:

- `channel` (string): Optional: the specific channel to check (a domain, email, phone, or app). Omit to list the confirmed channels.
- `org` (string, required): The organization name to look up (required), e.g. a bank or a company.

## Diagnostics

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

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 67
- 2026-11-11: 67
- 2026-11-10: 67
- 2026-11-09: 66
- 2026-11-08: 66

## Common questions

### What is the Hunch MCP server?

Hunch is an MCP server listed in the public MCP registry as io.github.dekeloco/hunch. A calm second look on scam messages: paste a suspicious message, get the smallest safe next step. This page covers its hosted endpoint (https://mcp.checkyourhunch.com/mcp).

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

Hunch scores 74 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 Hunch MCP server expose?

Hunch exposes 2 tools: check_message, check_official_channel. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.

### Does the Hunch MCP server require authentication?

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

### Is the Hunch MCP server still maintained?

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

VerifyMCP ran 12 checks on Hunch, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Hunch: HTTPS. 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://mcp.checkyourhunch.com/mcp
- Website: https://checkyourhunch.com/ai-assistants
- Changelog RSS feed: https://verifymcp.io/servers/dekeloco-hunch/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dekeloco-hunch/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dekeloco-hunch/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dekeloco-hunch/mcp
