Is the Featurejet Feedback Board MCP server down?

mcp-registry/com.featurejet/feedback-board · v1.28.1

healthy
Last checked 2026-10-22 13:37 UTC · handshake 244ms

As of 2026-10-22 13:37 UTC, the Featurejet Feedback Board MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 98.7% of Glimind's liveness checks. It had 83 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
98.7%
checks observed
3,737
outages (90d)
83
tools
22

The feedback board your AI agents work from: users vote, agents build over MCP. 22 tools.

Install Featurejet Feedback Board MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http featurejet-feedback-board-mcp-server https://mcp.featurejet.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "featurejet-feedback-board-mcp-server": {
      "type": "http",
      "url": "https://mcp.featurejet.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (69/100)

D (69/100): 0 error(s), 4 warning(s) across 22 tool(s); ~2,661 tokens of tool definitions.
Scores higher than 4% of 15,511 MCP servers Glimind has audited.
Its tool list costs an agent ~2,661 tokens per session — more than 50% of servers.
67 → 69 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints0
Token cost100
Client compatibility100
Protocol100
Reliability75
Stability100

What to fix (4)

22 of 22 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 →

Tools: add_evidence, claim_post, create_board, create_comment, create_post and 17 more

59 parameter(s) across 19 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 →

Tools: add_evidence, claim_post, create_board, create_comment, create_post and 14 more

8 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 →

Tools: claim_post, create_board, create_comment, create_post, delete_post and 3 more

Reachable 98.7% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Auto-fix: 20 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 19 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.featurejet%2Ffeedback-board/fixes

add_evidence 1 change
{
  "name": "add_evidence",
  "description": "Attach implementation evidence to a post (shown publicly).\n\n        kind is one of branch|commit|pr|transcript|url; ref is the branch\n        name, commit sha, or URL. Voters see these in the post page's\n        \"Implementation\" section.\n        ",
  "inputSchema": {
    "type": "object",
    "title": "add_evidenceArguments",
    "required": [
      "slug",
      "post_id",
      "kind",
      "ref"
    ],
    "properties": {
      "ref": {
        "type": "string",
        "title": "Ref"
      },
      "kind": {
        "type": "string",
        "title": "Kind"
      },
      "slug": {
        "type": "string",
        "title": "Slug"
      },
      "label": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Label",
        "default": null
      },
      "post_id": {
        "type": "integer",
        "title": "Post Id"
      },
      "action_key": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Action Key",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
claim_post 1 change
{
  "name": "claim_post",
  "description": "Atomically claim a post before working on it (double-work guard).\n\n        ttl_seconds defaults to 3600 (max 86400); re-claiming with the same\n        key extends the lease. Returns 409 if another key holds a live claim.\n        ",
  "inputSchema": {
    "type": "object",
    "title": "claim_postArguments",
    "required": [
      "slug",
      "post_id"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "title": "Slug"
      },
      "post_id": {
        "type": "integer",
        "title": "Post Id"
      },
      "agent_label": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Agent Label",
        "default": null
      },
      "ttl_seconds": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Ttl Seconds",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_board 1 change
{
  "name": "create_board",
  "description": "Create a new feedback board, as a DRAFT.\n\n        `slug` is the board's URL path segment (lowercase, hyphenated, unique);\n        `name` is the display name. The new board's public URL 404s until a\n        human publishes it from the dashboard -- `publish_board` is off by\n        default (403 `publish_disabled`).\n        ",
  "inputSchema": {
    "type": "object",
    "title": "create_boardArguments",
    "required": [
      "name",
      "slug"
    ],
    "properties": {
      "name": {
        "type": "string",
        "title": "Name"
      },
      "slug": {
        "type": "string",
        "title": "Slug"
      },
      "description": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Description",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

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.featurejet/feedback-board"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.featurejet/feedback-board"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.featurejet%2Ffeedback-board.svg)](https://glimind.com/server/mcp-registry%2Fcom.featurejet%2Ffeedback-board?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.featurejet%2Ffeedback-board?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.featurejet%2Ffeedback-board.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.featurejet%2Ffeedback-board.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.featurejet%2Ffeedback-board?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3e7f463ed77eb0e2…, first seen 2026-10-17, included at leaf 4390 of 46,243. Version history · verify what your client received.

Tools (22)

Compare: most reliable other servers · most reliable data servers · most reliable communication servers · most reliable security servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Featurejet Feedback Board MCP server down right now?

As of 2026-10-22 13:37 UTC, the Featurejet Feedback Board MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 98.7% of Glimind's liveness checks. It had 83 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Featurejet Feedback Board MCP server provide?

Featurejet Feedback Board MCP server advertises 22 tools, including add_evidence, claim_post, create_board, create_comment, create_post.

How do I install Featurejet Feedback Board MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.featurejet.com/mcp

Is the Featurejet Feedback Board MCP server safe to connect to an AI agent?

Glimind scanned all 22 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.

Operator of Featurejet Feedback Board MCP server?

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.

Feedback
Help us improve