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.

Appie.run

REMOTE · APPIE.RUN

Reddit threads and reply drafts, LinkedIn leads, on-brand articles, chatbots and short links.

Available components

60 Trust /100

Last scanned (15 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 16 Oct 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 Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1108 tokens (~79/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ask_chatbot" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 16 Oct 26 60

    First indexed and scored.

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 16 Oct 2026 · Probed https://appie.run/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=appie.run CN=WE1,O=Google Trust Services,C=US 9 Sept 2026 8 Dec 2026 ECDSA 256 ECDSA-SHA256 817f36395b2897170edf02f210a3c68a
SANs: appie.run, *.appie.run
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 appie.run. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
run. present 37315 8 Verified
appie.run. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'self' https:; script-src 'self' https: 'unsafe-inline' 'unsafe-eval'; style-src 'self' https: 'unsafe-inline'; frame-ancestors 'self' https://admin.shopify.com https://*.myshopify.com
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://appie.run/mcp Verified 200
http (plaintext) http://appie.run/mcp HTTPS enforced 301 https://appie.run/mcp
MCP tools · 14 exposed · ~1,108 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
add_author_sample ~94

Add a writing sample to an author so create_article can use that voice. Text is ready immediately. A blog URL is processed in the background.

NameTypeReqDescription
author_idintegeryes–
blog_urlstring–http(s) URL of a writing sample. Processed in the background.
contentstring–At least 100 characters. Omit when using blog_url.
titlestring––

No output schema declared.

No examples provided.

add_chatbot_content ~125

Add knowledge to a chatbot. content_type is text, url, sitemap, or article. Text and articles are pasted in. url and sitemap are crawled in the background. Poll chatbot_status until training is complete.

NameTypeReqDescription
article_idinteger–Content Writer article in this project. Required when content_type is article.
chatbot_idintegeryes–
contentstring–Required when content_type is text.
content_typestringyes–
titlestring––
urlstring–Required when content_type is url or sitemap.

No output schema declared.

No examples provided.

article_status ~36

Status and content of an article in this project. Does not spend credits.

NameTypeReqDescription
idintegeryesArticle id returned by create_article.

No output schema declared.

No examples provided.

ask_chatbot ~57

Send a message to a project chatbot and return the reply. Costs 1 credit(s).

NameTypeReqDescription
chatbot_idintegeryes–
messagestringyes–
session_idinteger–Omit to start a new conversation.

No output schema declared.

No examples provided.

chatbot_status ~29

Training status and sources for one chatbot. Does not spend credits.

NameTypeReqDescription
chatbot_idintegeryes–

No output schema declared.

No examples provided.

create_article ~121

Start an article in an author's voice. Pass author_id from list_authors, or omit it to use the active author. Generation is asynchronous. A light article costs 100 credits and a deep article costs 500, charged when generation runs. Poll article_status.

NameTypeReqDescription
article_typestring–light is about 500 words. deeply_researched is about 3000 words. Defaults to light.
author_idinteger–Author profile to write as. Defaults to the project's active author.
topicstringyesWhat the article should cover.

No output schema declared.

No examples provided.

create_author ~98

Create an author profile. Bio must be at least 50 characters. Optionally include a writing sample of at least 100 characters so create_article can use this voice.

NameTypeReqDescription
author_namestringyes–
biostringyesAt least 50 characters.
is_activeboolean–Defaults to true.
sample_contentstring–Optional writing sample, at least 100 characters.
sample_titlestring––

No output schema declared.

No examples provided.

create_chatbot ~84

Create a chatbot for this project. Creation is free. Add knowledge with add_chatbot_content, then call ask_chatbot.

NameTypeReqDescription
namestringyes–
openai_modelstring––
system_promptstring–Instructions for how the bot should answer.
temperaturenumber–0 to 1. Defaults to 0.2.

No output schema declared.

No examples provided.

create_short_link ~66

Create a short link for this project. Costs 1 credit(s).

NameTypeReqDescription
codestring–Optional custom code, 4 to 32 letters, numbers, underscores, or hyphens.
long_urlstringyesDestination URL, including http:// or https://.

No output schema declared.

No examples provided.

get_brain ~40

Read this project's Brain: website, about text, brand voice, key messages, ideal customer, and competitors. Content Writer and chatbots use this context.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

link_stats ~58

Click totals and a 30-day series for one short link in this project. Does not spend credits.

NameTypeReqDescription
codestring–Short code, used when id is omitted.
idinteger–Link id returned by create_short_link.

No output schema declared.

No examples provided.

list_authors ~26

List author profiles for this project, including whether each one is ready for create_article.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_chatbots ~22

List chatbots in this project and whether their knowledge is ready.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_brain ~252

Update this project's Brain. Send only the fields to change. Brand voice values are 0 to 100. category is one of: ecommerce, content, b2b_sales, portfolio, blog, news, corporate, saas, marketplace, other. icp_gender is male, female, or all.

NameTypeReqDescription
about_websitestring–What the company or website does.
app_urlstring––
brand_font_familystring––
brand_font_sizestring––
brand_logo_urlstring––
brand_primary_colorstring––
brand_secondary_colorstring––
brand_voiceobject–Each value is 0 to 100.
categorystring––
competitorsarray––
icp_age_rangestring––
icp_descriptionstring––
icp_genderstring––
icp_geographystring––
icp_secondary_geographystring––
key_messagingarray––
shopping_feed_urlstring––
sitemap_urlstring––
website_urlstring––

No output schema declared.

No examples provided.

Install

How do I install the Appie.run MCP server?

Appie.run is a hosted endpoint at https://appie.run/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 · appie.run

# add to Claude Code
claude mcp add --transport http appierun-appie 'https://appie.run/mcp'
Common questions

What is the Appie.run MCP server?

Appie.run is an MCP server listed in the public MCP registry as io.github.appierun/appie. Reddit threads and reply drafts, LinkedIn leads, on-brand articles, chatbots and short links. This page covers its hosted endpoint (https://appie.run/mcp).

Is the Appie.run MCP server safe to use?

Appie.run scores 60 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 Appie.run MCP server expose?

Appie.run exposes 14 tools: create_short_link, link_stats, create_article, article_status, list_authors, and 9 more. Their descriptions and schemas cost roughly 1,108 tokens of context every time the server is loaded.

Does the Appie.run MCP server require authentication?

No. We connected to Appie.run without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Appie.run MCP server still maintained?

Appie.run is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.