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/studiomeyer-io/meetmyagent-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/studiomeyer-io/meetmyagent-mcp/meetmyagent)<a href="https://agentmods.dev/mcp/studiomeyer-io/meetmyagent-mcp/meetmyagent"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/meetmyagent-mcp/meetmyagent/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/studiomeyer-io/meetmyagent-mcp/meetmyagent"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/meetmyagent-mcp/meetmyagent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
meetmyagent 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 9d 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
{
"meetmyagent": {
"command": "npx",
"args": [
"-y",
"meetmyagent-mcp"
],
"env": {
"MEETMYAGENT_API_KEY": "",
"MEETMYAGENT_API_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.
- 9d ago First seen · 13 lines scan A 88564b42ab96
meetmyagent is an MCP server published in the GitHub repository studiomeyer-io/meetmyagent-mcp (0 stars, last pushed today), 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
graphmind
MCP server "graphmind" as configured in aouicher/graphmind. Launched with graphmind mcp.
linkedin-mcp
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own. Runs locally from the @gtm-api/linkedin-mcp npm package. Needs 1 environment variable to run.
gtm-api
MCP server "gtm-api", hosted remotely at mcp.gtm-api.com, as configured in gtm-api/linkedin-mcp.
mcp-geo
DigestSEO GEO Tracker: track brand citations across five AI search engines. Runs locally from the @digestseo/mcp-geo npm package.
digestseo-geo
MCP server "digestseo-geo", hosted remotely at geo-mcp.digestseo.com, as configured in AKzar1el/mcp-geo.
marketplaces-mcp-ru
MCP servers for Wildberries and Ozon Seller APIs (schema-driven, safety-gated). Runs locally from the marketplaces-mcp-ru Python package. Needs 5 environment variables to run.