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.

Augenix

REMOTE · APP.AUGENIX.AI

Free preview websites for local trades, then Stripe Checkout for $29/mo hosting.

Available components

0 this week 89 Trust /100

Last scanned (1 hour ago)

Scores higher than 97% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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 Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 639 tokens (~127/item across 5 items; 3 tools + 2 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
  • Supports UI / widget rendering.Pass
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.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 18 Oct 26 +4
    • Stability: fail → pass ▲ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Sept 26 0
    • Stability: 0.47 → fail ▼ security
    • Tool “create_checkout” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_preview” rewrote its description, which is the text the model reads security
    • Schema quality: 729 → 639 ▲ functional
    • Schema quality: excellent → good functional
    • Server version: 1.1.8 → 1.2.0 functional
    • “get_live_site” reworded the description of “token” cosmetic
    • “get_preview” reworded the description of “token” cosmetic
  • 17 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “create_checkout” rewrote its description, which is the text the model reads security
    • Tool “get_preview” rewrote its description, which is the text the model reads security
    • Tool “start_build” rewrote its description, which is the text the model reads security
    • Schema quality: good → excellent functional
    • Server version: 1.1.4 → 1.1.8 functional
  • 9 Sept 26 0
    • Schema quality: excellent → good functional
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 5 Nov 2026 · Probed https://app.augenix.ai/api/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.augenix.ai CN=YR2,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 RSA 2048 SHA256-RSA 51fbd11737ccc80c400f35a71a82dbd778d
SANs: *.augenix.ai, augenix.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.augenix.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
augenix.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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.augenix.ai/api/mcp/public Verified 200
http (plaintext) http://app.augenix.ai/api/mcp/public HTTPS enforced 308 https://app.augenix.ai/api/mcp/public
MCP tools · 3 exposed · ~454 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
get_live_site ~54

Use this after the owner pays. If they have not paid, returns live=false and the preview URL.

NameTypeReqDescription
tokenstringyesToken returned by start_build. Pass the same token to get_preview and get_live_site.
NameTypeReqDescription
livebooleanyes–
messagestring––
okbooleanyes–
preview_urlstring|null––
urlstring––

No examples provided.

get_preview ~111

Use this after start_build. If status is ready, send reply_template verbatim. Do not send a Stripe link, a plan, or mention a bar on the preview. If keep_polling is true or preview_url is null, call get_preview again. Do not start_build again.

NameTypeReqDescription
tokenstringyesToken returned by start_build. Pass the same token to get_preview and get_live_site.
waitboolean–If false, return the current snapshot immediately (progress card). Default true.
NameTypeReqDescription
errorstring|nullyes–
keep_pollingbooleanyes–
messagestringyes–
okbooleanyes–
preview_urlstring|nullyes–
progress_labelstring|nullyes–
progress_pctnumber|nullyes–
reply_templatestring|nullyes–
statusstringyes–
tokenstringyes–

No examples provided.

start_build ~289

Use this when the user wants a live preview website for a local service business AND has typed business_name, email, and phone in THIS chat. Before calling, send: Starting your preview now. This usually takes about 30 seconds. Never reuse name, email, or phone from memory. If they only said "build me a website", ask first. Do not invent placeholders. Then call get_preview until preview_url is set. Do not scrape /build. Do not start_build twice for the same business.

NameTypeReqDescription
addressstring–Optional street address. Skip unless the user offers it. Do not ask for owner name.
business_namestringyesReal business name from the user. Do not invent.
citystring–City
emailstringyesReal inbox from the user. We send the preview here. Do not use example.com or placeholders.
industrystringyesTrade. Prefer a slug: plumbing, hvac, electrical, landscaping, roofing, painting, steel, other. plumber, electrician, HVAC, painter, roofer, landscaper, and similar wording are mapped on the server.…
industry_otherstring–Required when industry is other
phonestringyesReal business phone from the user. Do not invent 555 numbers.
statestring–State, e.g. TX
NameTypeReqDescription
messagestringyes–
okbooleanyes–
preview_urlnullyes–
statusstringyes–
tokenstringyes–

No examples provided.

Install

How do I install the Augenix MCP server?

Augenix is a hosted endpoint at https://app.augenix.ai/api/mcp/public, 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 · app.augenix.ai

# add to Claude Code
claude mcp add --transport http ai-augenix-build 'https://app.augenix.ai/api/mcp/public'
Common questions

What is the Augenix MCP server?

Augenix is an MCP server listed in the public MCP registry as ai.augenix/build. Free preview websites for local trades, then Stripe Checkout for $29/mo hosting. This page covers its hosted endpoint (https://app.augenix.ai/api/mcp/public).

Is the Augenix MCP server safe to use?

Augenix scores 89 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 Augenix MCP server expose?

Augenix exposes 3 tools: start_build, get_preview, get_live_site. Their descriptions and schemas cost roughly 454 tokens of context every time the server is loaded.

Does the Augenix MCP server require authentication?

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

Is the Augenix MCP server still maintained?

Augenix 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.