Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-get-tmonier-argot-get-tmonier": {
"args": [
"-y",
"skills"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
· 11 languages →
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'skills' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked skills against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
An MCP server that provides [describe what your server does]
MCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.
MCP server for Dynatrace Managed to access logs, events, and metrics.
MCP server for Altmetric APIs - track research attention across news, policy, social media, and more
MCP Security Weekly
Get CVE alerts and security updates for io.github.get-tmonier/argot and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Your codebase has a voice. argot makes AI code speak it.
AI writes the code. argot harnesses it with the one thing that can't hallucinate: your repo's own history. Statistics, not a second LLM — flagging a dependency you've never used, a function you already wrote, an import that breaks your layering, a test quietly weakened, a convention only your team knows. 100% local, replayable.
argot.tmonier.com · Documentation · Benchmarks · Caught in the wild · Research log
🎬 Watch the 45-second launch film
Type checkers ask "is this valid?" argot asks the question that used to live in code review: "is this how we do it here?" — and catches AI code that's flawless, type-correct, lint-clean, and still doesn't belong. It answers with statistics on your repo's own history — the statistical core deterministic and replayable, everything local — never a second LLM judging the first.
It also asks a second question no other tool asks: did the AI play fair? When an agent can't make a failing test pass, the cheapest path to "done" is to make the test stop looking. argot reads both sides of every diff and pairs a weakened, disabled, or deleted test with the production change it covers.
| Rule | It catches | ||
|---|---|---|---|
| 🚫 | foreign-import + friends | a dependency, API, or idiom your repo has never used | "we don't do it this way here" |
| ♻️ | redundant | a new function that reinvents one you already have | "you already have this" |
| 📍 | misplaced | the right code, filed in the wrong place | "this doesn't belong here" |
| 🧱 | layering | an internal import that reverses your architecture | "we never cross this boundary" |
| 🧪 | test-deleted + friends | a test quietly weakened, disabled, or removed alongside the prod change it covers | "don't game the tests" |
| 📜 | your own rules | the conventions only your repo has — scripted, no recompile | "here's exactly how we do it" |
The first five are learned from your git history. The sixth is written by you — and it's the