A
licenseNot graded
qualityC
maintenanceProvides a shared MCP SDK wrapper for building MCP servers with stdio transport, tool registration, JSON-safe responses, and environment helpers.
27 npm
MIT
claim-mcp-stdio-public
by lightnow-ai
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@claim-mcp-stdio-publicrun identify with message 'publisher acceptance test'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
python3 -m venv .venv
.venv/bin/pip install -e '.[test]'
.venv/bin/pytest
.venv/bin/claim-mcp-stdio-publicThe server reads and writes the MCP protocol on standard input/output.
Related MCP server: mcp-sandbox
Container
docker build -t claim-mcp-stdio-public:local .
docker run --rm -i claim-mcp-stdio-public:localThe 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.
Available Tools
1 toolidentifyC
Return deterministic identity data for ownership-claim acceptance tests.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ready |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
C2.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. 'Deterministic' is a genuine and useful trait (repeat calls yield identical output), but nothing is said about side effects, auth requirements, whether the 'message' input alters the response, or the shape of the returned identity data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no filler, and the core action is front-loaded. It is concise but arguably too terse to be self-sufficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values needn't be explained, but for a tool with an undocumented parameter, no annotations, and no usage guidance, the description leaves too much for an agent to infer before invoking it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
One parameter ('message', default 'ready') has 0% schema description coverage, and the description says nothing about what it means or how it influences the returned identity data. The description does not compensate for the documentation gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a verb and resource ('return deterministic identity data') but 'identity data' is left undefined, and the qualifier 'for ownership-claim acceptance tests' narrows it to a test-fixture role rather than describing what the data actually is. There are no siblings to differentiate from, so the ambiguity is unmitigated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
'for ownership-claim acceptance tests' hints at a use context, but there is no explicit statement of when to call this tool, what precondition it satisfies, or what to do instead. No alternatives or exclusions are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.0- First observed
identify
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
Related MCP Connectors
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Public, read-only MCP server for FarmNeural company facts, packages, and capabilities.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA public MCP server providing test fixtures for developers and QA, with a single tool 'identity' that returns a unique canary string to verify the server's response.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables building and testing MCP-style tool servers by exposing list_tools and call_tool over stdio or HTTP with local stub tools such as echo, get_time, and fake_crm_lookup.MIT
- FlicenseAqualityCmaintenanceEnables MCP clients to call a simple greeting tool that takes a name and returns personalized text and structured messages via stdio.1-