mcp-registry/io.github.dotnova/context-layer · v1.1.0
As of 2026-10-20 20:34 UTC, the Dotnova Context Layer MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Intelligent context infrastructure for AI teams: knowledge graph, sessions, tasks, documents.
Claude Code
claude mcp add --transport http dotnova-context-layer-mcp-server https://api.dotnova.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"dotnova-context-layer-mcp-server": {
"type": "http",
"url": "https://api.dotnova.io/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
62 of 62 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 →
62 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 →
23 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 →
6 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 →
Handshake + tools/list takes ~2,164 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.dotnova%2Fcontext-layer/fixes
{
"name": "accept_org_invite",
"description": "Accept a pending organization invite by organization name.",
"inputSchema": {
"type": "object",
"title": "AcceptOrgInviteParams",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"org_name"
],
"properties": {
"org_name": {
"type": "string",
"description": "Organization name to accept the invite for"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_task_dependency",
"description": "Add a dependency between tasks. Use this to express that a task is blocked by another task (must complete first) or relates to it. This prevents context contamination: when Task B depends on Task A, agents working on Task B will be warned if Task A is still in progress.",
"inputSchema": {
"type": "object",
"title": "AddTaskDependencyParams",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"task_id",
"depends_on_task_id"
],
"properties": {
"task_id": {
"type": "string",
"description": "The task that is blocked (depends on the other task)"
},
"dependency_type": {
"type": [
"string",
"null"
],
"description": "Dependency type: 'blocks' (must complete before) or 'relates_to' (informational link). Default: blocks"
},
"depends_on_task_id": {
"type": "string",
"description": "The task that blocks (the dependency / prerequisite)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_team_member",
"description": "Add a member to a team. Find the team by name or ID, and the user by name or email.",
"inputSchema": {
"type": "object",
"title": "AddTeamMemberParams",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"user"
],
"properties": {
"role": {
"type": [
"string",
"null"
],
"description": "Role in team: member or lead (default: member)"
},
"user": {
"type": "string",
"description": "User name or email to add"
},
"team_id": {
"type": [
"string",
"null"
],
"description": "Team ID (optional if team_name is provided)"
},
"team_name": {
"type": [
"string",
"null"
],
"description": "Team name (optional if team_id is provided)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/io.github.dotnova/context-layer"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.dotnova/context-layer"}) over MCP.
upload_document ~575 tokenssetup_organization ~491 tokenscreate_task ~461 tokenslog_traces_batch ~459 tokenslog_trace ~407 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%2Fio.github.dotnova%2Fcontext-layer?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dotnova%2Fcontext-layer?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dotnova%2Fcontext-layer.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dotnova%2Fcontext-layer.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.dotnova%2Fcontext-layer?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:df8ea5014bedd923…, first seen 2026-10-17, included at leaf 5857 of 35,120. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable productivity servers · most reliable other servers · most reliable devops servers · most reliable knowledge 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-20 20:34 UTC, the Dotnova Context Layer MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Dotnova Context Layer MCP server advertises 62 tools, including accept_org_invite, add_task_dependency, add_team_member, assign_task, create_position.
Point your MCP client at this streamable-http endpoint: https://api.dotnova.io/mcp
Glimind scanned all 62 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.