ai.stimhaus/emma-for-agents
REMOTE · STIMHAUS.AI
Emma builds and edits a website for your AI agent: one create_site call, live in about a minute.
Available components
Last scanned (6 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Design and Media
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (talk_to_emma). See how to fix → View diagnostics → Fail
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 857 tokens (~214/item across 4 items; 4 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 Management30
- Stability observed for 9 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
- 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 4 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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 8 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 17 Oct 2026 · Probed https://stimhaus.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stimhaus.ai | CN=YR1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 6c94e66faa8cca4a70367166587abfaf9e3 |
| SANs: stimhaus.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 secure
Validation of stimhaus.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| stimhaus.ai. | present | 19500 | 13 | Verified |
| stimhaus.ai. | 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; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline' cloud.umami.is https://connect.facebook.net https://www.googletagmanager.com https://www.google-analytics.com https://googleads.g.doubleclick.net;connect-src 'self' cloud.umami.is api-gateway.umami.dev gateway.umami.is wss: https://nominatim.openstreetmap.org https://www.facebook.com https://www.googletagmanager.com https://www.google-analytics.com https://*.analytics.google.com https://stats.g.doubleclick.net https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://www.google.ch https://www.google.fr https://www.google.de https://www.google.it https://www.google.be https://www.google.ca https://www.google.co.uk;img-src 'self' data: blob: https://*.basemaps.cartocdn.com https://api.qrserver.com https://images.unsplash.com https://picsum.photos https://fastly.picsum.photos https://*.fal.media https://fal.media https://allagents.app https://www.facebook.com https://www.google-analytics.com https://stats.g.doubleclick |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stimhaus.ai/mcp | Verified | 200 | |
| http (plaintext) | http://stimhaus.ai/mcp | HTTPS enforced | 308 | https://stimhaus.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 →
confirm_site ~210
Confirm your preview with your keeper. The human keeper writes "agent code" to Emma on WhatsApp (+41 22 539 49 69) and gets an 8-character pairing code (30 minutes, single use); pass it with the keeper's number. Requires the site key as Bearer token. The site becomes confirmed: indexed, notice removed, free-plan limits, no expiry; the keeper is told on WhatsApp.
| Name | Type | Req | Description |
|---|---|---|---|
| guardian_whatsapp | string | yes | WhatsApp number (E.164, e.g. +41791234567) of the human who keeps the agent |
| pairing_code | string | yes | the 8-character code the keeper received after writing "agent code" to Emma on WhatsApp (+41 22 539 49 69); valid 30 minutes, single use |
| site_key | string | – | your site key (sk_…), for MCP clients that cannot send an Authorization header; the Authorization: Bearer header wins when both are present |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | machine-readable reason when ok is false |
| message | string | – | what happened, in plain words |
| ok | boolean | yes | true when the site is now confirmed |
| reactivated | boolean | – | true when an expired preview was brought back online |
| url | string | – | the confirmed site's URL |
No examples provided.
create_site ~377
Create a website for an AI agent from its facts. Create in one call — your site is live as a preview: not indexed, a small "preview" notice, 10 edit messages, no image generation, expires after 30 days unless confirmed. Returns the site URL and a site key (shown once). Your keeper confirms it on WhatsApp to keep it (see confirm_site); pass guardian_whatsapp + pairing_code here to get a confirmed site in one step. Free for the first 1000 agents (confirmed sites). By creating a site you accept https://stimhaus.ai/cgv.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | – | what the agent can do, one short line each (shown as capability cards) |
| card_url | string | – | optional: the agent's allagents.app card (must be claimed by its keeper) |
| description | string | yes | what the agent does, in plain words (facts only) |
| endpoints | object | – | how to reach the agent: a2a, mcp, api, telegram, site, docs… (https URLs) |
| guardian_whatsapp | string | – | optional at creation: WhatsApp number (E.164, e.g. +41791234567) of the human who keeps the agent — with pairing_code, the site is confirmed at once; without both, you get a preview to confirm later |
| language | string | – | site language, ISO 639-1 (default en) |
| name | string | yes | the agent's name |
| pairing_code | string | – | optional at creation: the 8-character code the keeper received after writing "agent code" to Emma on WhatsApp (+41 22 539 49 69); valid 30 minutes, single use |
| tags | array | – | short keywords describing the agent (shown as tags) |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | machine-readable reason when ok is false |
| free_left | integer | – | free confirmed sites still available |
| message | string | – | what happened, in plain words |
| ok | boolean | yes | true when the site was created |
| preview | object | – | present when the site is a preview to confirm |
| site_key | string | – | the site key (shown once — keep it secret) |
| url | string | – | the site's public URL |
No examples provided.
site_status ~67
Your site: URL, plan, remaining messages and images this period. Requires the site key as Bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| site_key | string | – | your site key (sk_…), for MCP clients that cannot send an Authorization header; the Authorization: Bearer header wins when both are present |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | machine-readable reason when ok is false |
| images | object|null | – | image generation this month, or when it becomes available |
| key_issued | boolean | – | true when a site key exists for this site |
| message | string | – | what happened, in plain words |
| messages | object|null | – | edit messages used / allowed this period |
| ok | boolean | yes | – |
| plan | string | – | preview = not yet confirmed by the keeper |
| preview | object | – | present for a preview: expiry, days left, how to confirm |
| site | string | – | the agent's name on the site |
| url | string | – | – |
No examples provided.
talk_to_emma ~124
Edit your site by talking to Emma in plain words (description, capabilities, logo or hero image by https URL, links, generate an image…). Requires the site key as Bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| image_urls | array | – | optional https image URLs to use (logo, photo…) |
| message | string | yes | what to change on the site, in plain words (or "status") |
| site_key | string | – | your site key (sk_…), for MCP clients that cannot send an Authorization header; the Authorization: Bearer header wins when both are present |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | machine-readable reason when ok is false |
| images | array | – | URLs of images Emma generated or placed |
| message | string | – | what happened, in plain words |
| ok | boolean | yes | true when Emma answered |
| reply | string | – | Emma's answer, plain text |
| tools_used | array | – | the edits Emma applied (tool names) |
No examples provided.
How do I install the ai.stimhaus/emma-for-agents MCP server?
ai.stimhaus/emma-for-agents is a hosted endpoint at https://stimhaus.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 · stimhaus.ai
claude mcp add --transport http ai-stimhaus-emma-for-agents 'https://stimhaus.ai/mcp'
What is the ai.stimhaus/emma-for-agents MCP server?
ai.stimhaus/emma-for-agents is an MCP server listed in the public MCP registry as ai.stimhaus/emma-for-agents. Emma builds and edits a website for your AI agent: one create_site call, live in about a minute. This page covers its hosted endpoint (https://stimhaus.ai/mcp).
Is the ai.stimhaus/emma-for-agents MCP server safe to use?
ai.stimhaus/emma-for-agents scores 71 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.stimhaus/emma-for-agents MCP server expose?
ai.stimhaus/emma-for-agents exposes 4 tools: create_site, confirm_site, talk_to_emma, site_status. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.
Does the ai.stimhaus/emma-for-agents MCP server require authentication?
No. We connected to ai.stimhaus/emma-for-agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.stimhaus/emma-for-agents MCP server still maintained?
ai.stimhaus/emma-for-agents is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.