example-mcp
# Example MCP
Example MCP server from Scalably. Replace this line.
<!-- mcp-name: io.scalably/example-mcp -->
## Install
Claude Code:
```bash
claude mcp add example -- uvx scalably-example-mcp
```
Codex:
```bash
codex mcp add example -- uvx scalably-example-mcp
```
Claude Desktop: download `example-mcp.mcpb` from the latest GitHub release and open it.
## Tools (1)
| Tool | What it does |
|---|---|
| `example_echo` | Return the text you pass in. |
## Configuration
| Variable | Required | Purpose |
|---|---|---|
| `EXAMPLE_LOG_LEVEL` | no | INFO (default) or DEBUG |
## Verify
Each release lists the package version, the `.mcpb` sha256 and the production commit it was derived from in CHANGELOG.md. CI runs the tests and a clean install of the built wheel on every push.
## Privacy Policy
This server runs locally, on your machine, under your own credentials. It collects no personal data, contains no telemetry, stores nothing persistently, and talks only to the vendor API it wraps. No third party, including Scalably, receives your data. Contact: hello@scalably.io. Canonical copy: https://scalably.io/connector-privacy.html
## License
MIT. Copyright Scalably.
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool clearly performs an echo operation with no overlapping purposes.
The sole tool name 'example_echo' does not follow a clear verb_noun pattern ('example' is not a verb), but there is no inconsistency to compare against. The name is readable but not representative of a standard naming convention.
With only one tool, the server is far below the typical scope of 3-15 tools. The tool appears to be a placeholder, and the count feels excessively thin for a functional MCP server.
The description explicitly states 'Replace with real tools,' indicating this is a stub rather than a complete domain surface. There is no coherent set of operations to cover a real workflow, leaving significant gaps for any practical use.