claim-mcp-stdio-public
by lightnow-ai
README.md
# claim-mcp-stdio-public
Public, minimal stdio MCP server for LightNow publisher acceptance tests.
Its single `identify` tool returns the fixture name, version, transport and supplied message. It does not call external services or contain credentials.
## Local development
```sh
python3 -m venv .venv
.venv/bin/pip install -e '.[test]'
.venv/bin/pytest
.venv/bin/claim-mcp-stdio-public
```
The server reads and writes the MCP protocol on standard input/output.
## Container
```sh
docker build -t claim-mcp-stdio-public:local .
docker run --rm -i claim-mcp-stdio-public:local
```
The image runs as UID/GID 10001. Jenkins tests the real MCP transport and publishes native amd64/arm64 images to `harbor.apitree.net/lightnow-ai/claim-mcp-stdio-public`. Acceptance manifests pin a verified immutable image digest.
## Test scope
This public repository covers catalog submission, ownership claim/publication and private owner copies. These journeys use separate manifest identities; private repository access is tested in the existing private sibling repositories. No repository history or credentials are copied from those repositories.
TDQS
C2.7/5.0
Scored across 1 tool
Disambiguation5/5
With only a single tool there is nothing to confuse it with, so misselection is impossible. 'identify' has a clear, singular purpose for the test-fixture domain.
Naming Consistency4/5
The lone tool name 'identify' is a clean, lowercase verb, which is readable and conventional. There is no second tool to establish or violate a verb_noun pattern, so consistency cannot be fully demonstrated.
Tool Count2/5
A single trivial tool is extremely thin for a server, even one scoped to ownership-claim acceptance tests. It leaves almost no surface for an agent to work with.
Completeness2/5
The surface offers only identity retrieval with no supporting operations (e.g., list, create, or validate claims). For a testing-oriented server this is severely incomplete.
Maintenance
ActivityMaintained
ResponsivenessNo issues