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/mambalabsdev/mcp-event-presence-indexWrote 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/mambalabsdev/mcp-event-presence-index/mcp-event-presence-index)<a href="https://agentmods.dev/mcp/mambalabsdev/mcp-event-presence-index/mcp-event-presence-index"><img src="https://agentmods.dev/badge/mcp/mambalabsdev/mcp-event-presence-index/mcp-event-presence-index/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/mambalabsdev/mcp-event-presence-index/mcp-event-presence-index"><img src="https://agentmods.dev/badge/mcp/mambalabsdev/mcp-event-presence-index/mcp-event-presence-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-event-presence-index 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 12d 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.
This is a copy
86% identical to mamba-event-presence-index — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"mcp-event-presence-index": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-event-presence-index"
],
"env": {
"APIFY_TOKEN": ""
}
}
}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.
- 12d ago First seen · 12 lines scan A 1b5b0fccd016
mcp-event-presence-index is an MCP server published in the GitHub repository mambalabsdev/mcp-event-presence-index (0 stars, last pushed 4d 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. It is 86% identical to mamba-event-presence-index, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm run start-stdio.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.