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/seena18/meshwrightWrote 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/seena18/meshwright/meshwright)<a href="https://agentmods.dev/mcp/seena18/meshwright/meshwright"><img src="https://agentmods.dev/badge/mcp/seena18/meshwright/meshwright/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/seena18/meshwright/meshwright"><img src="https://agentmods.dev/badge/mcp/seena18/meshwright/meshwright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
meshwright 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 1mo 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
{ "meshwright": { "command": "uvx", "args": [ "meshwright" ] } }
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.
- 1mo ago First seen · 8 lines scan A 34c7ba1e3b02
meshwright is an MCP server published in the GitHub repository seena18/meshwright (0 stars, last pushed 20d ago), 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-08-31.
Other mcp servers, from other repositories
prismaid-mcp
MCP server "prismaid-mcp" as configured in open-and-sustainable/prismaid. Runs in Docker (ghcr.io/open-and-sustainable/prismaid-mcp:0.17.1).
openflowkit-mcp
Local-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. Runs locally from the @vrun-design/openflowkit-mcp npm package.
perplexity
MCP server "perplexity" as configured in tdimino/claude-code-minoan. Runs /path/to/perplexity-mcp/build/index.js with node. Needs 1 environment variable to run.
cgr-capture
MCP server that captures agent judgments and outcomes as CGR substrate on GRAFOMEM Cloud. Runs locally from the grafomem-cgr Python package. Needs 6 environment variables to run.
terraform
MCP server "terraform" as configured in aws-samples/sample-agentic-chatbot-accelerator. Runs in Docker (hashicorp/terraform-mcp-server:0.5.2).
deepseek-delegate-mcp
MCP server "deepseek-delegate-mcp" as configured in trixmix821/deepseek-delegate-mcp. Runs locally from the deepseek-delegate-mcp npm package.