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/Influship/influship-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/influship/influship-mcp/influship-mcp)<a href="https://agentmods.dev/mcp/influship/influship-mcp/influship-mcp"><img src="https://agentmods.dev/badge/mcp/influship/influship-mcp/influship-mcp/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/influship/influship-mcp/influship-mcp"><img src="https://agentmods.dev/badge/mcp/influship/influship-mcp/influship-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
influship-mcp 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 10d 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
{
"influship-mcp": {
"command": "npx",
"args": [
"-y",
"@influship/mcp"
],
"env": {
"INFLUSHIP_API_KEY": "",
"INFLUSHIP_MCP_URL": "https://mcp.influship.com/mcp"
}
}
}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.
- 10d ago First seen · 13 lines scan A f257d99c3fd3
influship-mcp is an MCP server published in the GitHub repository Influship/influship-mcp (1 stars, last pushed 3mo 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
yg3-mcp
Marketing MCP: content, SEO, outbound, LinkedIn, ads. Agents provision a sandbox with one POST. Remote server at mcp.yg3.ai.
seo-marketing
MCP server "seo-marketing", hosted remotely at seo.ezbizservices.com, as configured in ezbiz-services/mcp-seo-marketing.
behavior-mcp
MCP server "behavior-mcp" as configured in putervision/state-memory-mcp. Launched with behavior-mcp run. Needs 1 environment variable to run.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
lunchmoney-mcp
MCP server for managing LunchMoney personal finances: transactions, budgets, categories, and more. Runs locally from the @akutishevsky/lunchmoney-mcp npm package. Needs 2 environment variables to run.
claude-octopus
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. Runs locally from the claude-octopus npm package. Needs 7 environment variables to run.