MCP spec conformance: 1 requirement violated (via @hasmcp/mcp-spec-test) — spec 2025-11-25

When tested against MCP spec revision **2025-11-25**, this server fails 1 conformance requirement: a version-less request (no protocol version declared by the client) is refused rather than served on a default version, as the spec requires. In this run the probe itself timed out ("no response within 10000ms"), which may just be startup latency via `uvx` rather than an outright rejection — worth a closer look on your end. Because that first request never completed, several other cases can't be checked at all under this revision (marked "not verified" below, not failures). The same server tested against the newer revision 2026-07-28 fails 7 requirements (including a `server/discover` method returning `-32602 Invalid request parameters`) — that's covered in a separate issue filed alongside this one, since the violation counts genuinely differ by revision.

## Conformance report

# MCP 2025-11-25 conformance report

**Verdict: not conformant** — 1 requirement violated.

| | |
| --- | --- |
| Target | `uvx --from dbt-mcp dbt-mcp` |
| Transport | stdio |
| Revision tested | 2025-11-25 |
| Revisions supported | 2026-07-28, 2025-11-25 |
| Passed | 6 |
| Failed | 1 |
| Not verified | 13 |
| Cases applied | 20 |
| Duration | 25046ms |
| Tool | @hasmcp/mcp-spec-test 0.1.1 |

## Failed (1)

_the server deviates from the spec here_

### Version negotiation

- **a request with no version at all is served on the default**
a version-less request must be served, got 0: {"_raw":"no response within 10000ms"} 0 !== 200

## Not verified (13)

_skipped; a skip is not a pass_ — all stem from that first request never completing.

### Capability methods

- tools/list returns schema-conformant tools
- tools/call on an unknown tool is an error, not a crash
- tools/call returns a schema-conformant CallToolResult
- prompts/list returns schema-conformant prompts
- prompts/get returns messages with a role and content
- resources/list returns schema-conformant resources
- resources/templates/list returns schema-conformant templates
- resources/read returns contents for every sampled resource
- resources/read on an unknown uri is an error
- following nextCursor terminates and does not repeat a page
- an invalid pagination cursor is rejected (SHOULD)

### Version negotiation

- initialize returns the schema-required fields
- the handshake settles on the revision under test

## Passed (6)

_checked and conformant_

- server/discover: the suite is reading a schema that matches the features it selected
- Version negotiation: an unsupported version offered at the handshake is refused or downgraded, not echoed
- Official SDK interop: the official SDK does not yet implement the newest revision
- Official SDK interop: a stock official-SDK client completes the handshake
- Official SDK interop: the handshake settles on a revision inside the supported window
- Official SDK interop: a stock official-SDK client can list tools

## How to reproduce

**With Docker:**
```
docker pull hasmcp/mcp-spec-test:latest
docker run --rm hasmcp/mcp-spec-test -c "uvx --from dbt-mcp dbt-mcp" --spec-version 2025-11-25
```
(or, if that image can't run on your platform: `git clone https://github.com/hasmcp/mcp-spec-test && cd mcp-spec-test && docker build -t mcp-spec-test . && docker run --rm mcp-spec-test -c "uvx --from dbt-mcp dbt-mcp" --spec-version 2025-11-25`)

**Without Docker (npx):**
```
npx @hasmcp/mcp-spec-test@latest -c "uvx --from dbt-mcp dbt-mcp" --spec-version 2025-11-25
```

---
This issue was generated by an automated conformance sweep across public MCP server repos. Note this specific failure could be an environment/timing artifact (first-run `uvx` startup latency under the suite's 10s timeout) rather than a real rejection — worth confirming on your end before treating it as a hard bug. The maintainer is welcome to close this if it turns out to be a false positive.