DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to serve the three Jev tools to a non-DSH MCP host with Jevcore

Run the jevcore-mcp stdio server so any MCP host can call the jev_ask, jev_rank, and related tools.

Who it is forA developer whose MCP host is not DeepSeek Harness and who wants typed Jev judgments as tools.

The problemStdout is the protocol channel on stdio, so a stray log line can break the connection, and a missing key can go unnoticed.

The outcomeThe host lists the Jev tools, and the egress report appears on stderr while the protocol stays clean.

What you need first

  • Node 20 or later for jevcore and jevcore-mcp, or Node ^22.19.0 or >=24.0.0 for jevcore-dsh
  • A local checkout of the repo for the DeepSeek Harness install path
  • DeepSeek Harness, if you use the plugin or the gates
  • A TypeSafe or OpenRouter key only if you choose a live route; the default is the offline mock

Steps

  1. Run npx -y jevcore-mcp once from a terminal to check that the server starts.
  2. Read the egress report on stderr and confirm it names provider=mock and egress=OFF when no key is set.
  3. Add a server entry to your MCP host that spawns the command npx with args -y and jevcore-mcp.
  4. If you set JEV_PROVIDER=live, make sure the matching key is present, because a missing key is a startup error for this server.

Prompt for your agent

In the PerryLink/jevcore repo, start the jevcore-mcp stdio server with npx -y jevcore-mcp and register it with <MCP host config file>. Expected output: the host lists the three Jev tools. Verify that the egress report appears on stderr and that nothing else prints to stdout before the host connects.

Caveat. With no key the server stays on the offline mock without an error, so a host that appears to work may not be calling Jev at all until a key is set.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page