Demo
A small server, tested end to end.
I keep a small demo server to show how a finished MCP server behaves. It uses made-up data, never calls a real service, and is not affiliated with any company. It runs on my own machine for now, so this page shows what it contains and how it is tested, and I can walk you through it on request.
What the demo has
- One read-only tool with safety labels: read-only, not destructive, safe to repeat.
- Strict inputs. Only a fixed example value is accepted, and extra fields are refused.
- A bearer-token check, and a refusal of requests from other websites.
- A verification route that directories such as ChatGPT’s can use to confirm who runs a server.
What I test on it
All checks run locally with the internet switched off, apart from a stand-in service on the same machine. I send the dated results of the latest run on request (see the walk-through below).
- The server starts and completes the MCP handshake.
- The tool list appears with all four safety labels.
- A tool call reaches the stand-in service exactly once.
- Invalid or extra arguments are rejected before anything is sent upstream.
- A missing or wrong token gets a 401 response.
- A request from another website gets a 403 response.
- The verification route returns the configured text and refuses other methods.
What the demo does not prove
There is no public demo address yet, so you cannot connect your own AI client to it today. The checks above ran on my own machine. They say nothing about how a real API will behave. A client build is tested against the client’s own sandbox or test key. Never your production keys. I report anything I could not test.
Ask for a demo walk-through
Email syed@callablestudio.com with the subject “Demo walk-through”. I will reply with the demo’s tool list and the latest test results. I usually answer within two working days (India time).
Not ready for that? The free spec check needs only a link to your public OpenAPI file.