Kunkafa

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.kunkafa/kunkafa and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 3 Oct 2026. Not supplied by the maker.

• list_markets

  Markets this account can read, each with the durations that have forecasts now, and what it follows. Page with page.nextCursor.

• get_outlooks

  Current 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 du

• get_performance

  How often past forecasts touched their target, by confidence level and period. Pass probabilityPercent for the matching row (headline).

• get_results

  Recent example forecasts with their outcomes; not a full record.

• get_usage

  Remaining allowances, what one get_outlooks call returns, and this connection's permissions, canFollow and expiry. Uses no allowance.

• follow_market

  Follow 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_market

  Stop following a market; its data stops being readable. Check canFollow in get_usage first.

• get_glossary

  What every Kunkafa term and number means and how to read them. Call once before explaining results. No sign-in needed.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.