
Kunkafa MCP server
Which servers in the official MCP registry are Kunkafa's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.kunkafa/kunkafaverified in the MCP registry
The registry name sits under kunkafa.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools9
- Server calls itselfKunkafa
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 246 ms.
- Its tools do every use case we checked: Check the chance a market rises or falls by a set amount; Compare forecast odds across durations from an hour to two years; Read forecast bands for S&P 500, Nasdaq 100 and gold.
- Checked on 3 of the 7 days it takes to judge reliability.
Once connected
- For "Check the chance a market rises or falls by a set amount", the likely first call is get_outlooks.
- For "Read forecast bands for S&P 500, Nasdaq 100 and gold", the likely first call is list_markets.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- What an agent can do with it3 of 3 use cases
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer463 ms
- Space in an agent's context≈ 1,555 tokensthe definitions of all its tools (9), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results9 of 9 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · Check the chance a market rises or falls by a set amount
- can do · Compare forecast odds across durations from an hour to two years
- can do · Read forecast bands for S&P 500, Nasdaq 100 and gold
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_marketsMarkets this account can read, each with the durations that have forecasts now, and what it follows. Page with page.nextCursor.
get_outlooksCurrent forecasts for one market; one market per call by design, so data is not pulled in bulk. Choose durations (exact or a range) and optionally direction, confidence or target filters. At most 6 durations and 72 forecasts per call…
get_performanceHow often past forecasts touched their target, by confidence level and period. Pass probabilityPercent for the matching row (headline).
get_resultsRecent example forecasts with their outcomes; not a full record.
get_usageRemaining allowances, what one get_outlooks call returns, and this connection's permissions, canFollow and expiry. Uses no allowance.
follow_marketFollow a market for this account. Check canFollow in get_usage first. Replacing a followed market is allowed once every 30 days: ask the user, then call with confirmReplacement true.
unfollow_marketStop following a market; its data stops being readable. Check canFollow in get_usage first.
get_glossaryWhat every Kunkafa term and number means and how to read them. Call once before explaining results. No sign-in needed.
get_account_linksLinks to create an account, sign in and manage connections.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"kunkafa": {
"type": "http",
"url": "https://kunkafa.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http kunkafa https://kunkafa.com/mcpclaude.ai, ChatGPT and other clients: add https://kunkafa.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.