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/posecode-dev/posecodeWrote 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/posecode-dev/posecode/posecode-mcp-posecode-mcp)<a href="https://agentmods.dev/mcp/posecode-dev/posecode/posecode-mcp-posecode-mcp"><img src="https://agentmods.dev/badge/mcp/posecode-dev/posecode/posecode-mcp-posecode-mcp/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/posecode-dev/posecode/posecode-mcp-posecode-mcp"><img src="https://agentmods.dev/badge/mcp/posecode-dev/posecode/posecode-mcp-posecode-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
posecode-mcp 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
{
"posecode-mcp": {
"command": "npx",
"args": [
"-y",
"posecode-mcp"
],
"env": {
"POSECODE_BASE_URL": ""
}
}
}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 · 12 lines scan A d410e048a129
posecode-mcp is an MCP server published in the GitHub repository posecode-dev/posecode (119 stars, last pushed 4d ago), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
paperbanana
Agentic framework for automated academic illustration generation. Runs locally from the paperbanana Python package.
x402-bridge
Pay any x402 endpoint on the open web: auto-paying bridge with Bazaar discovery and spend caps. Runs locally from the @three-ws/mcp-bridge npm package. Needs 13 environment variables to run.
3D-AI-Agent-Avatar
3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers. Runs locally from the @three-ws/avatar-agent npm package. Needs 11 environment variables to run.
metaplex-agent
Deploy AI agents on-chain on Solana with an EIP-8004 identity. Deploy fee funds $THREE buybacks. Runs locally from the @three-ws/metaplex-agent-mcp npm package. Needs 9 environment variables to run.
three-token-mcp
Price, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token. Runs locally from the @three-ws/three-token-mcp npm package. Needs 5 environment variables to run.
ibm-watsonx
IBM watsonx.ai MCP by three.ws: chat, text generation, embeddings, and tokenization. Runs locally from the @three-ws/ibm-watsonx-mcp npm package. Needs 7 environment variables to run.