Sub-ms PreToolUse firewall, feedback memory, and single-use permits for AI coding agents.
Mantisbt is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Connects Claude Code, Claude Desktop and other MCP clients to the MantisBT REST API. Read, create and update issues, notes, attachments, relationships, tags and versions without leaving the editor.
What it covers
- Issues: fetch one or up to 50 at once, filter lists, create, update, delete
- Notes, attachments, relationships, tags and monitors — including editing existing notes and adding watchers in the same call as an update
- Projects and versions: categories, members and versions in one call; create, rename, release and obsolete versions
- Metadata: enum values, available fields and your own profile, cached locally
Offline semantic search
search_issues finds issues by meaning, not just by wording: "duplicate entries in the invoice list" also finds reports that say "shown twice" or "double records". The embedding model runs locally — no OpenAI key, no external API. Ranking combines semantic similarity with keyword matching (BM25), so identifiers, error codes and version numbers are found exactly. The index updates incrementally on start. Enable with MANTIS_SEARCH_ENABLED=true.
Fewer tokens
The server counts and projects fields itself, so the model gets a compact answer instead of raw issue lists:
list_issueswithgroup_by: "status"— a status overview of 604 issues in 165 tokens instead of about 1.27 millionget_issuewithselect— five issues with only the fields you need, 96 % smallerresponse: "short"oncreate_issueandupdate_issuereturns only the core and the changed fields
Control over what the model can do
MANTIS_TOOLSETSoffers only the tool groups you list, e.g.issues,notes,metaMANTIS_DISABLE_DESTRUCTIVE=truehides every delete and remove tool- HTTP mode binds to
127.0.0.1by default and refuses to start without a bearer token (MCP_HTTP_TOKEN)
Works with localized installations
Status, priority, severity and the other enum fields accept canonical English names, localized names or numeric IDs. A German or French MantisBT works the same way as an English one, and status filters match by ID rather than by label.
Resources and prompts
- Resources such as
mantis://projects/{id}(project with users, versions and categories) andmantis://enumsfor clients that read MCP resources - Prompt templates for a structured bug report, a feature request, an issue summary and a project status report
Requirements
- Node.js 22 or newer
- MantisBT 2.23+ with the REST API enabled
- A MantisBT API token (My Account → API Tokens)
Install via npx -y @dpesch/mantisbt-mcp-server and set MANTIS_BASE_URL and MANTIS_API_KEY. Stdio is the default transport; Streamable HTTP is available with TRANSPORT=http. Open source under the MIT license.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'MANTIS_BASE_URL=${MANTIS_BASE_URL}' --env 'MANTIS_API_KEY=${MANTIS_API_KEY}' --transport stdio mantisbt-mcp '--' npx -y @dpesch/mantisbt-mcp-server
# 2 — ask your agent for something these tools do
# search_issues, get_search_index_status, rebuild_search_index and 41 more
It needs MANTIS_BASE_URL, MANTIS_API_KEY: this reads them from your environment, so export them first.
Mantisbt costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Mantisbt as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads MANTIS_BASE_URL (Base URL of the MantisBT REST API, e.g. https://your-mantis.example.com/api/rest), MANTIS_API_KEY (MantisBT API key (Profile → API Tokens in MantisBT)) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx MANTIS_BASE_URL …, setx MANTIS_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'MANTIS_BASE_URL=${MANTIS_BASE_URL}' --env 'MANTIS_API_KEY=${MANTIS_API_KEY}' --transport stdio mantisbt-mcp '--' npx -y @dpesch/mantisbt-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: MANTIS_BASE_URL — Base URL of the MantisBT REST API, e.g. https://your-mantis.example.com/api/rest; MANTIS_API_KEY — MantisBT API key (Profile → API Tokens in MantisBT). You set them in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
44 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Search MantisBT issues using natural language. Returns the most relevant issues
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Natural language search query |
| top_n | integer | no | Number of results to return (default: 10, max: 50) |
| select | string | no | Comma-separated list of fields to include for each result (e.g. "id,summary,status,handler,priority"). When provided, each matching issue is fetched from MantisBT and enriched with the requested field |
| highlight | yes | If true, adds a "highlights" field per result with query terms bolded (term) in the issue summary and a short description snippet. Note: highlights are keyword-based, not semantic — some results m |
…
No parameter schema on file.
Build or update the semantic search index for MantisBT issues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Optional: only index issues from this project |
| full | boolean | no | If true, clears the existing index and rebuilds from scratch |
Retrieve one or more MantisBT configuration options. Common option names: - "status_enum_string" — issue status values and their IDs - "priority_enum_string" — priority values - "severity_enum_string" — severity values - "resolution_enum_string" — resolution values - "reproducibility_enum_string"…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| options | array | yes | Array of configuration option names to retrieve |
… Return valid ID, name, and (if available) localized label for all issue enum fields. Use this tool before creating or updating issues to look up the correct value for severity, status, priority, resolution, or reproducibility. Example response (English installation): { "severity":…
No parameter schema on file.
… Despite its name, MantisBT's GET /lang returns only the language of the current user ({ strings, language }), not a list of all languages.
No parameter schema on file.
List all tags defined in the MantisBT installation. The MantisBT REST API exposes a GET /tags endpoint on some installations. If that endpoint is not available, this tool falls back to the local metadata cache populated by get_metadata.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number (default: 1) |
| page_size | integer | no | Tags per page (default: 50) |
… List all file attachments of a MantisBT issue. Returns an array of attachment objects, each containing id, filename, size in bytes, content_type, and download_url. Returns an empty array if the issue has no attachments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID |
Upload a file as an attachment to a MantisBT issue. Adds the file to the issue without modifying any issue fields or status. Returns the created attachment metadata on success. Provide exactly one of the two input modes: - file_path (preferred): absolute path to a local file — use this whenever…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID |
| file_path | string | no | Preferred: absolute path to the local file to upload — use this whenever the file exists on disk (mutually exclusive with content) |
| content | string | no | Fallback: Base64-encoded file content — only use when file_path is not available (mutually exclusive with file_path) |
| filename | string | no | File name for the attachment (required when using content; overrides the derived name when using file_path) |
| content_type | string | no | MIME type of the file, e.g. "image/png" (default: "application/octet-stream") |
| description | string | no | Optional description for the attachment |
List all saved MantisBT issue filters accessible to the current user. Filter IDs can be used with list_issues.
No parameter schema on file.
Retrieve one MantisBT issue by "id", or several by "ids" (1–50). Pass exactly one of the two. With "id": returns the issue with all fields including notes (each with view_url), attachments and relationships, unless "select" is given. With "ids": returns { issues, requested, found, failed } —…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | no | Numeric issue ID (use either id or ids) |
| ids | array | no | Several issue IDs (1–50) to fetch in one call (use either id or ids) |
| select | string | no | Comma-separated list of fields to include in the response (server-side projection, same as list_issues). Significantly reduces response size. Example: "id,summary,status,notes" |
…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | Array of numeric issue IDs to fetch (1–50). null is returned per ID on 404/403/error instead of failing the whole call. |
List MantisBT issues with optional filtering. Returns a paginated list of issues. Use the "select" parameter to limit returned fields and reduce response size significantly. Note: "assigned_to", "reporter_id", "status", and date filters are applied client-side (the MantisBT REST API does not…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Filter by project ID |
| page | integer | no | Page number (default: 1) |
| page_size | integer | no | Issues per page (default: 50, max: 50) |
| assigned_to | integer | no | Filter by handler/assignee user ID |
| reporter_id | integer | no | Filter by reporter user ID |
| filter_id | integer | no | Use a saved MantisBT filter ID |
| sort | string | no | Sort field (e.g. "last_updated", "id") |
| direction | string | no | Sort direction |
| select | string | no | Comma-separated list of fields to include in the response (server-side projection). Significantly reduces response size. Example: "id,summary,status,priority,handler,updated_at" |
| status | string | no | Filter issues by status name (e.g. "new", "feedback", "acknowledged", "confirmed", "assigned", "resolved", "closed") or use "open" as shorthand for all statuses with id < 80 (i.e. not yet resolved or |
| group_by | string | no | Return counts per group instead of issues: "status", "handler", "priority" or "category". All matching issues are counted (page, page_size and select are ignored). |
Create a new MantisBT issue. Returns the full created issue object including the assigned id, summary, status, priority, severity, category, reporter, created_at, and view_url. With response: "short" only id, summary, project, category, status, handler, created_at and view_url (default "full"; it…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| summary | string | yes | Issue summary/title (required) |
| description | string | yes | Detailed issue description (required). Do not create issues without a description. Plain text or Markdown. |
| project_id | integer | yes | Project ID the issue belongs to — use list_projects to discover project IDs |
| category | string | yes | Category name (required). Use get_project with include: ["categories"] to list available categories for the project. |
| priority | string | no | Priority level. Canonical English names: none, low, normal, high, urgent, immediate. Default: "normal". Use get_issue_schema to see localized labels. |
| severity | string | no | Severity level. Canonical English names: feature, trivial, text, tweak, minor, major, crash, block. Default: "minor". Use get_issue_schema to see localized labels. |
| handler_id | integer | no | Numeric user ID of the assignee. Alternative to the handler field — use one or the other, not both. |
| handler | string | no | MantisBT login name of the assignee. The server resolves the name to a user ID from the project member list. Use get_project with member_query or include: ["users"] to look up valid login names. |
| version | string | no | Affected product version name. Use get_project with include: ["versions"] to list available version names for the project. |
| target_version | string | no | Target fix version — version in which the issue is planned to be resolved. Use get_project with include: ["versions"] to list available version names. |
| fixed_in_version | string | no | Version in which the issue was fixed. Use get_project with include: ["versions"] to list available version names. |
| steps_to_reproduce | string | no | Step-by-step instructions to reproduce the issue. Plain text or Markdown. |
| additional_information | string | no | Additional context or notes about the issue. Plain text or Markdown. |
| reproducibility | string | no | How reliably the issue reproduces. Canonical English names: always, sometimes, random, have not tried, unable to reproduce, N/A. Use get_issue_schema to see localized labels. |
| view_state | string | no | Visibility of the issue: "public" (visible to all, default) or "private" (restricted to higher-access users). |
| custom_fields | array | no | Custom field values: [{field: {id|name}, value: "<string>"}]. Use get_issue_schema or get_metadata to discover available custom fields per project. |
| response | string | no | "full" (default): the whole issue as MantisBT returns it, including description, notes and history. "short": only the fields that confirm the change — far fewer tokens. The default changes to "short" |
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric issue ID to update |
| add_monitors | array | no | MantisBT login names to add as monitors (watchers) of the issue |
| remove_monitors | array | no | MantisBT login names to remove from the monitors of the issue; names that are not monitoring are ignored. Rejected when the server runs with MANTIS_DISABLE_DESTRUCTIVE=true |
| dry_run | yes | If true, return the patch payload that would be sent without actually updating the issue. Useful for previewing changes before committing them. | |
| note | string | no | Optional note text appended after a successful update (e.g. reason for a status change). Replaces a separate add_note call. |
| note_view_state | string | no | Visibility of the appended note: "public" (default) or "private". Only used when "note" is set. |
| response | string | no | "full" (default): the whole issue as MantisBT returns it, including description, notes and history. "short": only the fields that confirm the change — far fewer tokens. The default changes to "short" |
| fields | yes | — |
Permanently delete a MantisBT issue. This action is irreversible.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric issue ID to delete |
… Fetch all projects and their associated users, versions, categories, and tags from MantisBT and store them in the local metadata cache. Tags are fetched via the dedicated GET /tags endpoint when available. On installations where that endpoint is missing (MantisBT < 2.26), tags are collected by…
No parameter schema on file.
Return the cached MantisBT metadata (projects with their users, versions and categories, plus all tags). - detail: "summary" (default) — compact counts: project count, tag count, per-project counts of users, versions and categories, cached_at, ttl_seconds. - detail: "full" — the complete raw…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail | string | no | "summary" (default): counts only; "full": the complete raw cache |
| refresh | yes | Re-fetch all metadata from MantisBT first (default: false) |
… Return the complete raw MantisBT metadata cache: all projects with full fields, and per-project lists of users, versions, categories, plus all tags. If the cache does not exist or has expired (default TTL: 24 hours), it will automatically sync first. Use get_metadata with refresh: true to…
No parameter schema on file.
… Return all field names that are valid for the "select" parameter of list_issues and get_issue. Fields are discovered by fetching a sample issue from MantisBT (which reflects the server's active configuration — e.g. whether eta, projection, or profile fields are enabled) and merging the result…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Optional project ID to scope the sample issue fetch |
Return what is valid for issues on this MantisBT server, in one response: - fields: all field names valid for the "select" parameter of get_issue, list_issues and search_issues. Discovered from a sample issue (reflects the server's active configuration) plus fields MantisBT omits when empty…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Optional project ID to scope the sample issue used for field discovery |
… Add a user as a monitor (watcher) of a MantisBT issue. Monitors receive email notifications whenever the issue is updated. Returns { success, monitors } — "monitors" lists the login names now monitoring the issue. Use it to subscribe team members to issue updates without assigning them as the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID — use list_issues or get_issue to obtain issue IDs |
| username | string | yes | MantisBT login name (not the display name) of the user to add as monitor. Use get_project with member_query to discover valid login names for a project. |
… Remove a user from the monitor list of a MantisBT issue. The user will no longer receive email notifications for updates to this issue. Returns { success, removed, monitors } — "monitors" lists the login names still monitoring the issue. If the user was not a monitor, the call succeeds with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID |
| username | string | yes | MantisBT login name (not the display name) of the monitor to remove |
… List all notes (comments) attached to a MantisBT issue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID |
Add a note (comment) to an existing MantisBT issue. Returns the created note object including id, created_at, reporter, text, view_state, and a view_url linking directly to the note in the MantisBT web UI. Full UTF-8 text is supported. Markdown syntax is stored as-is — rendering depends on the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID — use list_issues or get_issue to obtain issue IDs |
| text | string | yes | Note text (minimum 1 character). Full UTF-8 including emoji is supported. Markdown is stored as-is. |
| view_state | string | no | Visibility of the note: "public" (visible to all, default) or "private" (visible only to users with sufficient access level). |
Permanently delete a note from a MantisBT issue. This action is irreversible — deleted notes cannot be recovered. Returns a plain-text confirmation message on success. Returns an error if the note does not exist or the current user lacks permission to delete it (MantisBT enforces access control:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID that owns the note |
| note_id | integer | yes | Numeric note ID to delete — obtain from get_issue (notes[].id) |
Create a new version in a MantisBT project. Returns the created version object (id, name, description, released, obsolete, timestamp). Version names must be unique within the project. Without timestamp, MantisBT uses the current date. Requires the manage_project_threshold access level in the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric ID of the project the version belongs to — use list_projects to discover project IDs |
| name | string | yes | Version name, e.g. "1.2.0" |
| description | string | no | Optional version description |
| released | no | Mark the version as released. MantisBT default: false | |
| obsolete | no | Mark the version as obsolete. MantisBT default: false | |
| timestamp | string | no | Version date as ISO 8601 string, e.g. "2026-09-27" or "2026-09-27T10:00:00+02:00". Determines the order in roadmap and changelog. |
Update an existing version of a MantisBT project. Only the fields you pass are changed. Returns the updated version object. Renaming a version also rewrites the version, target_version and fixed_in_version fields of all issues that reference it (including subprojects if versions are inherited).…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric ID of the project the version belongs to — use list_projects to discover project IDs |
| version_id | integer | yes | Numeric version ID — use get_project with include: ["versions"] to discover version IDs |
| name | string | no | New version name (must be unique within the project) |
| description | string | no | New version description |
| released | no | Released flag | |
| obsolete | no | Obsolete flag | |
| timestamp | string | no | Version date as ISO 8601 string, e.g. "2026-09-27" or "2026-09-27T10:00:00+02:00". Determines the order in roadmap and changelog. |
| next_version | string | no | Only with released=true: name of a follow-up version to create as unreleased placeholder, e.g. "1.2.1". Used as-is — no automatic numbering. |
… Mark a version as released and set its date (default: now). Optionally create a follow-up version in the same step. The follow-up version is only created when next_version is given; its name is used as-is — no automatic numbering. Returns { released: <version> } plus either next_version:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric ID of the project the version belongs to — use list_projects to discover project IDs |
| version_id | integer | yes | Numeric version ID — use get_project with include: ["versions"] to discover version IDs |
| timestamp | string | no | Release date as ISO 8601 string. Default: now. |
| next_version | string | no | Name of a follow-up version to create as unreleased placeholder, e.g. "1.2.1". Omit to only release. |
Permanently delete a version of a MantisBT project. This action is irreversible. MantisBT clears the version, target_version and fixed_in_version fields of all issues that reference the deleted version (including subprojects if versions are inherited). To retire a version without touching issues,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric ID of the project the version belongs to — use list_projects to discover project IDs |
| version_id | integer | yes | Numeric version ID — use get_project with include: ["versions"] to discover version IDs |
Get one MantisBT project: its master data (id, name, description, status, enabled, view_state, access_level, subprojects as id and name of the direct subprojects) and, on request, its categories, users and versions in the same call. - include: any of "categories", "users", "versions" (default:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric project ID — use list_projects to discover project IDs |
| include | array | no | Related data to add: "categories", "users", "versions" |
| access_level | integer | no | Only users at or above this access level; implies include "users" |
| member_query | string | no | Case-insensitive substring to find users by login name, real name or email; implies include "users" |
| obsolete | yes | Also return obsolete versions; implies include "versions" | |
| inherit | yes | Also return versions inherited from parent projects; implies include "versions" |
List all MantisBT projects accessible to the current API user.
No parameter schema on file.
… List all users with access to a specific MantisBT project. Returns an array of user objects, each containing id, name (login name), real_name, email, and access_level fields. Access level IDs: 10=viewer, 25=reporter, 40=updater, 55=developer, 70=manager, 90=administrator. Prerequisites:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric project ID — use list_projects to discover project IDs |
| access_level | integer | no | Return only users at or above this access level. Common values: 10=viewer, 25=reporter, 40=updater, 55=developer, 70=manager, 90=administrator. Omit to return all users. |
… List all versions defined for a MantisBT project. Returns an array of version objects, each containing id, name, released (boolean), obsolete (boolean), and timestamp (version date). To create, change, release or delete versions use create_version, update_version, release_version and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric project ID — use list_projects to discover project IDs |
| obsolete | yes | Include obsolete (deprecated) versions in the response. Default: false. Set to true to see all versions including those no longer actively used. | |
| inherit | yes | Include versions inherited from parent projects. Default: false. Set to true for sub-projects that share versions with a parent project. |
… List all categories available for a MantisBT project. Note: The MantisBT API returns global (cross-project) categories with a "[All Projects] " prefix. This tool strips that prefix so the returned names can be used directly when creating issues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric project ID |
… Search for users with access to a MantisBT project by name, display name, or email. Returns up to limit matching users (default: 10, max: 100). Matching is case-insensitive substring search across name, real_name, and email fields. Omit query to list the first limit users. Data is…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Numeric project ID |
| query | string | no | Case-insensitive substring to match against name, real_name, or email |
| limit | integer | no | Maximum number of results to return (default: 10, max: 100) |
Add a relationship between two MantisBT issues. Relationship types — use either type_id (numeric) or type_name (string): - … / "duplicate_of" — this issue is a duplicate of target - … / "related_to" — this issue is related to target - … / "parent_of" — this issue depends on target…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | The source issue ID (the one the relationship is added to) |
| target_id | integer | yes | The target issue ID |
| type_id | integer | no | Relationship type ID: 0=duplicate_of, 1=related_to, 2=parent_of (depends on), 3=child_of (blocks), 4=has_duplicate. Use either type_id or type_name. |
| type_name | string | no | Relationship type name as alternative to type_id. Accepted: "duplicate_of", "related_to", "parent_of" (or "depends_on"), "child_of" (or "blocks"), "has_duplicate". Dash variants (e.g. "related-to") al |
Remove a relationship from a MantisBT issue. Use get_issue first to retrieve the relationship IDs. The relationship_id is the numeric id field of a relationship object in the issue's relationships array (not the type ID).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | The issue ID the relationship belongs to |
| relationship_id | integer | yes | The numeric ID of the relationship to remove (from the relationships array in get_issue) |
Attach one or more tags to a MantisBT issue. Each tag can be specified either by ID or by name. If a tag name is provided that does not exist yet, MantisBT will create it automatically (requires tag_create_threshold permission, default: REPORTER). Requires tag_attach_threshold permission…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID |
| tags | array | yes | Tags to attach — each entry needs at least id or name |
Remove a tag from a MantisBT issue. Requires tag_detach_own_threshold (default: REPORTER) for own tags, or tag_detach_threshold (default: DEVELOPER) for tags attached by others.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue_id | integer | yes | Numeric issue ID |
| tag_id | integer | yes | Numeric tag ID to remove |
Retrieve the profile of the user associated with the current API key: id, name (login name), real_name, email, language, timezone, access_level, created_at and the accessible projects. "language" is the MantisBT language of this user (e.g. "german", "english") — use it as the hint for which…
No parameter schema on file.
Return the version of this mantisbt-mcp-server and of the connected MantisBT installation in one response: { mcp_server: { version, commit?, built_at? }, mantis: { installed_version, latest_version?, status?, github_note? } } mcp_server describes the running build: version ends in "-dev" unless…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_latest | yes | Whether to fetch the latest MantisBT release from GitHub and compare (default: true) |
… Returns the version of this mantisbt-mcp-server instance.
No parameter schema on file.
… Returns the version of the connected MantisBT installation and optionally compares it against the latest official release on GitHub.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_latest | yes | Whether to fetch the latest MantisBT release from GitHub and compare (default: true) |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mantisbt or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_issues | no tags | |
| get_search_index_status | no tags | |
| rebuild_search_index | state-write | state-write: declares readOnlyHint: false |
| get_config | no tags | |
| get_issue_enums | no tags | |
| list_languages | no tags | |
| list_tags | no tags | |
| list_issue_files | untrusted-input | untrusted-input: keyword "download" |
| upload_file | external-sinkstate-write | external-sink: keyword "upload_file"; state-write: declares readOnlyHint: false |
| list_filters | no tags | |
| get_issue | untrusted-input | untrusted-input: keyword "fetch" |
| get_issues | no tags | |
| list_issues | no tags | |
| create_issue | external-sinkstate-write | external-sink: keyword "create_issue"; state-write: declares readOnlyHint: false |
| update_issue | state-write | state-write: declares readOnlyHint: false |
| delete_issue | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| sync_metadata | untrusted-inputstate-write | untrusted-input: keyword "fetch"; state-write: declares readOnlyHint: false |
| get_metadata | untrusted-input | untrusted-input: keyword "fetch" |
| get_metadata_full | no tags | |
| get_issue_fields | no tags | |
| get_issue_schema | no tags | |
| add_monitor | state-write | state-write: declares readOnlyHint: false |
| remove_monitor | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_notes | no tags | |
| add_note | state-write | state-write: declares readOnlyHint: false |
| delete_note | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| create_version | state-write | state-write: declares readOnlyHint: false |
| update_version | state-write | state-write: declares readOnlyHint: false |
| release_version | state-write | state-write: declares readOnlyHint: false |
| delete_version | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_project | no tags | |
| list_projects | no tags | |
| get_project_users | no tags | |
| get_project_versions | no tags | |
| get_project_categories | no tags | |
| find_project_member | no tags | |
| add_relationship | state-write | state-write: declares readOnlyHint: false |
| remove_relationship | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| attach_tags | state-write | state-write: declares readOnlyHint: false |
| detach_tag | state-write | state-write: declares readOnlyHint: false |
| get_current_user | no tags | |
| get_version | no tags | |
| get_mcp_version | no tags | |
| get_mantis_version | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.18.4. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Mantisbt can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.