Files
tai/research/mcp-client-support/dev-smartgate-message-format.md
T
retoor 251c3dc2ba research: mcp-client-support subject (106 sources, 3 conclusions)
- wire spec: lifecycle, stdio + Streamable HTTP transports, tools,
  utilities, legacy SSE, versioning, changelog (14 Tier 1)
- client ecosystem: Claude Code/VS Code/Cursor/Codex configs,
  mcp-remote, Smithery, registries, Glama (12 Tier 1)
- security/ops: authorization draft, trust model, poisoning,
  rug pulls, production hardening (12 Tier 1) + 68 Tier 2 cards
- conclusions: minimal stdlib client on 2025-11-25, normalizer +
  resolver agent for pasted configs/GitHub URLs, untrusted-until-
  consent trust model; nothing built yet
- audit PASS (14 subjects, 797 sources, 32 conclusions)
2026-10-18 19:23:02 +02:00

29 lines
1.1 KiB
Markdown

# Model Context Protocol (MCP) Message Format Explained
## Metadata
| Field | Value |
|---|---|
| Institute | Molodetz Institute - Research & Retrieval Division |
| Subject | mcp-client-support |
| Document type | Source Citation Card |
| Tier | 2 |
| Source title | Model Context Protocol (MCP) Message Format Explained |
| Source URL | http://dev.to/smartgate/model-context-protocol-mcp-message-format-explained-1hmo |
| Source type | blog post |
| Date researched | 2026-10-18 |
| Researched by | tai (agent), model: Claude Sonnet 5, on behalf of retoor |
| Research method | Search aggregator result listing (not independently opened or quoted) |
| Confidence | Not independently verified |
| Status | Active |
## Why it's here
Surfaced during wire-spec evidence gathering as a third-party walkthrough of the JSON-RPC round trip (`initialize` to `tools/list` to `tools/call`). Seen but not opened; logged so a future session can check its transcripts against the normative spec dossiers.
## Changelog
| Date | Change |
|---|---|
| 2026-10-18 | Logged as consulted-but-not-analyzed. |