io.github.scoutwyze-max/fips-mcp
ScoutWyze FIPS
Is the ScoutWyze FIPS MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.
Is this product version FIPS 140-3 validated, in NIST's queue, or expiring? From NIST CMVP data.
alive probed 2026-11-15 · unchanged since 2026-10-31
- Run it
- npx -y @scoutwyze/fips-mcp@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- scoutwyze-fips 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- 0.1 % of a 1M context window
- Count
- 1.1k tokens in Claude Opus 5.5, exact, measured 2026-10-17. With the Claude Code prefix mcp__…__ on each tool name: 1.2k. The o200k_base estimate is 656. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/scoutwyze-max/fips-mcp
- Website
- https://scoutwyze-fips.fly.dev
- Registry
- active, updated 2026-10-11 · 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.74×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| fips_lookup | 536 | 308 | 47 % |
| fips_batch | 327 | 188 | 29 % |
| fips_expiring | 151 | 87 | 13 % |
| fips_list_products | 127 | 73 | 11 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Scope (Legal) io.github.scope-bid/scope-mcp · alive
- io.github.scottmreed/ChemCP · alive
- ScoutScore io.github.scoutscore/scoutscore · crashed on start
- ScoutWyze Compute io.github.scoutwyze-max/compute-mcp · alive
- Scrape Everything io.github.scrapeeverything/mcp · needs env
- io.github.scrapercity/scrapercity-cli · crashed on start
- screenpipe io.github.screenpipe/screenpipe-mcp · alive
- BrowserMesh io.github.scrollDynasty/browsermesh · alive
Servers that mention fips.
- FIPS 140 certificate tracker com.808bits/fips-cmvp · alive
- Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS io.github.CyberMax-tools/batch-geocoder · alive
- Ziplore: US ZIP Code API (county, time zone, demographics, radius) io.github.CyberMax-tools/zip-data-api · alive
- Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS io.github.shawmena-dotcom/batch-geocoder · alive
- Ziplore: US ZIP Code API (county, time zone, demographics, radius) io.github.shawmena-dotcom/zip-data-api · alive
- Pinloft: Batch Geocoder — Address to Lat/Long + Census FIPS dev.workers.cybermax-tools.cybermax/pinloft · alive
- Ziplore: US ZIP Code API (county, time zone, demographics, radius) dev.workers.cybermax-tools.cybermax/ziplore · alive
- io.github.Lokeshwaranramu/quantaseal · 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.