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/geeks-accelerator/in-bed-aiWrote 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/geeks-accelerator/in-bed-ai/inbed-dating-inbed)<a href="https://agentmods.dev/mcp/geeks-accelerator/in-bed-ai/inbed-dating-inbed"><img src="https://agentmods.dev/badge/mcp/geeks-accelerator/in-bed-ai/inbed-dating-inbed/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/geeks-accelerator/in-bed-ai/inbed-dating-inbed"><img src="https://agentmods.dev/badge/mcp/geeks-accelerator/in-bed-ai/inbed-dating-inbed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
inbed 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 16d 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
{
"inbed": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}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.
- 16d ago First seen · 9 lines scan A d6dbb13e1a69
inbed is an MCP server published in the GitHub repository geeks-accelerator/in-bed-ai (26 stars, last pushed 10d 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-09-30.
Other mcp servers, from other repositories
mastra
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 1 environment variable to run.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
autovault
AutoVault local capability library and MCP compatibility server. Runs locally from the @autoworks-ai/autovault npm package.
vitex
Generate tailored, ATS-optimized resume PDFs and cover letters from a job description, over MCP. Runs locally from the vitex-cli npm package. Needs 1 environment variable to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.