Hunch
REMOTE · HUNCHSHEET.APP · 3 COMPONENTS
Calibrated judgments for text: yes/no probabilities, picks from your options, or scores.
Available components
Last scanned (17 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 6 Nov 2026.
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2253 tokens (~281/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://hunchsheet.app/mcp/try
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.hunchsheet.app | CN=YR1,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | RSA 2048 | SHA256-RSA | 6d5e749223eb8f5fa2890c10b36794a132c |
| SANs: *.hunchsheet.app, hunchsheet.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hunchsheet.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| hunchsheet.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hunchsheet.app/mcp/try | Verified | 200 | |
| http (plaintext) | http://hunchsheet.app/mcp/try | HTTPS enforced | 308 | https://hunchsheet.app/mcp/try |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hunch_ask Hunch: yes/no probability ~332
Judge a batch of short texts against one yes/no question and get back a calibrated probability (0 to 1) per text, not generated prose. Use it to score, tag, filter or triage many leads, support tickets, reviews, survey answers or emails at once, for example "Is this lead a decision maker?" or "Is this email urgent?". Prefer it to judging the texts yourself once there are more than about 25: one call returns a number per text and keeps the texts out of your context. Costs 1 credit per answered text (blank texts and texts repeated elsewhere in the same call are free; the same text asked again in a later call is charged again). Limits: the model reads the text only, no math, counting or dates; English works best; put the full definition of what counts as yes inside the question, since the model sees nothing else.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Only for the keyless /mcp/try connection: a key from hunch_get_key or a purchase. Leave out to use the free sample. Ignored when the connection is already signed in. |
| question | string | yes | A yes/no question, e.g. "Is this lead a decision maker who can approve a purchase without asking someone else?". Put the full definition of yes/no in the question text. |
| texts | array | yes | Short texts to judge (leads, tickets, reviews, survey answers, emails, ...), one answer per text. Blank entries and texts repeated elsewhere in the same call cost nothing. Chunked internally into cal… |
| Name | Type | Req | Description |
|---|---|---|---|
| charged | integer | yes | Credits spent on this call. |
| checkout | object | – | Present when texts were skipped for lack of credits: a checkout link for the person to open (url, plan, price_usd, credits_added). |
| credits | integer | yes | Credits left on the key after this call. |
| results | array | yes | – |
| sample | boolean | – | True when the answers came from the keyless free sample, so credits is the sample rows left today. |
No examples provided.
hunch_balance Hunch: check credits ~123
Check how many Hunch credits are left on this key and how many have been used so far. Read-only, costs nothing. Call it before a large batch, or when a judging tool reports texts were skipped for lack of credits. On the keyless /mcp/try connection it reports the free sample rows left today.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Only for the keyless /mcp/try connection: a key from hunch_get_key or a purchase. Leave out to use the free sample. Ignored when the connection is already signed in. |
| Name | Type | Req | Description |
|---|---|---|---|
| credits | integer | yes | Credits left on the key. |
| used | integer | yes | Credits used on this key so far, lifetime. |
No examples provided.
hunch_buy_credits Hunch: get a checkout link ~198
Returns a link the person can open to buy more credits with a card on Stripe. Nothing is charged until they finish paying on that page; you cannot pay for them. Starter is $29 for 5,000 rows (a key's first purchase), Top-up is $19 for 25,000 rows on a key that already paid. Credits never expire and there is no subscription. Call it when a judging tool says the key is out of credits, or when hunch_quote says the job needs more than the key holds. Show the link to the person and let them decide.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Only for the keyless /mcp/try connection: a key from hunch_get_key or a purchase. Leave out to use the free sample. Ignored when the connection is already signed in. |
| plan | string | – | Optional. Defaults to Top-up when the key already paid, Starter otherwise. |
| Name | Type | Req | Description |
|---|---|---|---|
| applies_to | string | – | – |
| credits_added | integer | yes | – |
| expires_in_seconds | integer|null | – | – |
| plan | string | yes | – |
| price_usd | number | yes | – |
| url | string | yes | Checkout link for the person to open. |
No examples provided.
hunch_get_key Hunch: get a free 100-row key ~76
Returns a Hunch key with 100 free rows, in this response, with no email and no card. For the keyless /mcp/try connection: pass the key as api_key to the other tools (or reconnect with it). Limited to 2 keys per address per day. Treat the key like a password.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| credits | integer | yes | – |
| key | string | yes | A hunch_ key. Secret. |
No examples provided.
hunch_multi Hunch: several yes/no questions at once ~305
Ask up to 10 yes/no questions about the same batch of texts in one call, one probability per question per text, not generated prose. Use it when several judgments read the same text at once, for example "Can they buy?", "Are they angry?", "Is it urgent?" on the same support ticket, for a fraction of the tokens of separate calls. Prefer it to judging the texts yourself once there are more than about 25: one call returns a number per text and keeps the texts out of your context. Costs 1 credit per answered question per text (blanks and duplicate texts are free). Limits: the model reads the text only, no math, counting or dates, English works best, and each question needs its own definition of yes inside it.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Only for the keyless /mcp/try connection: a key from hunch_get_key or a purchase. Leave out to use the free sample. Ignored when the connection is already signed in. |
| questions | array | yes | Up to 10 yes/no questions, each answered once per text, e.g. ["Can they buy?", "Are they angry?", "Is it urgent?"]. |
| texts | array | yes | Short texts to judge (leads, tickets, reviews, survey answers, emails, ...), one answer per text. Blank entries and texts repeated elsewhere in the same call cost nothing. Chunked internally into cal… |
| Name | Type | Req | Description |
|---|---|---|---|
| charged | integer | yes | – |
| checkout | object | – | Present when texts were skipped for lack of credits: a checkout link for the person to open (url, plan, price_usd, credits_added). |
| credits | integer | yes | – |
| results | array | yes | – |
| sample | boolean | – | True when the answers came from the keyless free sample, so credits is the sample rows left today. |
No examples provided.
hunch_pick Hunch: pick one option ~353
Sort a batch of short texts into one of your own categories and get back the chosen option plus how confident the model is, not generated prose. Use it to route support tickets, classify feedback, or tag leads by type, for example options ["billing: invoices and charges", "refund", "bug", "other"]. Prefer it to judging the texts yourself once there are more than about 25: one call returns a number per text and keeps the texts out of your context. Costs 1 credit per answered text (blanks and duplicates in the same call are free). Limits: 2 to 255 options, each "label" or "label: description" to disambiguate a short label; the model reads the text only, no math, counting or dates, English works best.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Only for the keyless /mcp/try connection: a key from hunch_get_key or a purchase. Leave out to use the free sample. Ignored when the connection is already signed in. |
| options | array | yes | The options to choose from, 2 to 255 of them. Each is "label" or "label: description" when the label alone is ambiguous, e.g. "billing: invoices and charges". |
| question | string | – | Optional. What is being decided, e.g. "Which category does this ticket belong to?". Defaults to "Which option best describes this text?". |
| texts | array | yes | Short texts to judge (leads, tickets, reviews, survey answers, emails, ...), one answer per text. Blank entries and texts repeated elsewhere in the same call cost nothing. Chunked internally into cal… |
| Name | Type | Req | Description |
|---|---|---|---|
| charged | integer | yes | – |
| checkout | object | – | Present when texts were skipped for lack of credits: a checkout link for the person to open (url, plan, price_usd, credits_added). |
| credits | integer | yes | – |
| results | array | yes | – |
| sample | boolean | – | True when the answers came from the keyless free sample, so credits is the sample rows left today. |
No examples provided.
hunch_quote Hunch: price a job ~196
Free, no key needed. Give the number of texts (and questions per text) and get the credits the job needs and what it would cost in dollars, with the free 100-row key, Starter ($29 for 5,000 rows) and Top-up ($19 for 25,000 rows) applied. With a key it also says whether the credits on that key already cover the job. Call it before a large batch so you can tell the person the price first.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Only for the keyless /mcp/try connection: a key from hunch_get_key or a purchase. Leave out to use the free sample. Ignored when the connection is already signed in. |
| questions_per_text | integer | – | Yes/no questions per text for hunch_multi (one credit each). Leave out for the other tools. |
| rows | integer | yes | How many texts the job has. |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_left | integer | – | Credits on the key. Only with a key. |
| credits_needed | integer | yes | Rows times questions per row. |
| enough | boolean | yes | True when the credits on the key (or the free 100 rows, with no key) already cover the job. |
| purchase | object | – | Cheapest purchase that covers the gap: items (plan, quantity, credits, usd) and total_usd. |
| rows | integer | yes | – |
| summary | string | yes | – |
| to_buy_credits | integer | – | – |
No examples provided.
hunch_score Hunch: score on a scale ~345
Place a batch of short texts on your own ordered scale (2 to 10 levels, low to high) and get back a probability-weighted position, the most likely level, and confidence, not generated prose. Use it for sentiment ("angry|disappointed|neutral|happy|delighted"), fit scoring ("no fit|weak|good|perfect"), or any low-to-high rating. Prefer it to judging the texts yourself once there are more than about 25: one call returns a number per text and keeps the texts out of your context. Costs 1 credit per answered text (blanks and duplicates in the same call are free). Limits: the model reads the text only, no math, counting or dates, English works best, and the question should say what is being scored.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Only for the keyless /mcp/try connection: a key from hunch_get_key or a purchase. Leave out to use the free sample. Ignored when the connection is already signed in. |
| levels | array | yes | The scale, low to high, 2 to 10 levels, e.g. ["angry", "disappointed", "neutral", "happy", "delighted"]. Each may be "label: description". |
| question | string | yes | What is being scored, e.g. "How does the reviewer feel about the product overall?". |
| texts | array | yes | Short texts to judge (leads, tickets, reviews, survey answers, emails, ...), one answer per text. Blank entries and texts repeated elsewhere in the same call cost nothing. Chunked internally into cal… |
| Name | Type | Req | Description |
|---|---|---|---|
| charged | integer | yes | – |
| checkout | object | – | Present when texts were skipped for lack of credits: a checkout link for the person to open (url, plan, price_usd, credits_added). |
| credits | integer | yes | – |
| results | array | yes | – |
| sample | boolean | – | True when the answers came from the keyless free sample, so credits is the sample rows left today. |
No examples provided.
How do I install the Hunch MCP server?
Hunch is a hosted endpoint at https://hunchsheet.app/mcp/try, 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.
remote · hunchsheet.app
claude mcp add --transport http app-hunchsheet-hunch 'https://hunchsheet.app/mcp/try'
What is the Hunch MCP server?
Hunch is an MCP server listed in the public MCP registry as app.hunchsheet/hunch. Calibrated judgments for text: yes/no probabilities, picks from your options, or scores. This page covers its hosted endpoint (https://hunchsheet.app/mcp/try).
Is the Hunch MCP server safe to use?
Hunch scores 86 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 8 tools: hunch_ask, hunch_pick, hunch_score, hunch_multi, hunch_balance, and 3 more. Their descriptions and schemas cost roughly 1,928 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 6 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 13 checks on Hunch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.