io.github.arslan2012/qpost-mcp
REMOTE · QPOST.DEV · 2 COMPONENTS
MCP server for QPost — lets AI agents publish video and image posts to YouTube, TikTok, Instagram.
Available components
Last scanned (12 hours ago)
Scores higher than 69% 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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 481 tokens (~60/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +2
- Tool “delete_post” is now declared destructive security
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ 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://qpost.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qpost.dev | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8d680594746851470ee0bd53f9e7c4a2 |
| SANs: qpost.dev, staging.qpost.dev, *.staging.qpost.dev | ||||||
| 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 qpost.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| qpost.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="qpost"
Bearer realm="qpost"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qpost.dev/mcp | Verified | 200 | |
| http (plaintext) | http://qpost.dev/mcp | HTTPS enforced | 301 | https://qpost.dev/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 →
create_post ~219
Create and publish (or schedule) a video or image post to connected platforms. Media must be supplied as a publicly reachable URL (mediaUrl / imageUrls) or base64 (mediaBase64) — this is a hosted server and cannot read files from your machine. Omit scheduledFor to publish immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string | yes | Main text/caption of the post |
| imageUrls | array | – | Multiple image URLs for a carousel |
| mediaBase64 | string | – | Base64-encoded media bytes, if you have no public URL |
| mediaFilename | string | – | Filename for mediaBase64, e.g. clip.mp4 — sets the MIME type |
| mediaKind | string | yes | – |
| mediaUrl | string | – | Publicly reachable URL of the video or single image |
| platforms | array | yes | – |
| scheduledFor | string | – | ISO datetime; omit to publish immediately |
| timezone | string | – | IANA timezone, default "UTC" |
| title | string | – | Optional title (YouTube) |
No output schema declared.
No examples provided.
delete_post ~23
Permanently delete a post you own.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_post ~28
Get a single post by ID, including per-platform publish status.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_post_stats ~51
How a published post is doing: views, likes, comments and shares per platform, read live from the platform (TikTok so far), plus each platform's public URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_connected_accounts ~39
List the YouTube/TikTok/Instagram accounts connected to this QPost account. Call this before creating a post to see which platforms are available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_posts ~35
List posts on this account, optionally filtered by status or platform.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
retry_post ~23
Retry publishing a post that previously failed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
update_post ~63
Update a post's caption, schedule, timezone, or status. Only the fields you pass are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| caption | string | – | – |
| id | string | yes | – |
| scheduledFor | – | – | – |
| status | string | – | – |
| timezone | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.arslan2012/qpost-mcp server?
io.github.arslan2012/qpost-mcp is a hosted endpoint at https://qpost.dev/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 · qpost.dev
claude mcp add --transport http arslan2012-qpost-mcp 'https://qpost.dev/mcp'
What is the io.github.arslan2012/qpost-mcp server?
io.github.arslan2012/qpost-mcp is listed in the public MCP registry as io.github.arslan2012/qpost-mcp. MCP server for QPost, lets AI agents publish video and image posts to YouTube, TikTok, Instagram. This page covers its hosted endpoint (https://qpost.dev/mcp).
Is the io.github.arslan2012/qpost-mcp server safe to use?
io.github.arslan2012/qpost-mcp scores 77 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 io.github.arslan2012/qpost-mcp server expose?
io.github.arslan2012/qpost-mcp exposes 8 tools: list_connected_accounts, create_post, list_posts, get_post, get_post_stats, and 3 more. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Does the io.github.arslan2012/qpost-mcp server require authentication?
Yes. io.github.arslan2012/qpost-mcp 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 io.github.arslan2012/qpost-mcp server still maintained?
io.github.arslan2012/qpost-mcp 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.