mcpcost

io.github.jmshinhwa/oracle-jdk-license-gate

@readystack/oracle-jdk-license-gate

Is the io.github.jmshinhwa/oracle-jdk-license-gate MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.

Finds the Java lines in your build that Oracle now bills for, and the free line that replaces each o

alive probed 2026-11-15 · unchanged since 2026-11-01

3tools
335tokens in Claude
0.2 %of Claude's 200k window
0.1×the median server
113 msto initialize
4 msto list tools
Run it
npx -y @readystack/oracle-jdk-license-gate@1.0.1 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
@readystack/oracle-jdk-license-gate 1.0.0
Capabilities
tools
Instructions
none
Of a 1M window
<0.1 % of a 1M context window
Count
335 tokens in Claude, exact, measured 2026-10-25. With the Claude Code prefix mcp__…__ on each tool name: 386. The o200k_base estimate is 190. Counted again when the tool definitions change. Method.
Repository
https://github.com/jmshinhwa/readystack-themes
Registry
active, updated 2026-09-23 · registry entry
Changes
2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.76×.

Tool≈ Claude tokenso200k estimateShare of this server
check_dir1347640 %
check_text1186735 %
check_file834725 %

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention license.

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-10-25 06:53alive104 ms3335190
2026-10-18 06:41alive113 ms3190

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher