io.github.nolindnaidoo/ids-le
IDs-LE
Is the IDs-LE MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.
Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside.
alive probed 2026-11-15 · unchanged since 2026-10-31
- Run it
- npx -y ids-le-mcp@1.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- ids-le 1.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 603 tokens in Claude Opus 5.5, exact, measured 2026-10-17. With the Claude Code prefix mcp__…__ on each tool name: 612. The o200k_base estimate is 373. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/nolindnaidoo/ids-le
- Website
- https://letools.dev/tools/ids-le
- Registry
- active, updated 2026-10-07 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.62×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| extract_ids | 603 | 373 | 100 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Dates-LE io.github.nolindnaidoo/dates-le · alive
- DecisionLint: Jev/Luna Lint io.github.nolindnaidoo/decisionlint · alive
- EnvSync-LE io.github.nolindnaidoo/envsync-le · alive
- i18n-LE io.github.nolindnaidoo/i18n-le · alive
- IPs-LE io.github.nolindnaidoo/ips-le · alive
- JevLint-LE io.github.nolindnaidoo/jevlint-le · alive
- Numbers-LE io.github.nolindnaidoo/numbers-le · alive
- Paths-LE io.github.nolindnaidoo/paths-le · alive
Servers that mention nolindnaidoo.
- Scrape-LE io.github.nolindnaidoo/scrape-le · alive
- Strings-LE io.github.nolindnaidoo/string-le · alive
- URLs-LE io.github.nolindnaidoo/urls-le · alive
- Secrets-LE io.github.nolindnaidoo/secrets-le · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
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
- The server answers initialize and tools/list. Nothing to fix.