AdaptlyPost
REMOTE · MCP.ADAPTLYPOST.COM · SCANNED SEP 20
Schedule and post to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, Bluesky.
Available components
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 Security92
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
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.
How do I install the AdaptlyPost MCP server?
AdaptlyPost is a hosted endpoint at https://mcp.adaptlypost.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.adaptlypost.com
claude mcp add --transport http com-adaptlypost-mcp-server 'https://mcp.adaptlypost.com/mcp'
{
"mcpServers": {
"com-adaptlypost-mcp-server": {
"url": "https://mcp.adaptlypost.com/mcp"
}
}
} {
"servers": {
"com-adaptlypost-mcp-server": {
"type": "http",
"url": "https://mcp.adaptlypost.com/mcp"
}
}
} [mcp_servers.com-adaptlypost-mcp-server] url = "https://mcp.adaptlypost.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-adaptlypost-mcp-server": {
"type": "remote",
"url": "https://mcp.adaptlypost.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-adaptlypost-mcp-server --url 'https://mcp.adaptlypost.com/mcp' --transport streamable-http
mcp_servers:
com-adaptlypost-mcp-server:
url: "https://mcp.adaptlypost.com/mcp" {
"McpServers": {
"com-adaptlypost-mcp-server": {
"Transport": "http",
"Url": "https://mcp.adaptlypost.com/mcp"
}
}
} assistant mcp add com-adaptlypost-mcp-server -t streamable-http -u 'https://mcp.adaptlypost.com/mcp'
{
"mcpServers": {
"com-adaptlypost-mcp-server": {
"type": "http",
"url": "https://mcp.adaptlypost.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 −31
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 0
- Tool “bulk_schedule_posts” changed its title: Bulk Schedule Posts cosmetic
- Tool “create_post” changed its title: Create Post cosmetic
- Tool “delete_post” changed its title: Delete Post cosmetic
- Tool “get_post” changed its title: Get Post cosmetic
- Tool “get_upload_urls” changed its title: Get Media Upload URLs cosmetic
- Tool “list_accounts” changed its title: List Connected Accounts cosmetic
- Tool “list_post_results” changed its title: List Post Results cosmetic
- Tool “list_posts” changed its title: List Posts cosmetic
- Tool “publish_draft” changed its title: Publish Draft cosmetic
- Tool “retry_failed_platforms” changed its title: Retry Failed Platforms cosmetic
- Tool “update_post” changed its title: Update Post cosmetic
- Tool “upload_media” changed its title: Upload Media cosmetic
12 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
- Tool “update_post” no longer declares itself destructive security
- Stability: unverified → 0.03 ▲ functional
- 29 Aug 26 63
First indexed and scored.
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 20 Sept 2026 · Probed https://mcp.adaptlypost.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=adaptlypost.com | CN=WE1,O=Google Trust Services,C=US | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | d063b9389ac309c13d5df2dfbccdf0b |
| SANs: adaptlypost.com, *.adaptlypost.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.adaptlypost.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| adaptlypost.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.adaptlypost.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Authentication required"
Bearer resource_metadata="https://mcp.adaptlypost.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Authentication required"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.adaptlypost.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Authentication required" |
Protected resource metadata
| Document | https://mcp.adaptlypost.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.adaptlypost.com/mcp |
| Authorisation server | https://harmonious-puzzle-14.authkit.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.adaptlypost.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.adaptlypost.com/mcp | HTTPS enforced | 301 | https://mcp.adaptlypost.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 →
bulk_schedule_posts Bulk Schedule Posts ~335
Schedule multiple posts at once. Each post gets its own text, content type, schedule time, and optional media. All posts share the same target platforms and connection IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| blueskyConnectionIds | array | – | Bluesky account connection IDs to post from |
| facebookConfigs | array | – | Facebook per-page config with post type and video title |
| instagramConfigs | array | – | Instagram per-connection config to set post type (FEED, REEL, STORY) |
| instagramConnectionIds | array | – | Instagram account connection IDs to post from |
| linkedinConnectionIds | array | – | LinkedIn account connection IDs to post from |
| pageIds | array | – | Facebook page IDs |
| pinterestConfigs | array | – | Pinterest per-connection config. boardId is required for Pinterest posts |
| pinterestConnectionIds | array | – | Pinterest account connection IDs to post from |
| platforms | array | yes | Target platforms |
| posts | array | yes | Array of posts to schedule |
| threadsConnectionIds | array | – | Threads account connection IDs to post from |
| tiktokConfigs | array | – | TikTok per-connection config. Each entry needs connectionId + privacyLevel at minimum |
| tiktokConnectionIds | array | – | TikTok account connection IDs to post from |
| timezone | string | – | IANA timezone |
| twitterConnectionIds | array | – | X (Twitter) account connection IDs to post from |
| youtubeConfigs | array | – | YouTube per-connection config with video title, tags, privacy, etc. |
| youtubeConnectionIds | array | – | YouTube channel connection IDs to post from |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The created scheduled post records with their ids, statuses, and schedule times as returned by the AdaptlyPost API. |
No examples provided.
create_post Create Post ~532
Create and schedule a post to one or more platforms. Pass connection IDs from list_accounts to target specific accounts. Omit scheduledAt to post immediately, or set saveAsDraft to save without publishing. For platform-specific options (YouTube titles, TikTok privacy, Pinterest boards, Instagram post type), use the corresponding platform configs.
| Name | Type | Req | Description |
|---|---|---|---|
| blueskyConnectionIds | array | – | Bluesky account connection IDs to post from |
| contentType | string | yes | Content type: TEXT, IMAGE, VIDEO, or CAROUSEL |
| facebookConfigs | array | – | Facebook per-page config with post type and video title |
| instagramConfigs | array | – | Instagram per-connection config to set post type (FEED, REEL, STORY) |
| instagramConnectionIds | array | – | Instagram account connection IDs to post from |
| linkedinConnectionIds | array | – | LinkedIn account connection IDs to post from |
| mediaUrls | array | – | Media URLs to attach. Use publicUrl values from upload_media or get_upload_urls |
| pageIds | array | – | Facebook page IDs |
| pinterestConfigs | array | – | Pinterest per-connection config. boardId is required for Pinterest posts |
| pinterestConnectionIds | array | – | Pinterest account connection IDs to post from |
| platformTexts | array | – | Per-platform caption overrides |
| platforms | array | yes | Target platforms (e.g. ["LINKEDIN", "TWITTER"]) |
| saveAsDraft | boolean | – | Save as draft instead of publishing |
| scheduledAt | string | – | ISO 8601 datetime to schedule (e.g. "2026-03-15T10:00:00Z"). Omit to post immediately |
| text | string | – | Default post text shared across platforms |
| threadsConnectionIds | array | – | Threads account connection IDs to post from |
| thumbnailTimestampMs | number | – | Generate thumbnail from video at this timestamp (milliseconds) |
| thumbnailUrl | string | – | Custom thumbnail image URL for video posts |
| tiktokConfigs | array | – | TikTok per-connection config. Each entry needs connectionId + privacyLevel at minimum |
| tiktokConnectionIds | array | – | TikTok account connection IDs to post from |
| timezone | string | – | IANA timezone (e.g. "America/New_York") |
| twitterConnectionIds | array | – | X (Twitter) account connection IDs to post from |
| youtubeConfigs | array | – | YouTube per-connection config with video title, tags, privacy, etc. |
| youtubeConnectionIds | array | – | YouTube channel connection IDs to post from |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The created post record including its id, status, and scheduled time as returned by the AdaptlyPost API. |
No examples provided.
delete_post Delete Post ~31
Delete a scheduled or draft post. Can't delete published posts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Post ID to delete |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The deletion confirmation for the post as returned by the AdaptlyPost API. |
No examples provided.
get_post Get Post ~36
Get full details of a single post by ID, including per-platform publishing status and error messages.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Post ID |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The full post record including its id, status, per-platform publishing status, and error messages as returned by the AdaptlyPost API. |
No examples provided.
get_upload_urls Get Media Upload URLs ~143
Get presigned upload URLs for direct file uploads. Returns uploadUrl (PUT your file here) and publicUrl (use in create_post mediaUrls). This only mints a URL — you MUST PUT the file to uploadUrl and confirm a 2xx response before using publicUrl, otherwise create_post/bulk rejects it with "Media file(s) not found in storage". Prefer the upload_media tool, which performs the upload for you. For each file, provide fileName and mimeType. Supported types: image/jpeg, image/png, image/webp, video/mp4, video/quicktime.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to get upload URLs for |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | An object with urls: one { uploadUrl, publicUrl, key } entry per requested file. |
No examples provided.
list_accounts List Connected Accounts ~68
List all connected social media accounts across all platforms (LinkedIn, YouTube, Instagram, Facebook, TikTok, Pinterest, Threads, Bluesky, Twitter). Returns connection IDs needed for creating posts. Facebook page accounts also include a pageId (the Facebook Page ID) since pages have no username.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The connected social accounts with their platform, connection ID, username, and pageId for Facebook pages as returned by the AdaptlyPost API. |
No examples provided.
list_post_results List Post Results ~44
Check per-platform posting results — success/failure status with error details for each platform a post was sent to.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Post ID to check results for |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The per-platform posting results with success/failure status and error details as returned by the AdaptlyPost API. |
No examples provided.
list_posts List Posts ~118
List posts with optional filters by status, platform, or date range. Supports pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | – | End date (ISO 8601) |
| limit | number | – | Max results |
| offset | number | – | Pagination offset |
| platforms | array | – | Filter by platform |
| sortOrder | string | – | NEWEST or OLDEST |
| startDate | string | – | Start date (ISO 8601) |
| statuses | array | – | Filter by status (e.g. ["SCHEDULED", "DRAFT"]) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The matching posts with their ids, statuses, platforms, and schedule times as returned by the AdaptlyPost API. |
No examples provided.
publish_draft Publish Draft ~61
Publish a draft post immediately or schedule it for later.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Draft post ID |
| scheduledAt | string | – | Schedule time (ISO 8601). Omit to publish now |
| timezone | string | – | IANA timezone |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The published or scheduled post record with its updated status as returned by the AdaptlyPost API. |
No examples provided.
retry_failed_platforms Retry Failed Platforms ~47
Retry publishing on platforms that failed. Get platform IDs from list_post_results.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Post ID |
| platformIds | array | yes | Failed platform IDs to retry |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The retry outcome for the requested platform IDs as returned by the AdaptlyPost API. |
No examples provided.
update_post Update Post ~425
Update a scheduled or draft post's caption, schedule, accounts, media, or platform configs. Cannot update published posts.
| Name | Type | Req | Description |
|---|---|---|---|
| blueskyConnectionIds | array | – | Bluesky account connection IDs to post from |
| contentType | string | – | – |
| facebookConfigs | array | – | Facebook per-page config with post type and video title |
| id | string | yes | Post ID to update |
| instagramConfigs | array | – | Instagram per-connection config to set post type (FEED, REEL, STORY) |
| instagramConnectionIds | array | – | Instagram account connection IDs to post from |
| linkedinConnectionIds | array | – | LinkedIn account connection IDs to post from |
| mediaUrls | array | – | Updated media URLs. Use publicUrl values from upload_media or get_upload_urls |
| pageIds | array | – | Facebook page IDs |
| pinterestConfigs | array | – | Pinterest per-connection config. boardId is required for Pinterest posts |
| pinterestConnectionIds | array | – | Pinterest account connection IDs to post from |
| platformTexts | array | – | – |
| platforms | array | – | Updated target platforms |
| scheduledAt | string | – | Updated schedule time (ISO 8601) |
| text | string | – | Updated text |
| threadsConnectionIds | array | – | Threads account connection IDs to post from |
| thumbnailTimestampMs | number | – | Generate thumbnail from video at this timestamp (milliseconds) |
| thumbnailUrl | string | – | Custom thumbnail image URL for video posts |
| tiktokConfigs | array | – | TikTok per-connection config. Each entry needs connectionId + privacyLevel at minimum |
| tiktokConnectionIds | array | – | TikTok account connection IDs to post from |
| timezone | string | – | IANA timezone for the schedule time |
| twitterConnectionIds | array | – | X (Twitter) account connection IDs to post from |
| youtubeConfigs | array | – | YouTube per-connection config with video title, tags, privacy, etc. |
| youtubeConnectionIds | array | – | YouTube channel connection IDs to post from |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The updated post record including its id, status, and scheduled time as returned by the AdaptlyPost API. |
No examples provided.
upload_media Upload Media ~148
Upload media files for use in posts. Supports two modes: 1. URLs: pass public image/video URLs — the server downloads and re-uploads them. 2. Files: pass base64-encoded file data directly (e.g. when the user attaches an image in the conversation). Returns mediaUrls ready to pass into create_post. The user does NOT need to see the returned URLs — just pass them to create_post.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Direct file uploads as base64. Use this when the user attaches/pastes an image or video in the conversation |
| urls | array | – | Public URLs of images or videos to upload (e.g. ["https://example.com/photo.jpg"]) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | An object with uploaded (array of { publicUrl, key } per file) and mediaUrls (the public URLs ready to pass to create_post). |
No examples provided.
What is the AdaptlyPost MCP server?
AdaptlyPost is an MCP server listed in the public MCP registry as com.adaptlypost/mcp-server. Schedule and post to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, Bluesky. This page covers its hosted endpoint (https://mcp.adaptlypost.com/mcp).
Is the AdaptlyPost MCP server safe to use?
AdaptlyPost scores 37 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 AdaptlyPost MCP server expose?
AdaptlyPost exposes 12 tools: list_accounts, upload_media, get_upload_urls, create_post, get_post, and 7 more. Their descriptions and schemas cost roughly 1,988 tokens of context every time the server is loaded.
Does the AdaptlyPost MCP server require authentication?
Yes. AdaptlyPost 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 AdaptlyPost MCP server still maintained?
AdaptlyPost is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.