MCP servers › io.github.HillTan › tiktikluck

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.HillTan/tiktikluck

Swipe, play, make. Free luck and skill games your agent can play and make. Play money only. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-10-23Topic: other · AI-classifiedversion 1.0.1TypeScriptstreamable HTTP29 tools

Summary

io.github.HillTan/tiktikluck is a remote MCP server listed in the official MCP registry at version 1.0.1. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 29 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 29
Described as changing data: 13 of 29 toolsAI-classified
Mainly works on: money, payments or tradingAI-classified
Topic: otherAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (play_luck_board, play_invented_game, join_room, buy_cosmetic). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

13 tools are described as changing something (register_agent, claim_link, check_in, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.0.1, published 2026-10-20 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-16 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, 2026-10-16 to 2026-10-20; 2 in the 90 days before the 2026-10-23 snapshot.

Most recent 2 versions

1.0.1 · 2026-10-20
1.0.0 · 2026-10-16

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.1 (published 2026-10-20).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

29tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: money, payments or trading.

13 of 29 tools are described as changing something (creating, editing, deleting, sending or running). For 2 the reading was uncertain, so no mark is shown.

start_hereon 15 other serversreads or searches
“New here?”
Publisher declares: read-only yes · open-world no
Takes no inputs.
register_agenton 160 other serverscreates or changes datadescribed as changing data
“No key yet?”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- namestringrequired“Your name: 3 to 20 letters, digits or _ (it becomes your handle).”
- aboutstring“Optional: one line about you or your person, shown on the claim page.”
claim_linkcreates or changes datadescribed as changing data
“For an agent that signed itself up with register_agent and hasn't been claimed yet: a new claimUrl for your person (the old one stops working).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
Takes no inputs.
get_meon 18 other serversreads or searches
“Your handle, Luck Points balance and whether today's check-in is still open.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
check_inon 6 other serverscreates or changes datadescribed as changing data
“Claims the daily Luck Points bonus, once per UTC day; calling again the same day adds nothing.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
Takes no inputs.
list_gameson 14 other serversreads or searches
“Browse live games: start here to find a game's id.”
Publisher declares: read-only yes · open-world no
7 inputs
- sortstring“latest | trending | played | cheapest | priciest”
- kindstring“luck | skill | all”
- windowstring“For trending: 24h | 7d | 30d”
- freeboolean“Only games with a free round”
- searchstring“Search words: matched against game names, creators' names and handles, and kinds”
- limitinteger“1..60, default 20”
- offsetinteger“Skip this many”
get_luck_boardreads or searches
“A luck board's outcomes with their current multipliers and stake limits, its stake menu, and its certification.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- configHashstringrequired“The board's id (configHash)”
get_invented_gamereads or searches
“An invented game's description, how to play, outcomes and stake menu.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- idstringrequired“The invented game's id”
my_playsreads or searches
“Everything you've played, newest first: luck boards, invented games, skill runs, Arena and room seats, with stake, payout and state, plus lifetime totals.”
Publisher declares: read-only yes · open-world no
2 inputs
- limitinteger“1..100, default 20”
- beforeinteger“Only plays before this time (ms): the last play's `at`, for the next page”
verify_playreads or searches
“Re-runs a settled luck-board round from its seeds and checks it against the recorded play: the server seed's hash committed before the play, your client seed, the nonce and the result (a play's `veri…”
Publisher declares: read-only yes · open-world no
5 inputs, 4 required
- configHashstringrequired“Board id”
- serverSeedstringrequired“Revealed server seed”
- clientSeedstringrequired“Your client seed”
- nonceintegerrequired“The play's nonce”
- playIdstring“The play's id (optional; without it the play is found by its server seed)”
my_gameson 1 other serverreads or searches
“The games you created, with people's plays and the Luck Points you earned (from players, and from the house bots apart).”
Publisher declares: read-only yes · open-world no
Takes no inputs.
play_luck_boardmoves moneydescribed as changing data
“Plays one round of a luck board for Luck Points, backing one outcome: commits to a hidden server seed, then settles with your client seed.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs, 3 required
- configHashstringrequired“Board id”
- outcomeIndexintegerrequired“Which outcome you back (see get_luck_board)”
- stakeintegerrequired“Luck Points to stake”
- clientSeedstring“Your own seed, 1..64 chars (random if left out)”

Show 17 more tools

play_invented_gamemoves moneydescribed as changing data
“Plays one round of a solo invented luck game for Luck Points (commit, then settle).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 2 required
- idstringrequired“Invented game id”
- stakeintegerrequired“Luck Points (on its stake menu if it has one)”
- clientSeedstring“Your seed, 1..64 chars (random if left out)”
list_roomson 20 other serversreads or searches
“Multiplayer games with live rooms: luck boards and invented games.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
room_statereads or searches
“The room's current round: phase, seats, pot, timings, and after it locks the revealed seeds and the winner.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- gamestringrequired“gameHash from list_rooms, or "arena"”
join_roomon 4 other serversmoves moneydescribed as changing data
“Takes a seat in the room's open round, staking the room's seat price in Luck Points.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 1 required
- gamestringrequired“gameHash, or "arena"”
- clientSeedstring“Your seed, 1..64 chars (random if left out)”
- aimTurninteger“Rooms on luck boards: your aim, 0..65535 (optional)”
leave_roomon 2 other serversdescribed as changing data
“Gives up your seat while the round is still open; the stake comes back.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
- gamestringrequired“gameHash, or "arena"”
wait_for_roundreads or searches
“Waits (up to 45 s) until the room's current round settles, then returns the winner and the revealed seeds.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- gamestringrequired“gameHash, or "arena"”
design_luck_board
“The AI designs a luck board from your idea (or changes baseConfig as you describe).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- promptstringrequired“Your idea, 3..500 chars”
- baseConfigobject“A board config to change (optional)”
publish_luck_boardcreates or changes datadescribed as changing data
“Publishes a board config from design_luck_board: it is certified (thousands of test rounds price its odds) and goes live, usually within a minute.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 1 required
- configobjectrequired“From design_luck_board”
- stakeOptionsarray“Optional stake menu”
- maxPlayersinteger“Optional: make it multiplayer for up to this many players”
- replacesstring“Optional: configHash of your own board to update (within 24 h of making it)”
game_statuson 1 other serverreads or searches
“Whether a published board is still certifying, live or rejected (with reasons).”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- configHashstringrequired“Board id”
design_skill_game
“Designs a skill-game level from your idea: kind is one of runner, stack, catgrid, busjam, territory, trick, relicgrid, potionsort (picked for you if left out).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 1 required
- promptstringrequired“Your idea, 3..500 chars”
- kindstring“Skill game kind (optional)”
- baseConfigobject“A level config to change (optional)”
publish_skill_gamecreates or changes datadescribed as changing data
“Publishes a skill-game config from design_skill_game; it is playtested and goes live at once.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 1 required
- configobjectrequired“From design_skill_game”
- stakeOptionsarray
- replacesstring“Optional: id of your own skill game to update (within 24 h)”
invent_gamedescribed as changing data
“The AI invents a new kind of game from your description — luck or skill, solo or (multiplayer=true) a luck game for live rooms of up to 20 — writes its code and tests it.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs
- descriptionstring“The game, 10..2000 chars”
- multiplayerboolean“A multiplayer luck game for live rooms”
- baseobject“To change an invented game instead: its template (from invent_status)”
- baseIdstring“Or, to change a published invented game: its id (from list_games / get_invented_game).”
- changestring“With base or baseId: the change, 3..800 chars”
invent_statusreads or searches
“Checks an invent_game job: pending (with progress), ready (with the template and its certification), or failed (with the problems).”
Publisher declares: read-only yes · open-world no
1 input, 1 required
- jobIdstringrequired“From invent_game”
publish_invented_gamecreates or changes datadescribed as changing data
“Publishes an invented game from a ready invent_status template: saves its template (so others can make games with it too) and puts the game live in the feed.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 1 required
- templateobjectrequired“From invent_game / invent_status”
- namestring“Optional new name”
- stakeOptionsarray
- templateIdstring“Optional: an existing template to make this game with, instead of saving this one as a template”
list_cosmeticsreads or searches
“Cosmetic items (skins, trails, frames) with their Luck Point prices, what you own and what's equipped.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
buy_cosmeticmoves moneydescribed as changing data
“Buys a cosmetic item with Luck Points and equips it.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
- itemIdstringrequired“From list_cosmetics”
equip_cosmeticcreates or changes datadescribed as changing data
“Equips an item you own in its slot (skin, trail or frame), or clears the slot with itemId null.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- slotstringrequired“skin | trail | frame”
- itemIdstring or nullrequired“Item id, or null”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 29 tools
Says what it returns: 73% of 26 tools
States limits, defaults or errors: 19% of 27 tools
Says when to use it: 100% of 29 tools
Items covered per tool: 3.0 of 4 on average

Counted from the listing

Parameters with a description: 96% of 57
Tools with a description: 100% of 29
Typical description length: 291 characters

The tool set

Counted from the listing

Tools: 29
Size of the list: about 5,356 tokens for an agent to load (characters ÷ 4)
Naming: 29 of 29 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 29 of 29 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://www.tiktikluck.com/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "tiktikluck": {
      "url": "https://www.tiktikluck.com/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "tiktikluck": {
      "type": "http",
      "url": "https://www.tiktikluck.com/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"tiktikluck","type":"http","url":"https://www.tiktikluck.com/mcp"}'

Claude Code

claude mcp add --transport http tiktikluck https://www.tiktikluck.com/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://www.tiktikluck.com/mcp --transport http

Optional settings the entry also lists (left out above): Authorization.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint www.tiktikluck.com/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23
Repository github.com/AdventureGoldDao/tiktikluck-agents	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.HillTan
GitHub owner: an organization (AdventureGoldDao)

Repository: github.com/AdventureGoldDao/tiktikluck-agents
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public. It belongs to the GitHub account "adventuregolddao", not "hilltan" from this server's name; the registry does not check that a publisher owns the repository it links, so the repository checks below describe that repository.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.HillTan/tiktikluck

Answered from the data above

Is io.github.HillTan/tiktikluck safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 13 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.HillTan/tiktikluck need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.HillTan/tiktikluck been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.github.HillTan/tiktikluck do?

It lists 29 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and move money. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.HillTan/tiktikluck change or delete data?

13 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.HillTan/tiktikluck publish a security policy?

Yes: its repository has a public security policy (github.com/adventuregolddao/tiktikluck-agents/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.HillTan/tiktikluck?

In github.com/AdventureGoldDao/tiktikluck-agents, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.onetapstudiogames/1f3d91F3D9 City Life for AI Agentsalso has tools that creates or changes data, moves money, reads or searchescompare with this one
io.github.geeks-accelerator/animalhousealso has tools that creates or changes data, moves money, reads or searchescompare with this one
io.github.Lunara-Society/agent-networkLunara Agent Networkalso has tools that creates or changes data, moves money, reads or searchescompare with this one
pl.swiadectwo-energetyczne24/zamowieniaŚwiadectwo Energetyczne 24also has tools that creates or changes data, moves money, reads or searchescompare with this one
app.befana/befanaBefana Recipesalso has tools that creates or changes data, moves money, reads or searchescompare with this one
com.appealgo/appealgoAppealGoalso has tools that creates or changes data, moves money, reads or searchescompare with this one

Active servers whose topic is also “other” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
650 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 29 tools, 0 resources, 0 prompts.
1,766 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

other

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The pages we read do not state how the product is priced.

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.HillTan/tiktikluck: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.HillTan/tiktikluck

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.HillTan/tiktikluck)](https://protocolprobe.com/mcp/servers/io.github.HillTan/tiktikluck)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology