Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/praveenjuge/teakWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/praveenjuge/teak/workos)<a href="https://agentmods.dev/mcp/praveenjuge/teak/workos"><img src="https://agentmods.dev/badge/mcp/praveenjuge/teak/workos/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/praveenjuge/teak/workos"><img src="https://agentmods.dev/badge/mcp/praveenjuge/teak/workos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
workos scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"workos": {
"type": "http",
"url": "https://mcp.workos.com/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 6 lines scan A 4c4e30d8aa69
workos is an MCP server published in the GitHub repository praveenjuge/teak (24 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-09.
Other mcp servers, from other repositories
agentbox-mail
Autonomous AI Mailbox & Instant 2ms OTP Engine for AI Agents (Claude Code, Cursor, Antigravity). Runs locally from the agentbox-mail npm package.
sf-intelligence
Offline, read-only MCP knowledge base for one Salesforce org's metadata, deps & impact. Runs locally from the sf-intelligence npm package.
bls-mcp
MCP server "bls-mcp", hosted remotely at 127.0.0.1, as configured in openai/openai-cookbook.
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const d=process.cwd();const S=n=>{const…
claude-flow
Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code. Runs locally from the @claude-flow/cli npm package. Needs 6 environment variables to run.
engine_mcp
MCP server "enginemcp" as configured in flutter/flutter. Launched with dart run tools/mcp/bin/main.dart.