ai.artemisgtm/gtm-engineer
REMOTE · ARTEMISGTM.AI
GTM engineering consulting firm for seed to Series C startups. We build and run GTM systems.
Available components
Last scanned (1 hour ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 508 tokens (~101/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 16 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 25 Oct 26 −3
- Stability: 0.13 → fail ▼ security
- Tool “claim_free_agent” was removed ▼ security
- Tool “get_install_command” was removed ▼ security
- Tool “list_agents” was removed ▼ security
- Tool “recommend_agent” was removed ▼ security
- Tool “start_purchase” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 118 → 101 ▲ functional
- Schema quality: excellent → good functional
- Server version: 1.0.0 → 2.0.0 functional
- New tool “book_evaluation” functional
- New tool “describe_firm” functional
- New tool “get_resources” functional
- New tool “list_systems” functional
- New tool “recommend_engagement” functional
- 23 Oct 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.
- 21 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 67
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 5 Nov 2026 · Probed https://artemisgtm.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=artemisgtm.ai | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a88cf00b32d27ff3df2ad5a955206b22b0 |
| SANs: artemisgtm.ai, www.artemisgtm.ai | ||||||
| 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 insecure
Validation of artemisgtm.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| artemisgtm.ai. | 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=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://artemisgtm.ai/mcp | Verified | 200 | |
| http (plaintext) | http://artemisgtm.ai/mcp | HTTPS enforced | 301 | https://artemisgtm.ai/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 →
book_evaluation ~90
The evaluation booking link for Artemis GTM and what happens on the call: Tom Regan walks the motion, names the biggest leak visible from the outside and says whether an engagement fits; the caller leaves with a written scoping note and, if it fits, a custom quote. This tool books nothing itself.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional: the problem or company in one line, echoed back. |
No output schema declared.
No examples provided.
describe_firm ~80
What Artemis GTM is: an AI GTM engineering firm for seed to Series C B2B startups, who founded it, what it builds, how it builds (its proprietary agent architecture, never sold or installed), what clients keep, how an engagement starts, how it is priced (custom, scoped on an evaluation call) and the booking link.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_resources ~76
The free guides on artemisgtm.ai, by topic (speed to lead, lead scoring and handoff, visitor identification, ICP, outbound, data and reporting), for a person who is not ready for an engagement.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional: a topic word to filter the guides, for example "outbound". |
No output schema declared.
No examples provided.
list_systems ~49
The GTM systems Artemis GTM builds inside a client's own CRM and tools, each with the problem it fixes, what gets built and the related free guides. No prices: every engagement is custom.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_engagement ~100
Given a B2B go-to-market problem in plain language (for example "leads sit for two days before anyone calls them", "most of our website traffic is anonymous", "our ICP is too broad"), name the system Artemis GTM would build to fix it, why, up to two alternates, the related guides and the next step: an evaluation call.
| Name | Type | Req | Description |
|---|---|---|---|
| problem | string | yes | The GTM problem, described in plain language. |
No output schema declared.
No examples provided.
How do I install the ai.artemisgtm/gtm-engineer MCP server?
ai.artemisgtm/gtm-engineer is a hosted endpoint at https://artemisgtm.ai/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 · artemisgtm.ai
claude mcp add --transport http ai-artemisgtm-gtm-engineer 'https://artemisgtm.ai/mcp'
What is the ai.artemisgtm/gtm-engineer MCP server?
ai.artemisgtm/gtm-engineer is an MCP server listed in the public MCP registry as ai.artemisgtm/gtm-engineer. GTM engineering consulting firm for seed to Series C startups. We build and run GTM systems. This page covers its hosted endpoint (https://artemisgtm.ai/mcp).
Is the ai.artemisgtm/gtm-engineer MCP server safe to use?
ai.artemisgtm/gtm-engineer scores 66 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 ai.artemisgtm/gtm-engineer MCP server expose?
ai.artemisgtm/gtm-engineer exposes 5 tools: describe_firm, list_systems, recommend_engagement, book_evaluation, get_resources. Their descriptions and schemas cost roughly 395 tokens of context every time the server is loaded.
Does the ai.artemisgtm/gtm-engineer MCP server require authentication?
No. We connected to ai.artemisgtm/gtm-engineer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.artemisgtm/gtm-engineer MCP server still maintained?
ai.artemisgtm/gtm-engineer 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.