Related Servers

The six tools split cleanly along a discover/verify/produce axis: radar and find_independent_software are discovery, replication_status and verified_claims are verdict lookups, and replication_template is scaffolding. The two lookalikes are separated correctly by granularity (per-DOI vs network-wide) and by resource (papers vs software only). The main trap is find_dataset, whose name implies a dataset search but which actually only returns handoff instructions to another MCP, which an agent could misread as a functioning search tool.

Three tools use a verb_noun pattern (find_independent_software, find_dataset) intermixed with bare noun phrases (radar, replication_status, replication_template, verified_claims). The bare noun `radar` is especially uninformative next to the rest. Readable overall, but the convention is clearly mixed rather than predictable.

Six tools is a sensible, tight surface for a discover/verify/scaffold workflow. However, find_dataset does not perform its own action (it delegates to another MCP), so one of the six is arguably a stub rather than an earning tool, and much of the descriptive weight is carried by long prompts instead of tool surface.

Discovery, verdict lookup (single and network-wide), and scaffolding are all covered, but the 'produce' half of the loop is entirely a handoff to an external template repo and a fresh agent session — the server itself cannot sign, publish, or submit anything. There is also no way to search or filter the verified-claims corpus (no topic or field query) and no dataset search at all, only an instruction stub.