Publora
REMOTE · MCP.PUBLORA.COM
Schedule and publish to 10 social platforms: LinkedIn, X, Instagram, TikTok, YouTube, and more.
Available components
Last scanned (8 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 0
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.publora.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=publora.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 72e7d10f710059f0e0deee8009fb950 |
| SANs: publora.com, *.publora.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.publora.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| publora.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.publora.com/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://mcp.publora.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| www-authenticate | Bearer resource_metadata="https://mcp.publora.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://mcp.publora.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.publora.com/mcp |
| Authorisation server | https://mcp.publora.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.publora.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.publora.com/mcp | HTTPS enforced | 308 | https://mcp.publora.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
complete_media Complete media upload ~85
Finalize an uploaded media file after the HTTP PUT to the presigned uploadUrl: Publora probes the bytes server-side and marks the media 'ready' for scheduling. Call once per uploaded mediaId (from get_upload_url), then schedule via update_post. Not needed for media attached via mediaUrls.
| Name | Type | Req | Description |
|---|---|---|---|
| mediaId | string | yes | MediaFile ID returned by get_upload_url |
No output schema declared.
No examples provided.
create_post Create post ~501
Create a post. FASTEST for media posts: pass mediaUrls (public https URLs — Publora downloads them server-side) together with scheduledTime to create AND schedule in one call; platforms like Instagram, TikTok, YouTube require media before scheduling. Manual alternative for local files: omit scheduledTime to create a draft, upload media with get_upload_url + HTTP PUT + complete_media (once per file), then call update_post with status 'scheduled'.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Post text content |
| idempotencyKey | string | – | Optional retry key. Reusing it with the identical request replays the original response without creating another post. |
| mediaUrls | array | – | Optional array (max 10) of public https URLs of images/videos to attach. Downloaded and validated server-side (jpeg, png, gif, webp, tiff, avif, mp4, mov, webm; images ≤25MB, videos ≤150MB). Must be… |
| platformSettings | object | – | Per-platform publishing options, keyed by platform. Example: { instagram: { coverUrl: 'https://.../cover.jpg' }, youtube: { title: 'My video', madeForKids: false }, tiktok: { viewerSetting: 'SELF_ONL… |
| platforms | array | yes | Array of platform identifiers in the exact format returned by list_connections. Each value must be the 'platformId' field copied verbatim from a connection object, e.g. ['twitter-1985855679454986200'… |
| scheduledTime | string | – | Optional ISO 8601 datetime for publishing, e.g. '2025-03-01T12:00:00Z'. Omit to create a draft. Scheduling a media-requiring platform without media fails validation — pass mediaUrls in the same call… |
No output schema declared.
No examples provided.
delete_media Delete media ~103
Remove one media file from a post group — e.g. a duplicate or never-uploaded slot that blocks scheduling with MEDIA_COUNT_EXCEEDED or media-not-ready errors. Find mediaIds via get_post (its 'media' array shows status per file). Deleting media from a scheduled post demotes it to draft; re-schedule with update_post afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| mediaId | string | yes | MediaFile ID to delete (see the 'media' array in get_post) |
No output schema declared.
No examples provided.
delete_post Delete post ~32
Delete a scheduled post group and all its platform-specific posts
| Name | Type | Req | Description |
|---|---|---|---|
| postGroupId | string | yes | Post group ID |
No output schema declared.
No examples provided.
get_post Get post ~33
Get details of a scheduled post group and its platform-specific posts
| Name | Type | Req | Description |
|---|---|---|---|
| postGroupId | string | yes | Post group ID |
No output schema declared.
No examples provided.
get_upload_url Get media upload URL ~199
Get a presigned S3 URL to upload a LOCAL media file (image/video) for a post. Call ONCE per file — repeat calls with the same fileName return the same mediaId instead of adding duplicate slots; use unique fileNames for different files. Next: HTTP PUT the raw bytes to uploadUrl with a Content-Type header EQUAL to the contentType passed here (the signature enforces it), then call complete_media with the mediaId. If the file is already reachable at a public URL, prefer create_post/update_post with mediaUrls — no upload steps at all.
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | yes | MIME type, e.g. 'image/jpeg' or 'video/mp4' |
| fileName | string | yes | File name, e.g. 'photo.jpg' |
| postGroupId | string | yes | Post group ID to attach media to |
| type | string | yes | Media type: 'image' or 'video' |
No output schema declared.
No examples provided.
linkedin_create_comment LinkedIn: comment on post ~196
Post a comment on a LinkedIn post
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Comment text (max 1250 characters). Supports mentions: @{urn:li:person:Dk968RHxiO|John Smith} or @{urn:li:organization:12345678|Company Name}. Person IDs must be raw native app-scoped member IDs retu… |
| parentComment | string | – | Parent comment URN for nested replies |
| platformId | string | yes | Platform connection ID, e.g. 'linkedin-XxxYyy' |
| postedId | string | yes | LinkedIn post URN, e.g. 'urn:li:share:123456' or 'urn:li:ugcPost:123456' |
No output schema declared.
No examples provided.
linkedin_create_reaction LinkedIn: react to post ~70
React to a LinkedIn post (like, praise, etc.)
| Name | Type | Req | Description |
|---|---|---|---|
| platformId | string | yes | Platform connection ID |
| postedId | string | yes | LinkedIn post URN, e.g. 'urn:li:share:123456' |
| reactionType | string | yes | Reaction type |
No output schema declared.
No examples provided.
linkedin_create_reshare LinkedIn: repost/reshare a post ~134
Reshare (repost) an existing LinkedIn post to your feed, optionally with commentary
| Name | Type | Req | Description |
|---|---|---|---|
| commentary | string | – | Optional commentary shown above the reshare (max 3000 characters) |
| parent | string | yes | URN of the post to reshare, e.g. 'urn:li:share:123456' or 'urn:li:ugcPost:123456' |
| platformId | string | yes | Platform connection ID, e.g. 'linkedin-XxxYyy' |
| visibility | string | – | Reshare visibility (default: PUBLIC). CONNECTIONS is only valid for personal accounts. |
No output schema declared.
No examples provided.
linkedin_delete_comment LinkedIn: delete comment ~81
Delete a comment from a LinkedIn post
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | Comment URN to delete, e.g. 'urn:li:comment:(urn:li:ugcPost:xxx,123456)' |
| platformId | string | yes | Platform connection ID |
| postedId | string | yes | LinkedIn post URN the comment belongs to |
No output schema declared.
No examples provided.
linkedin_delete_reaction LinkedIn: remove reaction ~43
Remove your reaction from a LinkedIn post
| Name | Type | Req | Description |
|---|---|---|---|
| platformId | string | yes | Platform connection ID |
| postedId | string | yes | LinkedIn post URN |
No output schema declared.
No examples provided.
linkedin_list_mentionables LinkedIn: list mentionable people ~107
List LinkedIn people captured from engagement (comments/reactions) on your connected company pages. Each entry carries the native app-scoped person id — the only id namespace LinkedIn resolves in mentions — plus a ready-to-use mention token in the form @{urn:li:person:ID|Name}. Requires a paid plan (403 UPGRADE_REQUIRED otherwise).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 25) |
| q | string | – | Name filter (substring) |
No output schema declared.
No examples provided.
list_connections List connected accounts ~25
List all connected social media accounts (Twitter, LinkedIn, TikTok, etc.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_posts List posts ~185
List scheduled/published posts with filtering by status, platform, date range
| Name | Type | Req | Description |
|---|---|---|---|
| fromDate | string | – | Start date filter (ISO 8601) |
| limit | number | – | Results per page (default: 20, max: 100) |
| page | number | – | Page number (default: 1) |
| platform | string | – | Filter by platform name, e.g. 'linkedin', 'twitter' |
| responseFormat | string | – | 'detailed' (default) returns full post content; 'concise' truncates each post's content to a preview to save tokens. |
| sortBy | string | – | Sort field (default: createdAt) |
| sortOrder | string | – | Sort direction (default: desc) |
| status | string | – | Filter by post status |
| toDate | string | – | End date filter (ISO 8601) |
No output schema declared.
No examples provided.
prune_media_reference Prune media reference ~87
Repair MEDIA_REFERENCE_MISSING by removing a stale/dangling media reference from an owned post group, even when the MediaFile row is absent or inaccessible. Use delete_media for normal existing media rows.
| Name | Type | Req | Description |
|---|---|---|---|
| mediaId | string | yes | Stale media ID reported in the MEDIA_REFERENCE_MISSING error |
| postGroupId | string | yes | Post group ID that contains the stale media reference |
No output schema declared.
No examples provided.
update_post Update post ~362
Edit an existing draft/scheduled post without deleting it. You may change its base content, target platforms, status, scheduled time, per-platform settings, and/or APPEND media from public https URLs via mediaUrls. Before changing platforms, call list_connections and copy each target's platformId verbatim. Published/failed posts and posts already being published are not editable. Scheduling re-validates the complete final content/media/platform state; omitting a field keeps its current value.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Optional replacement base post text. Updates every target without an explicit platform-specific override. An empty string is allowed for a draft; scheduling still enforces each platform's content/med… |
| idempotencyKey | string | – | Optional retry key. Reusing it with the identical request prevents repeated media appends and replays the original response. |
| mediaUrls | array | – | Optional array (max 10) of public https URLs of images/videos to APPEND to this post. Same rules as create_post: direct file URLs only; jpeg, png, gif, webp, tiff, avif, mp4, mov, webm; images ≤25MB,… |
| platformSettings | object | – | Per-platform publishing options to merge (same shape as create_post). Unknown platforms or fields are rejected. |
| platforms | array | – | Optional replacement target platform array. Call list_connections first and copy its platformId values verbatim. This replaces the whole set; [] is allowed only while the post remains a draft. |
| postGroupId | string | yes | Post group ID |
| scheduledTime | string | – | New scheduled time in ISO 8601 format |
| status | string | – | New status: 'draft' or 'scheduled' |
No output schema declared.
No examples provided.
How do I install the Publora MCP server?
Publora is a hosted endpoint at https://mcp.publora.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.publora.com
claude mcp add --transport http com-publora-mcp-server 'https://mcp.publora.com/mcp'
What is the Publora MCP server?
Publora is an MCP server listed in the public MCP registry as com.publora/mcp-server. Schedule and publish to 10 social platforms: LinkedIn, X, Instagram, TikTok, YouTube, and more. This page covers its hosted endpoint (https://mcp.publora.com/mcp).
Is the Publora MCP server safe to use?
Publora scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Publora MCP server expose?
Publora exposes 16 tools: list_connections, create_post, get_post, update_post, delete_post, and 11 more. Their descriptions and schemas cost roughly 2,243 tokens of context every time the server is loaded.
Does the Publora MCP server require authentication?
Yes. Publora asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Publora MCP server still maintained?
Publora is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.