Skip to content

WriteHero: LinkedIn post checker

io.writehero/linkedinwritehero.iostreamable-httpv1.0.0Scanned

Check, format and preview LinkedIn posts: limits, see-more cut, hooks, AI-sounding phrases.

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 2
  • 5 findings

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 5Claude Code: ask
  • check_linkedin_postCheck a LinkedIn post before publishing: character count against LinkedIn's 3000-character limit, the text likely shown before "see more" on desktop, a hook score, Markdown that Li…Can send data out1 finding

    Why it is in this group

    • The name "check_linkedin_post" says "post": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "check_linkedin_post" says "post": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "check_linkedin_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_linkedin_post" says "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Check a LinkedIn post before publishing: character count against LinkedIn's 3000-character limit, the text likely shown before "see more" on desktop, a hook score, Markdown that LinkedIn will not render, placeholders, and phrases that read as AI-written. Returns concrete issues to fix.

    Annotations the server declares

    • title: Check a LinkedIn post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • format_linkedin_postConvert Markdown into text that pastes cleanly into LinkedIn: **bold** and headings become Unicode bold, *italic* becomes Unicode italic, list markers become bullets, Markdown link…Can send data out1 finding

    Why it is in this group

    • The name "format_linkedin_post" says "post": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "format_linkedin_post" says "post": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "format_linkedin_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "format_linkedin_post" says "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Convert Markdown into text that pastes cleanly into LinkedIn: **bold** and headings become Unicode bold, *italic* becomes Unicode italic, list markers become bullets, Markdown links become plain URLs. Optionally replaces em dashes.

    Annotations the server declares

    • title: Format a post for LinkedIn
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • generate_linkedin_headlinesProfile headline options built only from the user's role, audience, outcome, proof and keywords.2 findings

    Why it is in this group

    • The name "generate_linkedin_headlines" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.proof.description mentions "credential".

      Matched text

      inputSchema.properties.proof.description: "A credential or result they can verify."

      What this check looks for
    • Warn

      The server marks "generate_linkedin_headlines" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_linkedin_headlines" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Profile headline options built only from the user's role, audience, outcome, proof and keywords. Every option fits LinkedIn's 220-character headline limit. Does not change the profile.

    Annotations the server declares

    • title: LinkedIn headline options
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • generate_linkedin_hooksOpening-line templates for a LinkedIn post, filled with the user's topic, audience and result.1 finding

    Why it is in this group

    • The name "generate_linkedin_hooks" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "generate_linkedin_hooks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_linkedin_hooks" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Opening-line templates for a LinkedIn post, filled with the user's topic, audience and result. Anything the user has not supplied stays in [brackets] to replace with a real detail; nothing is invented.

    Annotations the server declares

    • title: LinkedIn hook ideas
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • style_linkedin_textRestyle a short piece of text with Unicode letters that keep their look when pasted into LinkedIn (bold, italic, bold italic, serif, cursive, strikethrough, underline).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Restyle a short piece of text with Unicode letters that keep their look when pasted into LinkedIn (bold, italic, bold italic, serif, cursive, strikethrough, underline). Use sparingly; screen readers may read styled letters poorly.

    Annotations the server declares

    • title: Bold, italic or strikethrough text
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • preview_linkedin_postReturn a link to an approximate preview of the post in the LinkedIn feed on mobile and desktop, including about where "see more" cuts it.Reads text others writeNo findings

    Why it is in this group

    • The name "preview_linkedin_post" says "preview": a word for reading.

    What it can reach

    • untrusted-inputThe name "preview_linkedin_post" says "preview" and "post": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "return" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Return a link to an approximate preview of the post in the LinkedIn feed on mobile and desktop, including about where "see more" cuts it. Pass author_name and author_headline when you know them. Opening the link saves and publishes nothing. The post text travels in the link, so share it only with people who should read the draft.

    Annotations the server declares

    • title: Preview a LinkedIn post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

4 warn1 info
  • The server marks "check_linkedin_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_linkedin_post" says "post": a word for a change.

    What this check looks for
  • The server marks "format_linkedin_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "format_linkedin_post" says "post": a word for a change.

    What this check looks for
  • The server marks "generate_linkedin_hooks" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_linkedin_hooks" says "generate": a word for a change.

    What this check looks for
  • The server marks "generate_linkedin_headlines" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_linkedin_headlines" says "generate": a word for a change.

    What this check looks for
  • The input schema at properties.proof.description mentions "credential".

    Matched text

    inputSchema.properties.proof.description: "A credential or result they can verify."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http linkedin https://writehero.io/api/mcp
claude mcp add --transport http linkedin https://writehero.io/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__linkedin__preview_linkedin_post"
    ],
    "ask": [
      "mcp__linkedin__check_linkedin_post",
      "mcp__linkedin__format_linkedin_post",
      "mcp__linkedin__style_linkedin_text",
      "mcp__linkedin__generate_linkedin_hooks",
      "mcp__linkedin__generate_linkedin_headlines"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as linkedin. Review it before you use it.

Capability tags behind 3 rules
  • mcp__linkedin__check_linkedin_post outbound
  • mcp__linkedin__format_linkedin_post outbound
  • mcp__linkedin__preview_linkedin_post untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.writehero/linkedin/verify?hash=5b85b988f58afba518a409fe8a8b5af6da559320ce7664ddd3702b44d2e81b60" | jq -e '.changed == false'

Pinned hash 5b85b988f58a, from Oct 29, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.writehero/linkedin/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.writehero/linkedin
[![anlyon.dev](https://anlyon.dev/badge/io.writehero/linkedin.svg)](https://anlyon.dev/servers/io.writehero/linkedin)

Source: MCP Registry. Synced Oct 29, 2026, 06:18 UTC.