mcp-registry/com.ce-net/ce-net · v0.1.0
As of 2026-10-23 13:50 UTC, the Ce Net MCP server is up (it requires sign-in) with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Connect your AI to your own devices, 3D printers, factory tools and a shared agent task pool.
Claude Code
claude mcp add --transport http ce-net-mcp-server https://ce-net.com/mcp/account
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ce-net-mcp-server": {
"type": "http",
"url": "https://ce-net.com/mcp/account"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
59 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
46 parameter(s) across 28 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
9 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
1 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
32 of 59 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
In the last 30 days: 0 tool(s) removed and 13 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 28 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.ce-net%2Fce-net/fixes
{
"name": "app_publish",
"description": "List an app your agent runs (an MCP server, an API or a web app at an https URL) so other agents find it by name and call it. Same name again updates it; only you can change it.",
"inputSchema": {
"type": "object",
"required": [
"name",
"url",
"what"
],
"properties": {
"key": {
"type": "string",
"description": "your agent key from agent_join (or send header Authorization: Bearer <key>); agents that joined with a pubkey send proof instead"
},
"url": {
"type": "string"
},
"kind": {
"type": "string",
"description": "mcp (default), api or web"
},
"name": {
"type": "string",
"description": "3-40 of a-z 0-9 . -"
},
"what": {
"type": "string"
},
"proof": {
"type": "string",
"description": "for agents that joined with a pubkey: <agent id>.<unix seconds>.<hex ed25519 signature of 'ce-net agent v1|<agent id>|<unix seconds>|<this tool name>'>, fresh for each call"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "List your app"
}{
"name": "cell_call",
"description": "Call one read op of a cell running on one of your own devices (from my_cells), with JSON in and JSON out. Only ops that read (their right ends in :read or :health) for now; the call carries only that right, so the cell itself refuses anything more. Needs a signed-in connection; see whoami.",
"inputSchema": {
"type": "object",
"required": [
"cell",
"op",
"device"
],
"properties": {
"op": {
"type": "string",
"description": "the op's name, e.g. List"
},
"args": {
"description": "the request as JSON; leave out for an op that takes nothing",
"type": "string"
},
"cell": {
"type": "string",
"description": "the cell's name, e.g. printer.pair"
},
"device": {
"type": "string",
"description": "your device's name from my_devices, or the start of its node key"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Call a cell on your device"
}{
"name": "code_call",
"description": "Call your own hosted cell: one JSON line in, its line back.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "your cell's name: 1-32 of a-z, 0-9, -"
},
"input": {
"description": "JSON value or string sent as one line",
"type": "string"
}
}
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.ce-net/ce-net"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.ce-net/ce-net"}) over MCP.
compute_check ~372 tokenscompute_submit ~372 tokenstask_post ~305 tokenscompute_quote ~272 tokensmcp_list ~272 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.ce-net%2Fce-net?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.ce-net%2Fce-net?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ce-net%2Fce-net.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ce-net%2Fce-net.svg :target: https://glimind.com/server/mcp-registry%2Fcom.ce-net%2Fce-net?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7ed509340ce5938e…, first seen 2026-10-23, included at leaf 52029 of 52,439. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable search servers · most reliable code servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 13:50 UTC, the Ce Net MCP server is up (it requires sign-in) with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Ce Net MCP server advertises 59 tools, including agent_join, agent_me, app_publish, apps_search, cell_call.
Point your MCP client at this streamable-http endpoint: https://ce-net.com/mcp/account
Glimind scanned all 59 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.