Hunch MCP

A remote MCP server that analyzes suspicious messages to provide a calm second look, identifying red flags and suggesting the smallest safe next step without storing user data or requiring authentication.

Visit Hunch

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-08Published by Hunch

MCP endpoint (Streamable HTTP)

https://mcp.checkyourhunch.com/mcp

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 2 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 8, 2026, 8:45 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Check a suspicious message for scam indicators
Get a plain language finding on message safety
Receive a safe next step that avoids reused links

Source and maintenance

Community listingRegistry 3.9.1

mcp-registry: io.github.dekeloco/hunch@3.9.1 Project website

Protocol and capabilities

Server: hunch 3.9.1
MCP protocol negotiated in check: 2025-06-18
Tools: 2 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Use check_message to vet a suspicious message, and check_official_channel to check a channel against a public-source list of what organizations publish on their own sites (with source + date). Hunch advises, it never adjudicates, and anything not on the list is reported as "not listed", never "unofficial".

Tools

2 advertised

check_message — Check a message

Advertised by the server during the last successful anonymous check.

Advertised read-only

Paste or forward a suspicious message. Hunch reads only the words you give it, on one frozen engine (the same engine behind 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.

check_message input schema

{
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "The message text to check (required). Paste the words, not a screenshot."
    },
    "sender": {
      "type": "string",
      "description": "Optional: who it is from (email address or domain). If absent, Hunch says it cannot verify the sender."
    },
    "subject": {
      "type": "string",
      "description": "Optional: the subject line, for emails."
    }
  },
  "additionalProperties": false
}

check_message annotations

{
  "title": "Check a message",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

check_official_channel — Check an official channel

Advertised by the server during the last successful anonymous check.

Advertised read-only

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.

check_official_channel input schema

{
  "type": "object",
  "required": [
    "org"
  ],
  "properties": {
    "org": {
      "type": "string",
      "description": "The organization name to look up (required), e.g. a bank or a company."
    },
    "channel": {
      "type": "string",
      "description": "Optional: the specific channel to check (a domain, email, phone, or app). Omit to list the confirmed channels."
    }
  },
  "additionalProperties": false
}

check_official_channel annotations

{
  "title": "Check an official channel",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (4 of 4 answered).

2026-11-09: 2 of 2 checks answered
2026-11-10: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 413 ms
95th percentile latency: 413 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 8, 2026, 8:45 PM UTC · probe · passed · 413 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http hunch-mcp-checkyourhunch https://mcp.checkyourhunch.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add hunch-mcp-checkyourhunch --url https://mcp.checkyourhunch.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable hunch-mcp-checkyourhunch in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "hunch-mcp-checkyourhunch": {
      "type": "streamableHttp",
      "url": "https://mcp.checkyourhunch.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start hunch-mcp-checkyourhunch and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http hunch-mcp-checkyourhunch https://mcp.checkyourhunch.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://mcp.checkyourhunch.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "hunch-mcp-checkyourhunch": {
      "serverUrl": "https://mcp.checkyourhunch.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Hunch MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 6,154