mcpbeat Sign in

Kodem MCP Server

by kodemsecurity Your server? Claim it
answering

Kodem is answering right now. Last checked 10 min ago.

Ask about your Kodem Security data and act on findings in plain language, with your permissions.

Uptime history 10 days of history
10 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
450 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Kodem every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add kodem --transport http https://api.kodemsecurity.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "kodem": {
      "url": "https://api.kodemsecurity.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.kodem]
url = "https://api.kodemsecurity.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "kodem": {
      "url": "https://api.kodemsecurity.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "kodem": {
      "url": "https://api.kodemsecurity.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.kodemsecurity.com/mcp streamable-http sign-in 480 ms 10 min ago

Alternatives to Kodem

same job, measured the same way
Envibe
by dominic-righthere

Secure permission layer between AI agents and your .env files

48 installs/wk local only
GitHub Actions Security Audit
by tylerscomic-lab

Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.

answering
Snyk
by snyk

Easily find and fix security issues in your applications leveraging Snyk platform capabilities.

671 447 installs/wk local only
Eleion Scanner
by hernaninverso

Register/verify your domains, queue security scans, and read findings (CVE, severity).

29 installs/wk local only
GitHub Actions Audit
by unbearabledev

GitHub Actions workflow security audit - 21 checks: pinning, permissions, secrets, injection.

answering
BT Ops MCP
by tangchangzhe

Secure MCP server for BT Panel operations with scoped permissions and audited writes.

39 installs/wk local only
Trusteed
by trusteed-io

CTEM for your Trusteed tenant: security summary, findings, compliance gaps, and scans via OAuth.

answering
Fulcra
by fulcradynamics

Use your Fulcra secure context lake to collaborate with other agents, read and write data, and more

1 900 installs/wk answering

Kodem — questions

Answers built from our own checks of this server.

Why is there no tool list for Kodem?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Kodem working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 450 ms. The bar chart above shows every period we have measured.
How do I connect Kodem?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Kodem?
No API key is involved. Kodem answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Kodem?
It answers our handshake in 450 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.