tech.thecompound/openlookup
OpenLookup
Is the OpenLookup MCP server down? Yes. It has given no valid answer since 2026-10-18: not found.
OpenLookup: eleven keyless lookups. Model pricing, dep health, stack cost, registries.
not found down since 2026-10-18 · probed 2026-11-15 · unchanged since 2026-11-01
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y openlookup@0.5.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/kyisaiah47/openlookup
- Website
- https://thecompound.tech
- Registry
- active, updated 2026-10-02 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- CivicBinder MCP tech.thecompound/civicbinder · not found
- Compound Labs MCP tech.thecompound/compound-mcp · alive
- GoodStanding MCP tech.thecompound/goodstanding · not found
- KitGrade MCP tech.thecompound/kitgrade · not found
- tech.thecompound/parserail-mcp · not found
- RuleStack MCP tech.thecompound/rulestack · not found
- ScriptProbe MCP tech.thecompound/scriptprobe · not found
- SkillWorks MCP tech.thecompound/skillworks · not found
Servers that mention registries or keyless.
- ai.askmiles/catalog · alive
- ai.bidclub/bidclub · alive
- Builders in Fintech ai.buildersinfintech/fintech-data · alive
- ai.deskcrew/agentic · not found
- ai.duvera/gateway · alive
- ai.dynamicfeed/dynamic-feed · not found
- Last Price ai.last-price/pricing · alive
- RiskState — Crypto Risk Engine ai.riskstate/mcp · 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
- No valid answer since 2026-10-18, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.