MCP Servers
calllint/calllint
Pre-flight risk linting for MCP and agent tools — check the blast radius before your agent runs them.
Our verdict
We have not reviewed calllint/calllint yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About calllint/calllint
Calllint is a pre-flight risk linter for MCP and agent tools. It analyzes tools before execution to check their potential blast radius. It helps developers understand and mitigate dangerous operations early.
Best for
Developers building or deploying MCP servers and agent tools who want an early warning layer before executing tool calls.
Use cases
- Audit MCP tool permissions before allowing an agent to run them
- Identify destructive or high-risk operations in agent toolchains
- Add pre-flight tool checks to CI pipelines for agent projects
Notes
2 stars on GitHub. Last updated 2026-09-01. Licensed Apache-2.0.
Pros
- Small and focused on a specific safety gap
- Written in TypeScript, fitting common agent and MCP stacks
- Catch risky calls before they execute
Cons
- Very early project with only 2 stars, little community validation
- Limited scope, only covers MCP and agent tools
- Lacks evidence of production readiness or long-term maintenance
Key facts
What we have checked
- Days since the last commit
- 5
- GitHub forks
- 1
- GitHub stars
- 3
- Open issues
- 0
- Releases in the last 90 days
- 4
Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
npx calllint scan .cursor/mcp.jsonClients the listing names (not checked here)
Claude Desktop, Claude Code, Cursor, Windsurf, VS Code
Install
Add calllint/calllint to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --transport stdio calllint-calllint -- npx -y calllint-mcp@0.2.1Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"calllint-calllint": {
"command": "npx",
"args": [
"-y",
"calllint-mcp@0.2.1"
]
}
}
}Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"calllint-calllint": {
"command": "npx",
"args": [
"-y",
"calllint-mcp@0.2.1"
]
}
}
}VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"servers": {
"calllint-calllint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"calllint-mcp@0.2.1"
]
}
}
}Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.calllint-calllint]
command = "npx"
args = ["-y", "calllint-mcp@0.2.1"]- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What calllint/calllint connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.1Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.1Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.1Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.1Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 0.2.1Config checked | Codex docs |
Stars and usage
How calllint/calllint is growing
3 to 3
Health and security
Is calllint/calllint looked after, and what do its setup files show
Health score
75 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 30 of 30 | Last push 5 days ago |
| Releases | 15 of 15 | 4 releases in 90 days |
| Issue replies | Not counted | The latest check has no issue response reading (fewer than 3 measured issues, or issues switched off) |
| Maintainer | 15 of 15 | Owned by an organisation |
| Official source | 0 of 20 | Community server |
Sources
Where this comes from
- GitHubRegistry
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.