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/target1m/ravenpost-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/target1m/ravenpost-mcp/ravenpost)<a href="https://agentmods.dev/mcp/target1m/ravenpost-mcp/ravenpost"><img src="https://agentmods.dev/badge/mcp/target1m/ravenpost-mcp/ravenpost/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/target1m/ravenpost-mcp/ravenpost"><img src="https://agentmods.dev/badge/mcp/target1m/ravenpost-mcp/ravenpost.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ravenpost 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 8d 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
{
"ravenpost": {
"url": "https://api.ravenpo.st/mcp",
"type": "streamable-http"
}
}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.
- 8d ago First seen · 6 lines scan A 9f8d5d06b286
ravenpost is an MCP server published in the GitHub repository target1m/ravenpost-mcp (1 stars, last pushed 9d 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
framefetch
Any social-video URL → transcript, metadata, frames, OCR, summary, search, Q&A. MCP server + x402. Remote server at framefetch.net.
postfast
MCP server for the PostFast API — schedule and manage social media posts via AI tools. Runs locally from the postfast-mcp npm package. Needs 1 environment variable to run.
postfast-mcp
MCP server for the PostFast API — schedule and manage social media posts via AI tools. Runs locally from the postfast-mcp npm package. Needs 1 environment variable to run.
postiz-mcp
Canonical Postiz client for any MCP-compatible client: full coverage of the Postiz public API (integrations, posts, uploads, analytics, video) with env-gated writes, confirm-required deletes, and a built-in 30/hr rate-limit guard. MCP server + first-class. Runs locally from the postiz-mcp npm package.
mcp
Connect AI agents to Replynodes over the Model Context Protocol. Runs locally from the @replynodes/mcp npm package. Needs 1 environment variable to run.
social0-mcp
Post and schedule across 9 social platforms from Claude, Cursor, or ChatGPT. Runs locally from the social0-mcp npm package. Needs 1 environment variable to run.