io.github.reppingai/repping
Repping.ai
Is the Repping.ai MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Read and prepare posts, calendar, links and analytics in Repping.ai. Changes require human approval.
needs auth probed 2026-11-14 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","code":"invalid_token","message":"Could not validate these credentials. Check them an- Endpoint
- https://www.repping.ai/api/mcp (streamable-http)
- Host
- www.repping.ai
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://www.repping.ai/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server www.repping.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes repping:read repping:prepare repping:staff-read repping:staff-prepare offline_access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/reppingai/repping-mcp
- Website
- https://www.repping.ai/mcp
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention analytics or approval.
- JustIdea Agency agency.justidea/justidea-agency · alive
- Adako: ad ops for AI assistants ai.adako/ads · needs auth
- AgenticBooks ai.agenticbooks/books · needs auth
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- Analytics Legends — SAP AI & Analytics MCP Server ai.analyticslegends/sap-analytics · alive
- ai.argushq/enforcement-database · no DNS
- AutoRFP.ai ai.autorfp/mcp · needs auth
- Authoryze ai.authoryze/authoryze · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.