Services / Local MCP server · Registry
co.truncus/mcp-server
Runs on your own machine from the npm package @truncus/mcp-server (latest version 0.1.3, changed 2026-10-18).
Listed in a public agent registry. The name is the registry's label, not ours. Not reviewed by a person.
Checked monthly. Local MCP servers (package checks): weekly once the service's place in the capability tree is confirmed, monthly otherwise.
In the capability tree: Messaging and communication / Email (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✗ what it does is unclear to our placement; ✗ its latest check did not pass.
Recent package checks
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Latest version deprecated HTTP 200 latest version is deprecated |
281 ms |
What this evidence does not show
- A passing check means the package exists in its registry and its latest version is not deprecated or yanked (package-check/1). It does not show that the server works, what its tools do, or that it is safe to run: it runs on your machine with the access you give it.
- Listed in the Official MCP Registry; the package facts come from npm or PyPI. The registry's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page.
Machine-readable: /api/v1/services/cand_656eec5d524b5c29