Redacted Context MCP

Overview Schema Source Related Servers Discussions Admin

Github Search Issues

redctx_github_search_issues

Read-onlyIdempotent

Search a configured GitHub repo’s issues by words or qualifiers, excluding pull requests. Returns matches in one-line tab-separated format or “No matches.”

Instructions

Search one configured repo's issues with GitHub issue-search syntax and return matches (pull requests excluded) in the same tab-separated one-line format as redctx_github_list_issues, or No matches.. Use it to find issues by words or qualifiers; use redctx_github_list_issues to browse by state and label without a query. The query leaves the machine unredacted and is scoped automatically with repo:, is:issue and state:, so placeholders copied from redacted output will not match upstream; one request returns at most 100 issues. Titles and labels are redacted; titles are untrusted external text.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum issues to return. Default 30; values above 100 still return at most 100.
`query`	Yes	GitHub issue-search terms and qualifiers, for example `timeout label:bug`, sent as typed. The server appends `repo:`, `is:issue` and, unless `state` is `all`, `state:`.
`state`	No	Issue state filter: `open` (default), `closed`, or `all`.	open
`repo_alias`	No	Neutral repo alias from the local policy (list them with `redctx_github_repos`), not `owner/repo`. Default `context`. An unknown alias fails with `Unknown GitHub repo alias.`.	context

Output Schema

Name	Required	Description	Default
`text`	Yes	The tool output, identical to the text content block and already redacted: sensitive values appear as deterministic `[CATEGORY_<hex>]` placeholders (forms declared as aliases of one entity share its hex and add a form suffix, `[CATEGORY_<hex>.<form>]`) and files as `@p_<id>` references. When the result has `isError: true`, this is a fixed error message instead, such as a limit error or the notice that context access is blocked until the operator repairs the local redaction config.
`receipt`	Yes	Redaction statistics for this call only; never contains original values.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.10.0Oct 15, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum issues to return. Default 30; values above 100 still return at most 100."

addedInput schema / properties / query / description

Added value: +"GitHub issue-search terms and qualifiers, for example `timeout label:bug`, sent as typed. The server appends `repo:`, `is:issue` and, unless `state` is `all`, `state:`."

changedInput schema / properties / repo_alias / description

Previous value: -"Configured neutral repo alias, not owner/repo."New value: +"Neutral repo alias from the local policy (list them with `redctx_github_repos`), not `owner/repo`. Default `context`. An unknown alias fails with `Unknown GitHub repo alias.`."

addedInput schema / properties / state / description

Added value: +"Issue state filter: `open` (default), `closed`, or `all`."

addedOutput schema / description

Added value: +"Structured copy of every tool result: the output text plus a receipt of what redaction did."

addedOutput schema / properties / receipt / description

Added value: +"Redaction statistics for this call only; never contains original values."

addedOutput schema / properties / receipt / properties / counts_by_category / description

Added value: +"Placeholders substituted while producing this result (content and paths), keyed by category such as `PERSON`, `EMAIL` or `SECRET`; categories with none are omitted."

addedOutput schema / properties / receipt / properties / detector_profile / description

Added value: +"Active built-in detector profile: `default`, or `extended`, which adds more identifier types and prompt-injection markers."

addedOutput schema / properties / receipt / properties / detectors

Added value: +{
+  "description": "Present only when the server runs additional local detectors: one entry per detector, in load order.",
+  "items": {
+    "properties": {
+      "name": {
+        "description": "Detector name.",
+        "type": "string"
+      },
+      "nominated": {
+        "description": "Distinct values this detector nominated during the call; every occurrence of each is redacted.",
+        "type": "integer"
+      },
+      "positional": {
+        "description": "Nominated spans redacted only at their own position, because they were too long or exceeded the per-text value budget.",
+        "type": "integer"
+      },
+      "version": {
+        "description": "Detector version string.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "version",
+      "nominated",
+      "positional"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / text / description

Added value: +"The tool output, identical to the text content block and already redacted: sensitive values appear as deterministic `[CATEGORY_<hex>]` placeholders (forms declared as aliases of one entity share its hex and add a form suffix, `[CATEGORY_<hex>.<form>]`) and files as `@p_<id>` references. When the result has `isError: true`, this is a fixed error message instead, such as a limit error or the notice that context access is blocked until the operator repairs the local redaction config."

First observedv0.4.0Jun 25, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile, and the description goes well beyond them: the query leaves the machine unredacted, automatic `repo:`/`is:issue`/`state:` scoping means redacted placeholders will not match upstream, one request caps at 100 issues, and titles/labels are redacted with titles flagged as untrusted external text. These are exactly the non-obvious traits an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, well front-loaded with the output format and exclusion up front, then usage routing, then constraints. The first sentence is dense but every clause carries information; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering read-only/idempotent safety, the description supplies the remaining essentials: return format, result count cap, redaction behavior, and scope injection. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 3 is the baseline. The description nonetheless adds genuine query semantics the schema only partly conveys — that the query is sent as typed, that the server appends scope qualifiers, and the downstream consequence that placeholders copied from redacted output will not match.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (one configured repo's issues), names the syntax accepted, and explicitly excludes pull requests. It also clearly distinguishes itself from `redctx_github_list_issues`, so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ('find issues by words or qualifiers') paired with an explicit alternative and its triggering condition ('use `redctx_github_list_issues` to browse by state and label without a query'). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server