Endpoint report / Metadata only
Svelte MCP
A dated endpoint inspection. Metadata and any separately recorded tool call have their own evidence, scope and limitations.
What this establishes
The anonymous endpoint advertised 4 tools and passed four bounded metadata checks. Tool execution was not tested. Actual ChatGPT and Claude workflows were not tested.
Tool names and metadata are server declarations. Advertised capabilities are not evidence of successful task execution.
- Connection and metadata
- Metadata checks passed
- Observed tool catalog
- Complete: 4 tools
- Read-only smoke test
- Not tested
- ChatGPT / Claude
- Not tested / Not tested
- Overall score
- Not assigned
Recorded checks
These checks cover the metadata inspection. They are separate from the tool-call result above, when present.
protocol-negotiation
Negotiated protocol 2025-06-18; this does not establish host compatibility.
initialized-notification
The initialization notification received HTTP 202 with an empty body.
tool-metadata-shape
SDK metadata shape checked for 4 observed tools. This is not complete JSON Schema validation or behavior verification.
oauth-login
OAuth discovery, login, token refresh and authenticated access are outside this anonymous inspection.
Metadata request evidence
request-1 / initialize
2026-10-15T07:14:19.234Z
HTTP 200 · 1338 ms · 4672 B
response-received
request-2 / notifications/initialized
2026-10-15T07:14:20.572Z
HTTP 202 · 231 ms · 0 B
notification-accepted
request-3 / tools/list
2026-10-15T07:14:20.803Z
HTTP 200 · 175 ms · 24868 B
response-received
Observed tool catalog
Names were advertised through tools/list. Any tool execution is recorded separately in the smoke test section.
Complete: 4 tools
- get-documentation
- list-sections
- playground-link
- svelte-autofixer
Endpoint and provenance
- Endpoint
- https://mcp.svelte.dev/mcp
- Official source
- https://svelte.dev/docs/ai/remote-setup
- Profile
- Anonymous endpoint profile
- Requested protocol
- 2025-11-25
- Reported protocol
- 2025-06-18
- Protocol
- 2025-06-18
- Observed at
- 2026-10-15T07:14:20.978Z
- Run ID
- 6e17adb3-3579-4174-ad0d-f5ca24fed8cd
- Catalog SHA-256
- 16ce022158979d9e8e7f52e612eb5422f0bb98d841370e47793d12f68e456530
- Fingerprint scope
- complete-catalog
SHA-256 of all observed tool objects, recursively sorted object keys and sorted canonical tool strings; schema array order is preserved. Raw descriptions, schemas and headers are not persisted.
Inspection bounds
- requestTimeoutMs
- 5,000
- runTimeoutMs
- 30,000
- responseBytes
- 1,048,576
- requests
- 7
- pages
- 5
- tools
- 200
What this report does not establish
These observations do not establish general task success, security, OAuth behavior or ChatGPT and Claude compatibility. Read the limits of each recorded test.
- Metadata-only anonymous inspection. No tools/call, OAuth flow, API model calls, host UI or publication review was executed. No global quality or safety score is produced.
- Annotations are server declarations, not verified behavior. Metadata success does not establish task success, security, usefulness or ChatGPT/Claude compatibility.
- Only active exact HTTPS endpoints in the reviewed source registry are accepted. Redirects, supplied credentials, arbitrary endpoints and OAuth URL fetching are disabled. DNS/TLS use the local runtime: this is not a hardened multi-tenant SSRF sandbox and must not be exposed as a public scanner.
- Session identifiers are used only in memory. Request/response headers, raw error messages, raw descriptions and schemas are excluded from artifacts. Tool names and aggregate metadata remain untrusted server input.
- Only the recorded protocol versions and bounded catalog prefix are supported. Reaching a bound or lacking access means unknown, not a failed server or a passing full audit.
What should your MCP do better?
Share a public endpoint or repository, the tasks that matter, and the clients your users use. We will discuss a pilot scope, access and price.
Discuss a benchmarkOpens your email app. Send public links only; arrange sandbox access separately.