Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Postlyra

REMOTE · POSTLYRA.APP

Manage Telegram drafts, media, schedules and publications from AI clients.

Available components

0 this week 92 Trust /100

Last scanned (6 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security89
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 9167 tokens (~218/item across 42 items; 41 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 43 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
  • Supports UI / widget rendering.Pass
Changelog

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.

  • 1 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “create_post_draft” rewrote its description, which is the text the model reads security
  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • “publish_post” added an optional parameter “pinAfterPublish” cosmetic
    • “reschedule_publication” added an optional parameter “pinAfterPublish” cosmetic
    • “schedule_post” added an optional parameter “pinAfterPublish” cosmetic
  • 29 Oct 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “update_post” rewrote its description, which is the text the model reads security
    • Tool coverage: 39% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • “apply_post_to_publication” reworded the description of “expectedRevision” cosmetic
    • “apply_post_to_publication” reworded the description of “publicationId” cosmetic
    • “archive_post” reworded the description of “postId” cosmetic
    • “assign_signature” reworded the description of “channelId” cosmetic
    • “assign_signature” reworded the description of “draftId” cosmetic
    • “assign_signature” reworded the description of “selection” cosmetic
    • “assign_signature” reworded the description of “target” cosmetic
    • “attach_media” reworded the description of “expectedRevision” cosmetic
    • “attach_media” reworded the description of “mediaId” cosmetic
    • “attach_media” reworded the description of “postId” cosmetic
    • “attach_media_to_draft” reworded the description of “draftId” cosmetic
    • “attach_media_to_draft” reworded the description of “mediaFile1” cosmetic
    • “attach_media_to_draft” reworded the description of “mediaFile2” cosmetic
    • “attach_media_to_draft” reworded the description of “mediaFile3” cosmetic
    • “attach_media_to_draft” reworded the description of “mediaFile4” cosmetic
    • “attach_media_to_draft” reworded the description of “mediaFile5” cosmetic
    • “attach_media_to_draft” reworded the description of “mediaFile6” cosmetic
    • “attach_media_to_draft” reworded the description of “mediaFiles” cosmetic
    • “attach_media_to_draft” reworded the description of “references” cosmetic
    • “cancel_publication” reworded the description of “publicationId” cosmetic
    • “convert_draft_to_signature” reworded the description of “channelIds” cosmetic
    • “convert_draft_to_signature” reworded the description of “default” cosmetic
    • “convert_draft_to_signature” reworded the description of “draftId” cosmetic
    • “convert_draft_to_signature” reworded the description of “title” cosmetic
    • “copy_post” reworded the description of “postId” cosmetic
    • “copy_post” reworded the description of “title” cosmetic
    • “create_media_upload” reworded the description of “category” cosmetic
    • “create_media_upload” reworded the description of “contentType” cosmetic
    • “create_media_upload” reworded the description of “fileName” cosmetic
    • “create_media_upload” reworded the description of “sizeBytes” cosmetic
    • “create_post_draft” reworded the description of “language” cosmetic
    • “create_post_draft” reworded the description of “mediaFile1” cosmetic
    • “create_post_draft” reworded the description of “mediaFile2” cosmetic
    • “create_post_draft” reworded the description of “mediaFile3” cosmetic
    • “create_post_draft” reworded the description of “mediaFile4” cosmetic
    • “create_post_draft” reworded the description of “mediaFile5” cosmetic
    • “create_post_draft” reworded the description of “mediaFile6” cosmetic
    • “create_post_draft” reworded the description of “mediaFiles” cosmetic
    • “create_post_draft” reworded the description of “references” cosmetic
    • “create_post_draft” reworded the description of “signatureSelection” cosmetic
    • “create_post_draft” reworded the description of “templateId” cosmetic
    • “create_post_draft” reworded the description of “topic” cosmetic
    • “create_signature” reworded the description of “inlineButtons” cosmetic
    • “create_signature” reworded the description of “language” cosmetic
    • “create_signature” reworded the description of “mediaFile1” cosmetic
    • “create_signature” reworded the description of “mediaFile2” cosmetic
    • “create_signature” reworded the description of “mediaFile3” cosmetic
    • “create_signature” reworded the description of “mediaFile4” cosmetic
    • “create_signature” reworded the description of “mediaFile5” cosmetic
    • “create_signature” reworded the description of “mediaFile6” cosmetic
    • “create_signature” reworded the description of “mediaFiles” cosmetic
    • “create_signature” reworded the description of “title” cosmetic
    • “create_template” reworded the description of “category” cosmetic
    • “create_template” reworded the description of “description” cosmetic
    • “create_template” reworded the description of “documentJson” cosmetic
    • “create_template” reworded the description of “locale” cosmetic
    • “create_template” reworded the description of “name” cosmetic
    • “delete_publication” reworded the description of “publicationId” cosmetic
    • “delete_signature” reworded the description of “signatureId” cosmetic
    • “delete_template” reworded the description of “templateId” cosmetic
    • “finalize_media_upload” reworded the description of “uploadIntentId” cosmetic
    • “get_content_attention” reworded the description of “locale” cosmetic
    • “get_post” reworded the description of “postId” cosmetic
    • “get_postlyra_guide” reworded the description of “level” cosmetic
    • “get_postlyra_guide” reworded the description of “locale” cosmetic
    • “get_postlyra_guide” reworded the description of “topic” cosmetic
    • “get_signature” reworded the description of “signatureId” cosmetic
    • “list_publications” reworded the description of “channelId” cosmetic
    • “list_publications” reworded the description of “from” cosmetic
    • “list_publications” reworded the description of “limit” cosmetic
    • “list_publications” reworded the description of “offset” cosmetic
    • “list_publications” reworded the description of “postId” cosmetic
    • “list_publications” reworded the description of “status” cosmetic
    • “list_publications” reworded the description of “to” cosmetic
    • “preview_post” reworded the description of “draftId” cosmetic
    • “preview_signature” reworded the description of “signatureId” cosmetic
    • “publish_post” reworded the description of “draftId” cosmetic
    • “publish_post” reworded the description of “idempotencyKey” cosmetic
    • “reschedule_publication” reworded the description of “publicationId” cosmetic
    • “reschedule_publication” reworded the description of “scheduledAt” cosmetic
    • “restore_post” reworded the description of “postId” cosmetic
    • “schedule_post” reworded the description of “channelId” cosmetic
    • “schedule_post” reworded the description of “expectedRevision” cosmetic
    • “schedule_post” reworded the description of “idempotencyKey” cosmetic
    • “schedule_post” reworded the description of “postId” cosmetic
    • “schedule_post” reworded the description of “scheduledAt” cosmetic
    • “schedule_post” reworded the description of “timezone” cosmetic
    • “search_posts” reworded the description of “channelId” cosmetic
    • “search_posts” reworded the description of “from” cosmetic
    • “search_posts” reworded the description of “includeArchived” cosmetic
    • “search_posts” reworded the description of “limit” cosmetic
    • “search_posts” reworded the description of “offset” cosmetic
    • “search_posts” reworded the description of “query” cosmetic
    • “search_posts” reworded the description of “status” cosmetic
    • “search_posts” reworded the description of “to” cosmetic
    • “show_post_card” reworded the description of “postId” cosmetic
    • “update_post” reworded the description of “expectedRevision” cosmetic
    • “update_post” reworded the description of “locale” cosmetic
    • “update_post” reworded the description of “needsAttention” cosmetic
    • “update_post” reworded the description of “postId” cosmetic
    • “update_post” reworded the description of “title” cosmetic
    • “update_post_draft” reworded the description of “appendCallToAction” cosmetic
    • “update_post_draft” reworded the description of “draftId” cosmetic
    • “update_post_draft” reworded the description of “mediaFile1” cosmetic
    • “update_post_draft” reworded the description of “mediaFile2” cosmetic
    • “update_post_draft” reworded the description of “mediaFile3” cosmetic
    • “update_post_draft” reworded the description of “mediaFile4” cosmetic
    • “update_post_draft” reworded the description of “mediaFile5” cosmetic
    • “update_post_draft” reworded the description of “mediaFile6” cosmetic
    • “update_post_draft” reworded the description of “mediaFiles” cosmetic
    • “update_post_draft” reworded the description of “references” cosmetic
    • “update_post_draft” reworded the description of “signatureSelection” cosmetic
    • “update_post_draft” reworded the description of “templateId” cosmetic
    • “update_signature” reworded the description of “inlineButtons” cosmetic
    • “update_signature” reworded the description of “language” cosmetic
    • “update_signature” reworded the description of “mediaFile1” cosmetic
    • “update_signature” reworded the description of “mediaFile2” cosmetic
    • “update_signature” reworded the description of “mediaFile3” cosmetic
    • “update_signature” reworded the description of “mediaFile4” cosmetic
    • “update_signature” reworded the description of “mediaFile5” cosmetic
    • “update_signature” reworded the description of “mediaFile6” cosmetic
    • “update_signature” reworded the description of “mediaFiles” cosmetic
    • “update_signature” reworded the description of “signatureId” cosmetic
    • “update_signature” reworded the description of “title” cosmetic
    • “update_template” reworded the description of “category” cosmetic
    • “update_template” reworded the description of “description” cosmetic
    • “update_template” reworded the description of “documentJson” cosmetic
    • “update_template” reworded the description of “locale” cosmetic
    • “update_template” reworded the description of “name” cosmetic
    • “update_template” reworded the description of “templateId” cosmetic
    • “update_workspace” reworded the description of “cadencePerWeek” cosmetic
    • “update_workspace” reworded the description of “remindersEnabled” cosmetic
  • 15 Oct 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “create_post_draft” rewrote its description, which is the text the model reads security
    • Tool “show_post_card” rewrote its description, which is the text the model reads security
  • 14 Oct 26 0
    • Resource “postlyra-post-card” now points somewhere else: ui://postlyra/post-card/v6.html → ui://postlyra/post-card/v7.html security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “attach_media_to_draft” rewrote its description, which is the text the model reads security
    • Tool “create_post_draft” rewrote its description, which is the text the model reads security
    • Tool “get_auth_status” rewrote its description, which is the text the model reads security
    • Tool “publish_post” rewrote its description, which is the text the model reads security
    • Tool “update_post_draft” rewrote its description, which is the text the model reads security
    • Schema quality: 7380 → 8173 ▼ functional
    • New tool “get_postlyra_guide” functional
    • “list_publications” added an optional parameter “sort” cosmetic
    • “publish_post” added an optional parameter “dryRun” cosmetic
    • “publish_post” added an optional parameter “expectedRevision” cosmetic
    • “publish_post” reworded the description of “confirmationText” cosmetic
    • “publish_post” reworded the description of “confirmed” cosmetic
    • “update_post” reworded the description of “inlineButtons” cosmetic
  • 13 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Server version: 0.3.6 → 0.3.7 functional
  • 12 Oct 26 +1
    • Stability: 0.97 → pass security
  • 10 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “convert_draft_to_signature”, which the server declares destructive security
    • New tool “delete_signature”, which the server declares destructive security
    • New tool “update_signature”, which the server declares destructive security
    • Schema quality: 5618 → 7293 ▼ functional
    • New tool “assign_signature” functional
    • New tool “create_signature” functional
    • New tool “get_signature” functional
    • New tool “list_signatures” functional
    • New tool “preview_signature” functional
    • “create_post_draft” added an optional parameter “signatureSelection” cosmetic
    • “preview_post” added an optional parameter “channelId” cosmetic
    • “update_post_draft” added an optional parameter “signatureSelection” cosmetic
Diagnostics

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://postlyra.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=postlyra.app CN=YE2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA384 6c4de492b656afcc21c4d720d2096e58a87
SANs: postlyra.app, www.postlyra.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of postlyra.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
postlyra.app. 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 tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://postlyra.app/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://postlyra.app/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://postlyra.app/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://postlyra.app/mcp
Authorisation server https://postlyra.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://postlyra.app/mcp Verified 200
http (plaintext) http://postlyra.app/mcp HTTPS enforced 301 https://postlyra.app/mcp
MCP tools · 41 exposed · ~6,966 tokens

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 →

Tool Tokens
update_signature ~434

Use this when managing post auto-signatures. Edit an owner-bound reusable auto-signature; changes affect future publications using it. Already queued and published snapshots retain their original signature. Read get_signature first. Never publishes.

NameTypeReqDescription
inlineButtonsarray–Separate Telegram keyboard rows; use url or one supported action per button. RichDocument buttons use type/value instead.
languagestring–Content language: ru/Russian or en/English.
mediaFile1object–Client-uploaded JPEG/PNG/GIF/WebP image, <=10 MiB; bind this slot in media.src. See get_formatting_capabilities.
mediaFile2object–Client-uploaded JPEG/PNG/GIF/WebP image, <=10 MiB; bind this slot in media.src. See get_formatting_capabilities.
mediaFile3object–Client-uploaded JPEG/PNG/GIF/WebP image, <=10 MiB; bind this slot in media.src. See get_formatting_capabilities.
mediaFile4object–Client-uploaded JPEG/PNG/GIF/WebP image, <=10 MiB; bind this slot in media.src. See get_formatting_capabilities.
mediaFile5object–Client-uploaded JPEG/PNG/GIF/WebP image, <=10 MiB; bind this slot in media.src. See get_formatting_capabilities.
mediaFile6object–Client-uploaded JPEG/PNG/GIF/WebP image, <=10 MiB; bind this slot in media.src. See get_formatting_capabilities.
mediaFilesarray–Actual client-uploaded image files; at most six total across this array and mediaFile1..6. Bind via mediaFiles[0] etc. in richDocument.
richDocumentobject–Complete reusable RichDocument. Use get_formatting_capabilities and the same media slot bindings as post drafts.
signatureIdstringyesOwner-bound signatureId from list_signatures/create_signature.
titlestring–Saved-item title, e.g. Weekly recap.
NameTypeReqDescription
displayobject––
documentJsonobject––
inlineButtonsarray––
localestring––
messagestringyes–
previewUrlstring|null––
richHtmlstring––
screenshotobject––
screenshotUrlstring|null––
signatureobjectyes–
signatureIdstringyes–
textstring––
titlestring––
updatedAtstring––

No examples provided.

update_template ~137

Use when changing the author's saved template. System templates and other users' templates cannot be edited.

NameTypeReqDescription
categorystring–Template category label, e.g. news.
descriptionstring–Short description of the template purpose.
documentJsonobject–Complete RichDocument working layout; see get_formatting_capabilities for syntax and preserve untouched blocks when replacing.
localestring–Language code, e.g. en or ru.
namestring–Name for the personal template, e.g. Weekly recap.
templateIdstringyesTemplate id returned by list_templates; select an owner-visible template.
NameTypeReqDescription
dataobjectyes–
messagestringyes–

No examples provided.

update_workspace ~102

Use when the author asks to change the account time zone, weekly publication target or content reminder preference. Does not change existing publication times.

NameTypeReqDescription
cadencePerWeekinteger–Desired weekly publication target, from 0 to 70; used for planning reminders.
remindersEnabledboolean–Whether content-planning reminders are enabled for this account.
timezonestring–IANA zone, for example Asia/Bangkok; publication times are stored in UTC.
NameTypeReqDescription
dataobjectyes–
messagestringyes–

No examples provided.

Install

How do I install the Postlyra MCP server?

Postlyra is a hosted endpoint at https://postlyra.app/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 · postlyra.app

# add to Claude Code
claude mcp add --transport http prof-1t-postlyra-mcp 'https://postlyra.app/mcp'
Common questions

What is the Postlyra MCP server?

Postlyra is an MCP server listed in the public MCP registry as io.github.prof-1t/postlyra-mcp. Manage Telegram drafts, media, schedules and publications from AI clients. This page covers its hosted endpoint (https://postlyra.app/mcp).

Is the Postlyra MCP server safe to use?

Postlyra scores 92 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 Postlyra MCP server expose?

Postlyra exposes 41 tools: get_auth_status, get_postlyra_guide, get_formatting_capabilities, list_channels, list_templates, and 36 more. Their descriptions and schemas cost roughly 6,966 tokens of context every time the server is loaded.

Does the Postlyra MCP server require authentication?

Yes. Postlyra 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 Postlyra MCP server still maintained?

Postlyra 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.