retoor
251c3dc2ba
- 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)
29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
# How to Test and Debug an MCP Server: From the Inspector to Automated Tool Tests
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Institute | Molodetz Institute - Research & Retrieval Division |
|
|
| Subject | mcp-client-support |
|
|
| Document type | Source Citation Card |
|
|
| Tier | 2 |
|
|
| Source title | How to Test and Debug an MCP Server: From the Inspector to Automated Tool Tests |
|
|
| Source URL | https://dev.to/jeff_pdc/how-to-test-and-debug-an-mcp-server-from-the-inspector-to-automated-tool-tests-4oci |
|
|
| 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; reported to show raw curl and stdio transcripts of the handshake and tool calls. Seen but not opened; raw transcripts would be handy cross-checks for tai's own wire output.
|
|
|
|
## Changelog
|
|
|
|
| Date | Change |
|
|
|---|---|
|
|
| 2026-10-18 | Logged as consulted-but-not-analyzed. |
|