io.github.shashwatgtm/craft-content-mcp
REMOTE · CRAFT-CONTENT.GTMHELIX.COM · 2 COMPONENTS
CRAFT Content: 8 B2B content tools by Helix GTM Consulting
Available components
Last scanned (23 hours ago)
Scores higher than 79% 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 Security83
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3121 tokens (~390/item across 8 items; 8 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 Management54
- Stability check failed: schema churn in the 18 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.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 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50.
- 2 Nov 26 0
- Tool “newsletter_builder” rewrote its description, which is the text the model reads security
- Tool “testimonial_capture” rewrote its description, which is the text the model reads security
- Tool “webinar_script” rewrote its description, which is the text the model reads security
- Tool “case_study_generator” rewrote its description, which is the text the model reads security
- Tool “thought_leadership_series” rewrote its description, which is the text the model reads security
- Tool “content_repurposer” rewrote its description, which is the text the model reads security
- Schema quality: 349 → 390 ▼ functional
- “content_repurposer” added an optional parameter “publication_approval” cosmetic
- “newsletter_builder” added an optional parameter “publication_approval” cosmetic
- “testimonial_capture” added an optional parameter “customer_status” cosmetic
- “testimonial_capture” added an optional parameter “publication_approval” cosmetic
- “thought_leadership_series” added an optional parameter “publication_approval” cosmetic
- “webinar_script” added an optional parameter “publication_approval” cosmetic
- “case_study_generator” added an optional parameter “publication_approval” cosmetic
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 34.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 24 to 27.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 14.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 4.
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://craft-content.gtmhelix.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=craft-content.gtmhelix.com | CN=YE1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 69dc638bdb4108859e5dc34591ac8cc2c84 |
| SANs: craft-content.gtmhelix.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 secure
Validation of craft-content.gtmhelix.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gtmhelix.com. | present | 23401, 43960 | 13, 13 | Verified |
| craft-content.gtmhelix.com. | Verified address RRset verified with the apex keys |
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=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://craft-content.gtmhelix.com/mcp | Verified | 200 | |
| http (plaintext) | http://craft-content.gtmhelix.com/mcp | HTTPS enforced | 301 | https://craft-content.gtmhelix.com/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 →
case_study_generator Case Study Generator ~420
Builds a customer case study from the customer name, your product and the challenge, solution and results you give (mode full), or an interview kit for collecting them (mode discovery). Optional customer industry, quote, interview notes and business model fit the wording to the customer. Returns a headline, the story with each result you list, a customer quote, social and email copy and sector notes when the sector can be read from your text. A bracket marks anything you did not give. Ask whether written customer approval covers the exact material and intended use.
| Name | Type | Req | Description |
|---|---|---|---|
| business_model | string | – | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| challenge | string | – | The customer's challenge or problem (needed in full mode) |
| customer_industry | string | – | The customer's industry, used for context |
| customer_name | string | yes | Customer or company name |
| customer_quote | string | – | Optional: a direct quote from the customer |
| interview_notes | string | – | Optional: raw interview notes or a transcript. In full mode they fill a missing challenge, solution or results; the answer says they were not used when you gave all three |
| mode | string | – | full builds the case study and needs the challenge, solution and results; discovery returns interview questions for collecting them |
| publication_approval | string | – | Optional confirmed written approval for this exact customer name, figures, quote and intended use. Ask before publication. A draft cannot grant customer permission. |
| results | string | – | Measurable outcomes, one per line or per semicolon (needed in full mode) |
| solution | string | – | How your product solved it (needed in full mode) |
| your_product | string | yes | Your product or service name |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
No output schema declared.
No examples provided.
content_repurposer Content Repurposer ~357
Turns a source text into finished versions for other channels: a LinkedIn post, an X thread, an email, a blog summary and quote cards. Needs the source text and its type. Optional target formats, brand voice and a key message steer the result. Each version is written from whole sentences of your source, with key points chosen by a stated rule and kept in the source order; claims it cannot support are listed to source, and any requested format it does not know is named. Returns the versions, notes on the key points and proof used, and sector notes. Ask whether written customer approval covers the exact material and intended use.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_voice | string | – | The brand voice to keep |
| key_message | string | – | Optional: the core message to emphasize in every format |
| publication_approval | string | – | Optional confirmed written approval for this exact customer name, figures, quote and intended use. Ask before publication. A draft cannot grant customer permission. |
| source_content | string | yes | The original content to repurpose (a blog post, article or transcript, for example) |
| source_type | string | yes | The kind of content the source is |
| target_formats | string | – | Optional: formats to generate, comma-separated. Defaults to: linkedin_post, twitter_thread, email, blog_summary, quote_cards. Other options: infographic_outline, video_script, podcast_talking_points,… |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
No output schema declared.
No examples provided.
craft_content_improver CRAFT Content Improver ~276
Reviews pasted copy and its content type against listed rules: buzzwords, claims that need proof, fragments, unfilled merge fields, claims about the reader and a missing figure or ask. Optional goal, audience and tone preference refine the review. Returns a score for each area with each deduction quoted from your text, and the edits it made. If it finds no edit to make, it says so and prints no improved version.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Optional: who the content is for. The review reports when the text never mentions them |
| content | string | yes | The content to review |
| content_type | string | yes | The kind of content; it changes which checks apply |
| goal | string | – | Optional: what the content should achieve (for example 'book a first meeting' or 'educate readers'). If not given, a goal is chosen from the content type |
| tone_preference | string | – | The tone you want. Only more_formal and more_casual are checked in the text; any other value is named in the answer as not used |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
No output schema declared.
No examples provided.
newsletter_builder Newsletter Builder ~408
Writes a first draft of a newsletter issue from your topic and the action you want readers to take. Optional key points, audience segment, newsletter type, tone, earlier topics and your product fit it to the reader. Returns a subject line and preview, an opening, a short section for each key point, your own call to action as the button, A/B subject lines, alternative opening hooks and sector notes. Without key points it suggests some from the topic and sector. The draft uses only what you gave: it adds no statistic or customer story, and says what it did not get. Ask whether written customer approval covers the exact material and intended use.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_segment | string | – | Who the newsletter is for; sets tone and depth |
| cta_goal | string | yes | The action readers should take, in your own words (for example 'register for the webinar', 'book a call', 'read the guide'); it becomes the button |
| key_points | string | – | Optional: key points to cover, one per line, per semicolon or comma-separated. If not provided, points are suggested from the topic and newsletter type |
| newsletter_type | string | – | The kind of newsletter |
| previous_topics | string | – | Optional: recent newsletter topics, to avoid repetition and suggest connections |
| publication_approval | string | – | Optional confirmed written approval for this exact customer name, figures, quote and intended use. Ask before publication. A draft cannot grant customer permission. |
| tone | string | – | The writing tone |
| topic | string | yes | The main topic or theme of the newsletter |
| your_product | string | – | Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder. |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
No output schema declared.
No examples provided.
sales_enablement_content Sales Enablement Content ~371
Builds a sales kit from your product, the persona you sell to and your proof points. Optional objections, value propositions, competitor objections, price context, sales stage and business model shape it. Returns a pitch order, a script for each objection answered with the sector's pattern and the proof point that fits it, competitor responses, discovery questions and follow-up templates. Without objections it suggests the ones your sector raises.
| Name | Type | Req | Description |
|---|---|---|---|
| business_model | string | – | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| common_objections | string | – | Optional: sales objections you hear, one per line, per semicolon or comma-separated. If not provided, likely objections for your sector are suggested |
| competitor_objections | string | – | Optional: 'why not [competitor]' objections |
| price_context | string | – | Optional: your pricing against the market (for example 'Premium, above market', 'Budget option' or 'Mid-market') |
| product | string | yes | The product name and what it does |
| proof_points | string | yes | Evidence for your claims: case studies, metrics and quotes, one per line, per semicolon or comma-separated |
| sales_stage | string | – | The stage of the sales funnel |
| target_persona | string | yes | Who sales is pitching to (role and company type) |
| value_props | string | – | Optional: key value propositions, one per line, per semicolon or comma-separated. Taken from the proof points if not provided |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
No output schema declared.
No examples provided.
testimonial_capture Testimonial Capture ~408
Prepares a testimonial request from the customer's name, company, success story and the type of testimonial you want. Optional role, relationship, intended use, incentive, your product and business model fit it to the customer. Returns a request email, interview questions for the customer's role and sector, quote drafts for the customer to edit and a sign-off checklist. It uses your product name when you give it and says so when you do not. Ask whether written customer approval covers the exact material and intended use.
| Name | Type | Req | Description |
|---|---|---|---|
| business_model | string | – | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| customer_company | string | yes | The customer's company |
| customer_name | string | yes | The customer's name |
| customer_role | string | – | The customer's job title |
| customer_status | string | – | Ask whether the customer is active or cancelled before a testimonial request. A confirmed typed fact takes precedence over cancellation wording. |
| incentive | string | – | Optional: what you are offering in return |
| publication_approval | string | – | Optional confirmed written approval for this exact customer name, figures, quote and intended use. Ask before publication. A draft cannot grant customer permission. |
| relationship_context | string | – | How long they have been a customer and the key interactions |
| success_story | string | yes | A short description of their success with your product |
| testimonial_type | string | yes | The kind of testimonial you need |
| use_case | string | – | Where the testimonial will be used (the website or a sales deck, for example) |
| your_product | string | – | Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder. |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
No output schema declared.
No examples provided.
thought_leadership_series Thought Leadership Series ~415
Writes a first draft of each article in a thought leadership series from your topic, your take and the reader you write for. Optional proof points, author background, number of articles and article style shape them. Returns, for each article, a headline, a short draft with the objection it answers, your proof and a way to test the idea, a promotional post for each article, a publishing order and sector notes. Your take and proof points are quoted as you wrote them and no result, customer or figure is invented. Without proof points it names the evidence to gather. Ask whether written customer approval covers the exact material and intended use.
| Name | Type | Req | Description |
|---|---|---|---|
| article_type | string | – | The style of the articles |
| author_background | string | – | Optional: your role and why you are credible (for example 'a long career in enterprise sales') |
| num_articles | integer | – | How many articles to outline, a whole number from 1 to 5. If left out, the series has three articles |
| proof_points | string | – | Optional: evidence supporting your take: personal stories, client examples, data or stats, one per line, per semicolon or comma-separated. If not provided, proof points to gather are suggested |
| publication_approval | string | – | Optional confirmed written approval for this exact customer name, figures, quote and intended use. Ask before publication. A draft cannot grant customer permission. |
| target_reader | string | yes | Who should read this, named specifically (for example 'Heads of IT at companies with many branches' rather than 'managers') |
| topic | string | yes | The topic you want to build authority on |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
| your_take | string | yes | Your own view on this topic: what you believe that others do not, or your contrarian view |
No output schema declared.
No examples provided.
webinar_script Webinar Script ~466
Writes a webinar run of show and a full spoken script from your topic, target audience and webinar type. Optional duration, key takeaways, speakers, polls, product mention level, your product and business model shape it. Returns the run of show, the script with the speaker lines and on-screen cues for each segment built from your takeaways and speakers, polls with answer options, anticipated questions with answers, a follow-up email sequence and sector notes. Without key takeaways it suggests them from the topic and type. The script uses only what you gave and says what it did not get. Ask whether written customer approval covers the exact material and intended use.
| Name | Type | Req | Description |
|---|---|---|---|
| business_model | string | – | Optional: how you charge, so the advice fits it. If omitted, it is read from your text and the answer says how. |
| duration | string | – | The webinar length |
| include_polls | boolean | – | Include poll suggestions with answer options |
| key_takeaways | string | – | Optional: what attendees should learn, one per line, per semicolon or comma-separated. If not provided, takeaways are suggested from the topic |
| product_mention_level | string | – | Whether to add product tie-in placeholders to the script ('none' leaves them out) |
| publication_approval | string | – | Optional confirmed written approval for this exact customer name, figures, quote and intended use. Ask before publication. A draft cannot grant customer permission. |
| speakers | string | – | Optional: speakers as you want them listed. Separate speakers with semicolons or line breaks ('Name, Title; Name, Title'), or with commas if each is one phrase |
| target_audience | string | yes | Who will attend (for example 'Support leaders at consumer apps') |
| topic | string | yes | The webinar topic or title |
| webinar_type | string | yes | The kind of webinar; sets the structure |
| your_product | string | – | Optional: your product or service name, used in the answer. Without it the answer says so and shows a placeholder. |
| your_sector | string | – | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. |
No output schema declared.
No examples provided.
How do I install the io.github.shashwatgtm/craft-content-mcp server?
io.github.shashwatgtm/craft-content-mcp is a hosted endpoint at https://craft-content.gtmhelix.com/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 · craft-content.gtmhelix.com
claude mcp add --transport http shashwatgtm-craft-content-mcp 'https://craft-content.gtmhelix.com/mcp'
What is the io.github.shashwatgtm/craft-content-mcp server?
io.github.shashwatgtm/craft-content-mcp is listed in the public MCP registry as io.github.shashwatgtm/craft-content-mcp. CRAFT Content: 8 B2B content tools by Helix GTM Consulting. This page covers its hosted endpoint (https://craft-content.gtmhelix.com/mcp).
Is the io.github.shashwatgtm/craft-content-mcp server safe to use?
io.github.shashwatgtm/craft-content-mcp scores 79 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.shashwatgtm/craft-content-mcp server expose?
io.github.shashwatgtm/craft-content-mcp exposes 8 tools: case_study_generator, newsletter_builder, webinar_script, content_repurposer, thought_leadership_series, and 3 more. Their descriptions and schemas cost roughly 3,121 tokens of context every time the server is loaded.
Does the io.github.shashwatgtm/craft-content-mcp server require authentication?
No. We connected to io.github.shashwatgtm/craft-content-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.shashwatgtm/craft-content-mcp server still maintained?
io.github.shashwatgtm/craft-content-mcp 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.