Is com.uplika/uplika up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://api.uplika.com/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (fetch failed: 801ED4ED01000000:error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:../deps/open…)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (not asked: https://api.uplika.com did not answer the agent-card request).https://api.uplika.com/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (not asked: https://api.uplika.com did not answer the agent-card request)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (not asked: https://api.uplika.com did not answer the agent-card request)./.well-known/http-message-signatures-directory |
Read at https://api.uplika.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 61 tools: approve_reply, bridge_status, create_automation, create_comment_to_dm, delete_automation, delete_post, delete_reply, describe_grammar, diagnose_naver_blog, disable_automation, duplicate_automation, enable_automation, expand_naver_keywords, follow, get_automation, get_contact, get_help, get_insights, get_naver_keyword_history, get_post, get_publish_options, get_quota, hide_reply, like, list_accounts, list_automation_runs, list_automation_templates, list_automation_versions, list_automations, list_channel_posts, list_conversations, list_mentions, list_naver_drafts, list_naver_keyword_reports, list_platforms, list_posts, list_replies, media_complete, media_from_url, media_presign, media_upload_link, media_upload_status, naver_layout, open_post, publish, publish_naver_draft, publish_now, put_automation, read_conversation, refresh_account, reply, research_naver_keywords, retry_post, search_youtube_videos, select_channels, send_dm, send_to_past_comments, update_automation, update_media, update_post, validate_automation.
Its tools changed between 2026-09 and 2026-10:
- Added (39):
approve_reply,create_automation,create_comment_to_dm,delete_automation,delete_reply,describe_grammar,diagnose_naver_blog,disable_automation,duplicate_automation,enable_automation,expand_naver_keywords,follow,get_automation,get_contact,get_help,get_naver_keyword_history,get_publish_options,like,list_automation_runs,list_automation_templates,list_automation_versions,list_automations,list_conversations,list_mentions,list_naver_drafts,list_naver_keyword_reports,naver_layout,publish_naver_draft,publish_now,put_automation,read_conversation,research_naver_keywords,search_youtube_videos,send_dm,send_to_past_comments,update_automation,update_media,update_post,validate_automation bridge_status: description changeddelete_post: description changedget_insights: description changedget_post: description changedlist_channel_posts: description changedlist_platforms: description changedlist_posts: description, input schema changedlist_replies: description changedmedia_from_url: description, input schema changedmedia_presign: description, input schema changedmedia_upload_link: description changedmedia_upload_status: description, input schema changedopen_post: description changedpublish: description, input schema changedrefresh_account: description changedreply: description, input schema changedretry_post: description, input schema changedselect_channels: description, input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.uplika/uplika |
|---|---|
| Endpoint | https://api.uplika.com/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt