Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "altessa": {
      "type": "http",
      "url": "https://mcp.altessa.studio/mcp"
    }
  }
}

claude mcp add --transport http altessa https://mcp.altessa.studio/mcp

[mcp_servers.altessa]
url = "https://mcp.altessa.studio/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "altessa": {
      "type": "remote",
      "url": "https://mcp.altessa.studio/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "altessa": {
      "type": "http",
      "url": "https://mcp.altessa.studio/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=altessa&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmFsdGVzc2Euc3R1ZGlvL21jcCJ9"
}

{
  "servers": {
    "altessa": {
      "type": "http",
      "url": "https://mcp.altessa.studio/mcp"
    }
  }
}

{
  "mcpServers": {
    "altessa": {
      "httpUrl": "https://mcp.altessa.studio/mcp"
    }
  }
}

extensions:
  "altessa":
    enabled: true
    name: "altessa"
    type: streamable_http
    uri: "https://mcp.altessa.studio/mcp"
    timeout: 300

Quality 96 / 100strong

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations4 of 4 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 1,523 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
pass
tools.hidden_textno hidden text in tool names, descriptions, schemas or annotations

stability100 · weight 15

pass
stability.changes4 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name
pass
stability.new_linksno tool change named a new site

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 1,523 tokens to load them all · tool set 8a37d41bc7ad · tools last changed 2026-10-25 · checked 2026-11-14 06:30 UTC

Tool changes

2026-10-25estimate_wedding_budgetchangedannotations
2026-10-25build_wedding_timelinechangedannotations
2026-10-25generate_seating_chartchangedannotations
2026-10-25plan_reception_layoutchangedoutput schema, annotations

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository

provenance55

liveness100

freshness100

hygiene80

+dns-namespace +website +reachable +uptime-100% +updated-20d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://mcp.altessa.studio/mcp` streamable-http	none	yes	100%	483 ms	2026-07-28	2026-11-14

Tools (4)

`build_wedding_timeline`	Use this when someone wants a minute-by-minute wedding day schedule: getting ready, first look, ceremony, cocktail hour, reception, send-off. Needs the ceremony start time; everything else has defaults. Do not use for the months-long planning checklist or vendor payment schedules.
`estimate_wedding_budget`	Use this when someone gives a total wedding budget, a guest count, or both and wants a category-by-category split (venue, catering, photo and video, flowers, music, attire, stationery, and so on) with per-guest math and a contingency line. Do not use for tracking actual spending or vendor payments.
`generate_seating_chart`	Use this when someone has a list of wedding guests and wants them assigned to tables, keeping families, friend groups, or couples together and keeping specific people apart. Accepts names with optional group labels and keep-apart pairs. Returns table assignments and a shareable chart. Do not use for floor plans without names (use plan_reception_layout) or for RSVP tracking.
`plan_reception_layout`	Use this when someone wants to plan a wedding reception floor plan, figure out how many tables fit in a room, or check whether a venue space can hold their guest count with a dance floor, bar, buffet, DJ or band, and head table. Needs guest count; room dimensions in feet are optional (if missing, returns the space required instead of a fit check). Do not use for ceremony seating, seating assignments by name (use generate_seating_chart), or venue search.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "studio.altessa/altessa",
  "title": "Altessa Wedding Planner",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.altessa.studio/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://www.altessa.studio/plugins",
  "description": "Reception layouts to scale, seating charts, wedding day timelines, and budgets. No login needed."
}