mcp-registry/ai.taskive/mcp · vQuery and manage tasks, projects, teams, and boards in Taskive via MCP. Authenti
As of 2026-10-26 18:05 UTC, the Taskive MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
AI-native project management + agent memory: tasks, sprints, risk, burnout, knowledge search.
Point your MCP client at this streamable-http endpoint: https://mcp.taskive.ai/mcp
98 of 98 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 →
98 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 →
206 parameter(s) across 88 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 →
35 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 →
Loading this server's tool list costs an agent ~23,251 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. 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 →
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.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 88 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.taskive%2Fmcp/fixes
{
"name": "add_project_member",
"description": "Add Project Member\n\nPRIV-03: Grant an org user access to a private project.\n\nAuthorization: only the project's creator or admin/owner (T-264-02). Access\nmanagement is creator-scoped, not RBAC-gated — no new permission slug needed.\n\n### Responses:\n\n**201**: Successful Response (Success Response)\nContent-Type: application/json\n\n**Example Response:**\n```json\n{\n \"user_id\": \"User Id\",\n \"email\": \"Email\",\n \"role\": \"Role\"\n}\n```\n\n**Output Schema:**\n```json\n{\n \"properties\": {\n \"user_id\": {\n \"t",
"inputSchema": {
"type": "object",
"title": "add_project_memberArguments",
"required": [
"project_id",
"user_id"
],
"properties": {
"user_id": {
"type": "string",
"title": "user_id"
},
"project_id": {
"type": "string",
"title": "project_id",
"format": "uuid"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_task_blocker",
"description": "Add Blocker\n\nTASK-06: Mark task_id as blocking another task (blocker → blocked).\nT-04 mitigation: self-blocking rejected (blocker_task_id == blocked_task_id → 422).\nSEC-MCP-01: both anchor (task_id) and target (blocked_task_id) must belong to the\ncaller's org before the INSERT — otherwise a caller could link a foreign org's task.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n\n**Output Schema:**\n```json\n{}\n```\n**422**: Validation Error\nContent-Typ",
"inputSchema": {
"type": "object",
"title": "add_task_blockerArguments",
"required": [
"task_id"
],
"properties": {
"task_id": {
"type": "string",
"title": "task_id",
"format": "uuid"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "add_task_dependency",
"description": "Add Dependency\n\nAdd a blocker to this task (from blocked perspective): blocker_task_id must complete first.\n\nSEC-MCP-01: both anchor (task_id) and target (blocker_task_id) must belong to the\ncaller's org before the INSERT — otherwise a caller could link a foreign org's task.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n\n**Output Schema:**\n```json\n{}\n```\n**422**: Validation Error\nContent-Type: application/json\n\n**Example Response:**\n```json\n{\n \"",
"inputSchema": {
"type": "object",
"title": "add_task_dependencyArguments",
"required": [
"task_id"
],
"properties": {
"task_id": {
"type": "string",
"title": "task_id",
"format": "uuid"
}
}
},
"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/ai.taskive/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.taskive/mcp"}) over MCP.
create_task ~628 tokenslog_decision ~509 tokensupdate_workflow_state ~402 tokenslist_tasks ~399 tokensupdate_context_entry ~391 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%2Fai.taskive%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.taskive%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.taskive%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.taskive%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fai.taskive%2Fmcp?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:3129264bd3eb6be7…, first seen 2026-10-17, included at leaf 12935 of 74,608. Version history · verify what your client received.
Compare: most reliable data servers · most reliable other servers · most reliable productivity servers · most reliable communication 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-26 18:05 UTC, the Taskive MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Taskive MCP server advertises 98 tools, including add_project_member, add_task_blocker, add_task_dependency, ai_health, archive_project.
Point your MCP client at this streamable-http endpoint: https://mcp.taskive.ai/mcp
Glimind scanned all 98 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.