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/lizTheDeveloper/ai-agent-messagingWrote 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/lizthedeveloper/ai-agent-messaging/agent-messaging)<a href="https://agentmods.dev/mcp/lizthedeveloper/ai-agent-messaging/agent-messaging"><img src="https://agentmods.dev/badge/mcp/lizthedeveloper/ai-agent-messaging/agent-messaging.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-messaging 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 7d 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
{
"agent-messaging": {
"command": "python",
"args": [
"mcp_server/servers/agent_messaging_server.py"
],
"env": {
"NATS_URL": "nats://localhost:4222",
"NATS_NAMESPACE": "themultiverse"
}
}
}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.
- 7d ago First seen · 12 lines scan A 20c9177dcfb4
agent-messaging is an MCP server published in the GitHub repository lizTheDeveloper/ai-agent-messaging (2 stars, last pushed 9mo 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
mcp-superset
MCP server for managing Apache Superset — dashboards, charts, datasets, SQL Lab, access control, and more. Runs locally from the mcp-superset Python package. Needs 3 environment variables to run.
AynOps
A Model Context Protocol server that gives AI Clients real-time cybersecurity reconnaissance capabilities — WHOIS, DNS enumeration, port scanning, SSL inspection, CVE lookup, IP reputation, ASN lookup and more. Runs locally from the AynOps Python package. Needs 2 environment variables to run.
openroad-mcp
OpenROAD MCP server (TypeScript/npx). Runs locally from the openroad-mcp npm package.
sagemath
Model Context Protocol server that provides stateful SageMath computations. Runs locally from the sagemath-mcp Python package.
lucius-mcp
Allure TestOps MCP Server. Runs locally from the lucius-mcp Python package. Needs 3 environment variables to run.
osm-edit
Review-first MCP server for previewed, version-checked OpenStreetMap road edits from local GPX surveys. Runs locally from the osm-edit-mcp Python package. Needs 3 environment variables to run.