Home / MCP registry index / io.github.sadri-dridi/jira-key-shape
Jira Key Shape
io.github.sadri-dridi/jira-key-shape in the official MCP registry.
Endpoint https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/jira-key-shape/mcp. Source: github.com/sadri-dridi/named-mcp-utilities.
The registry describes it as: Check a Jira issue key shape. Key discarded.
Not read yet. The index re-reads every listed server about once a week, and this one is in the queue. You can check it yourself right now.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-sadri-dridi-jira-key-shape)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
Jira and Confluence MCP servers
| Confluence io.github.pipeworx-io/confluence | 47 tools, nothing matched 2026-10-22 |
| Ichimoku Signal io.github.Fizzl13/ichimoku-signal | 8 tools, nothing matched 2026-10-22 |
| ai.waystation/jira ai.waystation/jira | not reachable 2026-10-22 |
| Atlassian Rovo MCP Server com.atlassian/atlassian-mcp-server | not read yet |
| Jira io.github.pipeworx-io/jira | not read yet |
| Statuspage io.github.pipeworx-io/statuspage | not read yet |