# MikeKappel.com

Version: 3.126.0
Updated UTC: 2026-06-18T23:02:44Z

Michael Kappel / Mike Kappel is presented here as a Senior Software Engineer and Software Architect focused on AI-assisted engineering, Model Context Protocol (MCP), .NET, SQL Server, TypeScript, confirmed Angular experience, enterprise modernization, and machine-readable portfolio evidence.

Primary human review routes:

- `/resume/`
- `/projects/#selected-projects`
- `/case-studies/`
- `/career/`
- `/experience/`
- `/contacts/`

Confirmed professional profile links:

- Website: `https://mikekappel.com/`
- LinkedIn: `https://www.linkedin.com/in/michaelkappel`
- GitHub: `https://github.com/MichaelKappel`
- NuGet: `https://www.nuget.org/profiles/Michael.Kappel`
- UAIX Agent Executability Matrix: `https://uaix.org/en-us/spec/agent-executability-matrix/`

MCP connection routes:

- Canonical Streamable HTTP endpoint: `POST /mcp`
- WordPress REST transport fallback: `POST /wp-json/mk/v1/mcp`
- MCP manifest: `GET /wp-json/mk/v1/mcp-manifest`
- MCP runtime status: `GET /wp-json/mk/v1/mcp-status`
- MCP client configuration: `GET /mcp-client-config.json`
- Bounded research reader: `GET /wp-json/mk/v1/research-item`
- MCP Registry-compatible remote server manifest: `GET /server.json`
- Site-specific discovery card: `GET /.well-known/mcp.json`
- Static capability manifest: `GET /assets/data/mcp-manifest.json`
- Human connection and usage guide: `GET /mcp-server/`
- Sparse-vector retrieval metadata: `GET /research-vectors/manifest.json`

The MCP server is stateless and read-only. It exposes ten bounded tools, twelve resources, three parameterized research resource templates, and three prompts. Every tool publishes JSON Schema 2020-12 input/output contracts and validates structured output. All four definition-list operations use bounded pages with signed opaque continuation cursors. Research access supports catalog discovery, hybrid search, one-call and resource-only bounded context assembly, readable resource links, and chunked reading across 999 guarded records and 802 Markdown documents while preserving public/private gates and labeling retrieved report text as untrusted reference content.

Capability downshift order:

1. MCP at `/mcp`
2. MCP through `/wp-json/mk/v1/mcp`
3. Purpose-specific `/wp-json/mk/v1/*` REST routes
4. Static JSON/text discovery
5. Public HTML
6. Safe no-op rather than private inference or simulated success

Primary machine-readable review routes:

- `/llms-full.txt`
- `/.well-known/mcp.json`
- `/api/public-route-index.json`
- `/route-qa-contract.json`
- `/research-dashboard.json`
- `/.well-known/ai-agent.json`
- `/.well-known/openapi.json`

Boundaries:

- WordPress is the production runtime; JavaScript is progressive enhancement.
- `/reports/` is raw noindex research; `/docs/` is curated Architecture Notes.
- Only the declared MCP tools may be invoked through the MCP endpoint. Discovery does not authorize uploads, writes, credential testing, private extraction, form automation, shell execution, arbitrary URL retrieval, or unknown-route crawling.
- Package-level MCP QA does not prove that the live site has already deployed v3.126.0. Verify the reported runtime version before relying on the endpoint.
- Photography remains creative-range context only, not software-delivery proof.

## MCP v3.126.0 interoperability
- POST requires `Accept: application/json, text/event-stream`; missing or one-sided negotiation returns HTTP 406.
- JSON-RPC request identifiers are strings or integers only.
- Search results include bounded triage metadata and gated readable results may include short-lived item-bound signed read grants.
- Research source/type/mode/limit completion and `mk://mcp/deployment-manifest` are available to resource-capable clients.