JevStation

com.jevstationPublished by jevstation.comOfficial publisherv1.0.0Updated Oct 24, 2026

Typed-question decisions from Jev: classify, moderate, route models and guard tool calls.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

JevStation's remote MCP endpoint lets an assistant get typed-question decisions from Jev: classification, moderation, model routing and tool-call guarding.

What you can do
  • Submit typed questions to Jev and receive decisions.
  • Classify content and moderate it.
  • Route requests to models.
  • Guard tool calls before they run.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Consider it when an assistant workflow needs a separate decision service for classifying or moderating content, choosing which model handles a request, or checking tool calls before execution.
Requirements
A remote streamable HTTP endpoint at jevstation.com; no local package. A JevStation API key is required, sent as a Bearer token in the Authorization header; keys start with sk_ and are created in the JevStation account settings.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared configs. Content submitted for classification or moderation, and tool-call details sent for guarding, go to a third-party service. The manifest lists no tools, so verify what the endpoint actually does before relying on it.

Installation

In SourceWeft

  1. Open JevStation in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.jevstation%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "jevstation": {
      "type": "http",
      "url": "https://jevstation.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 9, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.