Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

InnoDay

PYPI · INNODAY · SCANNED SEP 20

Unified ticketing MCP server for Jira, Linear, Trello, Notion, and GitHub Issues.

Available components

pypi · innoday 1
0 this week 1 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency6
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the InnoDay MCP server?

InnoDay runs locally as a PyPI package, launched with uvx innoday. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · innoday

# add to Claude Code
claude mcp add havilandsoftware-mcp-server-innoday -- uvx innoday
// .cursor/mcp.json
{
  "mcpServers": {
    "havilandsoftware-mcp-server-innoday": {
      "command": "uvx",
      "args": [
        "innoday"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "havilandsoftware-mcp-server-innoday": {
      "command": "uvx",
      "args": [
        "innoday"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add havilandsoftware-mcp-server-innoday -- uvx innoday
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "havilandsoftware-mcp-server-innoday": {
      "type": "local",
      "command": [
        "uvx",
        "innoday"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add havilandsoftware-mcp-server-innoday --command uvx --arg innoday
# ~/.hermes/config.yaml
mcp_servers:
  havilandsoftware-mcp-server-innoday:
    command: "uvx"
    args: ["innoday"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "havilandsoftware-mcp-server-innoday": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "innoday"
      ]
    }
  }
}
# add to Vellum
assistant mcp add havilandsoftware-mcp-server-innoday -t stdio -c uvx -a innoday
// mcp.json
{
  "mcpServers": {
    "havilandsoftware-mcp-server-innoday": {
      "command": "uvx",
      "args": [
        "innoday"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 0
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
  • 26 Jul 26 0

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/innoday@0.112.2-beta

Provenance Version not published

The package exists but this version is not published, so there is no artifact to attest.

Result Version not published
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the InnoDay MCP server?

InnoDay is an MCP server listed in the public MCP registry as io.github.havilandsoftware/mcp-server-innoday. Unified ticketing MCP server for Jira, Linear, Trello, Notion, and GitHub Issues. This page covers its PyPI package (innoday).

Is the InnoDay MCP server safe to use?

InnoDay scores 1 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the InnoDay MCP server still maintained?

InnoDay is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.