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/AndreiFinogeev/weft-mcpWrote 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/andreifinogeev/weft-mcp/weft)<a href="https://agentmods.dev/mcp/andreifinogeev/weft-mcp/weft"><img src="https://agentmods.dev/badge/mcp/andreifinogeev/weft-mcp/weft/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/andreifinogeev/weft-mcp/weft"><img src="https://agentmods.dev/badge/mcp/andreifinogeev/weft-mcp/weft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
weft 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 yesterday.
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
{ "weft": { "url": "https://letsweft.com/api/mcp", "type": "streamable-http" } }
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.
- yesterday First seen · 6 lines scan A f2caaa8da912
weft is an MCP server published in the GitHub repository AndreiFinogeev/weft-mcp (0 stars, last pushed yesterday), 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-27.
Other mcp servers, from other repositories
jobs-mcp-proxy
MCP server for AI job search — find jobs, track applications, get alerts. Claude, ChatGPT, Cursor. Runs locally from the @foundrole/ai-job-search-mcp npm package.
kelvia-mcp
Task manager your agent can fully operate: boards, tasks, sprints, roles, worklogs, day planner. Runs locally from the kelvia-mcp npm package. Needs 3 environment variables to run.
laver-mcp
Kanban boards, sprints, tickets and a team wiki, with versioned writes for concurrent agents. Runs locally from the @laver/mcp npm package. Needs 3 environment variables to run.
kaiten
A local MCP server that connects Cursor and Claude Code to Kaiten, a work-management app with tasks and kanban boards. It runs with the Kaiten MCP package and needs a Kaiten API token and workspace address.
kaiten-mcp
A local MCP server that connects Cursor and Claude Code to Kaiten, a work-management app with tasks and kanban boards. It runs from a Python package and needs a Kaiten API token, workspace address, and server URL.
graphmind
MCP server "graphmind" as configured in aouicher/graphmind. Launched with graphmind mcp.