MCP.Market

RepeatPost MCP server

online · 100% uptime
by repeatpost.com·com.repeatpost/mcp·v1.3.1
No reviews yet

Schedule and publish social media posts, write captions and create branded graphics with RepeatPost.

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed RepeatPost yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

RepeatPost tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How RepeatPost compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
243 ms
faster than 56% of 30,031 servers

Release history: 4 versions in the registry since 2026-10-09, latest 2026-10-31, typically one every 4 days.

Install RepeatPost in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://api.repeatpost.com/mcp
Add to Cursor

RepeatPost: common questions

Is RepeatPost MCP server safe?
Mostly: it is graded B (77/100). Read the RepeatPost safety report
How do I install RepeatPost?
It runs remotely at api.repeatpost.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does RepeatPost need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is RepeatPost maintained?
The latest release is v1.3.1.
Is RepeatPost up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does RepeatPost compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 243 ms (faster than 56% of 30,031 servers). Full comparison.