Wever Labs MCP server
Which servers in the official MCP registry are Wever Labs's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-15
- Registry namecom.weverlabs/agentic-railsverified in the MCP registry
The registry name sits under weverlabs.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-15
- Tools5
- Server calls itselfwever-labs-agent-api
- Server version0.1.0
- Protocol version2025-11-25
On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 2952 ms.
get_service_catalogRead the four supported Labs computation contracts and connection instructions.
check_evidence_inventoryCompare explicit submitted evidence labels and return exact matched and missing items. This does not read or verify document contents.
review_mcp_manifestInventory submitted MCP tool declarations and flag missing or consequential annotations. This does not connect to a server or grant authority.
build_operator_briefSummarize supplied service health and queue observations into deterministic priorities. No private records are fetched and no activity is invented.
prepare_work_orderPrepare a validated DiligenceOps task for a specific Connect recipient. Submission, recipient permission and execution remain separate steps.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agentic-rails": {
"type": "http",
"url": "https://weverlabs.com/api/mcp"
}
}
}OpenAPI spec
38 paths, read 2026-10-15. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.