A G.B. Industry companyMCP Server Starter
This fictional sample shows the local, credential-free contract Zinvyl delivers before anyone connects a production system, grants OAuth access, hosts an endpoint, or authorizes an external write.
Effective October 23, 2026
Synthetic server
A fictional inventory server exposes one get-item tool. The tool accepts a synthetic item identifier through a declared schema and returns a fixed sample object. It performs no network request, reads no private data, stores no credential, and changes no external state.
What the starter contains
- Current SDK structure: a TypeScript MCP v2 server factory served over stdio.
- Bounded tool contracts: one to three distinct read-only tools with validated string, number, or boolean inputs.
- Fixture outputs: approved synthetic objects that make the contract inspectable without pretending a production integration exists.
- Protocol-safe logging: stdout remains reserved for JSON-RPC and the readiness message goes to stderr.
- Truthful verification: static construction checks are recorded as passed; isolated typecheck and MCP Inspector execution remain marked not run.
Delivered package
source-files.json—package.jsonandsrc/index.tssource text.tool-schemas.json— explicit tool names, fields, fixture outputs, and side-effect boundaries.verification-report.json— completed static checks and remaining runtime steps.deployment-notes.mdandREADME.md— setup, Inspector, and security boundaries.
Boundary
This $249 service is a local fixture starter. It does not implement production business logic, connect APIs, handle credentials, grant permissions, deploy or host a server, write to external systems, or guarantee compatibility with every MCP host. Those actions require a separate funded implementation scope, fresh authorization, and runtime verification.