WriteHero: LinkedIn post checker
REMOTE · WRITEHERO.IO
Check, format and preview LinkedIn posts: limits, see-more cut, hooks, AI-sounding phrases.
Available components
Last scanned (19 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 794 tokens (~132/item across 6 items; 6 tools + 0 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 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 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 71
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 4 Nov 2026 · Probed https://writehero.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=writehero.io | CN=YE2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6339b566f34ba2c7ce44f00ea3aef63f0e7 |
| SANs: *.writehero.io, writehero.io | ||||||
| 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 writehero.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| writehero.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://writehero.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://writehero.io/api/mcp | HTTPS enforced | 301 | https://writehero.io/api/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 →
check_linkedin_post Check a LinkedIn post ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| post | string | yes | The full post text. |
No output schema declared.
No examples provided.
format_linkedin_post Format a post for LinkedIn ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| post | string | yes | Post text, Markdown allowed. |
| replace_em_dashes | boolean | – | Replace em dashes with commas. |
No output schema declared.
No examples provided.
generate_linkedin_headlines LinkedIn headline options ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who the user helps. |
| goal | string | – | clients: win clients; job: get hired; general: both. |
| keywords | string | – | Skills people search for. |
| outcome | string | – | The result they deliver, e.g. book more sales calls. |
| proof | string | – | A credential or result they can verify. |
| role | string | yes | Current or target job title. |
| tone | string | – | warm phrases the value as "Helping..."; plain and bold as "I help...". |
No output schema declared.
No examples provided.
generate_linkedin_hooks LinkedIn hook ideas ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who the post is for, e.g. founders. |
| result | string | – | A real result the user can back up, e.g. hired 4 engineers in 30 days. |
| topic | string | yes | What the post is about, e.g. hiring engineers. |
No output schema declared.
No examples provided.
preview_linkedin_post Preview a LinkedIn post ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| author_headline | string | – | Headline shown under the name. |
| author_name | string | – | Name shown on the preview. |
| post | string | yes | The post text. |
No output schema declared.
No examples provided.
style_linkedin_text Bold, italic or strikethrough text ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| style | string | – | Style to apply. |
| text | string | yes | The words to restyle. |
No output schema declared.
No examples provided.
How do I install the WriteHero: LinkedIn post checker MCP server?
WriteHero: LinkedIn post checker is a hosted endpoint at https://writehero.io/api/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 · writehero.io
claude mcp add --transport http io-writehero-linkedin 'https://writehero.io/api/mcp'
What is the WriteHero: LinkedIn post checker MCP server?
WriteHero: LinkedIn post checker is an MCP server listed in the public MCP registry as io.writehero/linkedin. Check, format and preview LinkedIn posts: limits, see-more cut, hooks, AI-sounding phrases. This page covers its hosted endpoint (https://writehero.io/api/mcp).
Is the WriteHero: LinkedIn post checker MCP server safe to use?
WriteHero: LinkedIn post checker scores 74 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 WriteHero: LinkedIn post checker MCP server expose?
WriteHero: LinkedIn post checker exposes 6 tools: check_linkedin_post, format_linkedin_post, style_linkedin_text, generate_linkedin_hooks, generate_linkedin_headlines, preview_linkedin_post. Their descriptions and schemas cost roughly 639 tokens of context every time the server is loaded.
Does the WriteHero: LinkedIn post checker MCP server require authentication?
No. We connected to WriteHero: LinkedIn post checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WriteHero: LinkedIn post checker MCP server still maintained?
WriteHero: LinkedIn post checker is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.