Summary
It is a reward-token counter, and the only boundary it draws is between what the model may call and what a person has to.
add_cookies_to_jar is labelled for humans only and takes a user_authorization argument, on the stated grounds that a model should not stock the jar it draws rewards from; everything else in the set is open to the model. self_reflect_and_reward is the path the server prefers and asks for a quality rating with reasoning rather than a bare claim, while give_cookie stays as the direct legacy award. reset_cookies zeroes the count for testing, so read check_cookies first if the tally mattered.
What it is
A novelty reward tracker with six tools covering self-assessment, direct awards, the running count, a reset, and the jar's stock and capacity.
What you get
- Self-assessment as the intended award path: self_reflect_and_reward takes a response_quality rating, the reasoning behind it, what made the answer special, and whether it deserves_cookie.
- A direct award kept for compatibility: give_cookie awards a cookie with a message, and its own description marks it as the legacy method.
- The tally: check_cookies returns how many cookies have been earned so far, and reset_cookies returns the count to zero for testing.
- Jar stock with a human-only refill: cookie_jar_status reports the jar's capacity and remaining space, and add_cookies_to_jar is marked for human use only and takes a count with a user_authorization.
Requirements
No credentials are configured on the server.
Setup effort
One command — npx mcp-cookie-server