Read-only semantic filtering, code search, log triage and traceable evidence for AI agents.
Connect Runs on your machine
claude mcp add jev-filter -e TYPESAFE_API_KEY=<TYPESAFE_API_KEY> -- npx -y @apixly/[email protected]{
"mcpServers": {
"jev-filter": {
"command": "npx",
"args": [
"-y",
"@apixly/[email protected]"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}{
"mcpServers": {
"jev-filter": {
"command": "npx",
"args": [
"-y",
"@apixly/[email protected]"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}{
"servers": {
"jev-filter": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@apixly/[email protected]"
],
"env": {
"TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
TYPESAFE_API_KEYRequired, secret | Your TypeSafe Jev API key. Inference calls are billable; do not publish the key. |
Details
| Package | @apixly/[email protected] (NPM, stdio) |
| First published | 23 Oct 2026 |
| Last updated | 23 Oct 2026 |
| Registry name | io.github.apixly-ai/jev-filter |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.