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/MortalPastry/wyrd-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/mortalpastry/wyrd-mcp/wyrd-scribe-wyrd)<a href="https://agentmods.dev/mcp/mortalpastry/wyrd-mcp/wyrd-scribe-wyrd"><img src="https://agentmods.dev/badge/mcp/mortalpastry/wyrd-mcp/wyrd-scribe-wyrd/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/mortalpastry/wyrd-mcp/wyrd-scribe-wyrd"><img src="https://agentmods.dev/badge/mcp/mortalpastry/wyrd-mcp/wyrd-scribe-wyrd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
wyrd 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 23d 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
{
"wyrd": {
"command": "npx",
"args": [
"-y",
"wyrd-mcp"
],
"env": {
"WYRD_GRANT": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 2. 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.
- 23d ago First seen · 12 lines scan A 7d1d9ec716b2
wyrd is an MCP server published in the GitHub repository MortalPastry/wyrd-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-09-24.
Other mcp servers, from other repositories
caelune-mcp
MCP server "caelune-mcp" as configured in EllisMorrow/Caelune. Launched with https://github.com/EllisMorrow/Caelune/releases/download/v0.5.6/caelune-mcp-win-.
md-feedback
Review markdown plans before AI agents build. Annotate, gate-check, apply fixes, session handoffs. Runs locally from the md-feedback npm package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.
slack-mcp-server
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth. Runs locally from the @jtalk22/slack-mcp npm package. Needs 2 environment variables to run.
telegram-dev
MCP server "telegram-dev" as configured in leshchenko1979/fast-mcp-telegram. Runs src.server with python3.