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.

seelig.ai booking

REMOTE · WWW.SEELIG.AI

Lists the AI consulting services of seelig.ai (Switzerland) and requests a 30-minute first call.

Available components

+4 this week 68 Trust /100

Last scanned (18 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 22 Oct 2026.

Category CRM and Sales

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 Security63
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 416 tokens (~138/item across 3 items; 3 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 8% of tool parameters carry a description.Partial
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).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.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 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.

  • 18 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.

  • 16 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.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Oct 26 63

    First indexed and scored.

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 22 Oct 2026 · Probed https://www.seelig.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.seelig.ai CN=YR1,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 RSA 2048 SHA256-RSA 6fba291a67ffd0a93d1e8c65eafd949f2fb
SANs: www.seelig.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 insecure

Validation of www.seelig.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
seelig.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; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://i.scdn.co; font-src 'self'; connect-src 'self' blob: https://vitals.seelig.ai; media-src 'self'; worker-src 'self'; manifest-src 'self'; frame-src 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; report-uri /api/csp-report; report-to csp-endpoint
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.seelig.ai/api/mcp Verified 200
http (plaintext) http://www.seelig.ai/api/mcp HTTPS enforced 308 https://www.seelig.ai/api/mcp
MCP tools · 3 exposed · ~245 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_free_slots ~91

Returns open start times (ISO 8601, UTC offset included) for a 30-minute video call about one service. Dates are YYYY-MM-DD, from today onward, covering at most 14 calendar days (to is at most 13 days after from).

NameTypeReqDescription
fromstringyes–
servicestringyes–
timeZonestring––
tostringyes–

No output schema declared.

No examples provided.

list_services ~48

Lists every seelig.ai service with id, price in CHF, duration in weeks, deliverable and page URL, in English or German.

NameTypeReqDescription
langstring–Language of names and descriptions

No output schema declared.

No examples provided.

request_booking ~106

Requests a 30-minute first call about one service at an open start time. Sends the person a confirmation email, which cannot be unsent. Nothing is booked until they confirm through the link in it.

NameTypeReqDescription
emailstringyes–
langstring––
namestringyes–
notesstring––
servicestringyes–
startstringyes–
timeZonestring––
websitestring––

No output schema declared.

No examples provided.

Install

How do I install the seelig.ai booking MCP server?

seelig.ai booking is a hosted endpoint at https://www.seelig.ai/api/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 · www.seelig.ai

# add to Claude Code
claude mcp add --transport http yodaisgaming-seelig-ai-booking 'https://www.seelig.ai/api/mcp'
Common questions

What is the seelig.ai booking MCP server?

seelig.ai booking is an MCP server listed in the public MCP registry as io.github.Yodaisgaming/seelig-ai-booking. Lists the AI consulting services of seelig.ai (Switzerland) and requests a 30-minute first call. This page covers its hosted endpoint (https://www.seelig.ai/api/mcp).

Is the seelig.ai booking MCP server safe to use?

seelig.ai booking scores 68 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 seelig.ai booking MCP server expose?

seelig.ai booking exposes 3 tools: list_services, get_free_slots, request_booking. Their descriptions and schemas cost roughly 245 tokens of context every time the server is loaded.

Does the seelig.ai booking MCP server require authentication?

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

Is the seelig.ai booking MCP server still maintained?

seelig.ai booking is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.