cypher_report_issue
ActiveTool of cypher-mcp
File a field report about this service as a GitHub issue on the operator's repo. Found a tool's metadata or response wrong or confusing? Report it where the tool lives. The **author of record is your npub** — no npub / no proof, no issue — and it is stamped into the issue so the report is attributed to you, not the operator. Costs a small fee (a free write to an issue tracker would be abused). The report is PUBLIC and goes to the maintainers' normal triage; nothing is verified here. Returns the filed issue's repo, number, and url. If this operator has not enabled field reports, returns an "issue reporting not configured" situation and you are not charged.
Parameters schema
{
"type": "object",
"required": [
"npub",
"dpop_token",
"title",
"body"
],
"properties": {
"body": {
"type": "string",
"description": "The details — which tool, what was wrong, what you expected."
},
"npub": {
"type": "string",
"description": "Your Nostr public key (npub1...); the report's author of record."
},
"title": {
"type": "string",
"description": "One-line summary of the problem."
},
"tool_name": {
"type": "string",
"default": "",
"description": "Optional: the specific tool the report is about\n(e.g. \"schwab_get_option_chain\")."
},
"dpop_token": {
"type": "string",
"description": "Raw JSON of a kind-27235 Nostr event signed by npub —\nnot base64, not NIP-98 'Authorization: Nostr <b64>' framing. Its\n`u` tag must hold THIS tool's exact name (from tools/list), not\nthe endpoint URL; content:\"\", created_at within 60s of now, and a\nrandom `nonce` tag recommended. Or a cached dpop_token phrase."
}
},
"additionalProperties": false
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
cypher-mcp
https://github.com/lonniev/cypher-mcp
2/7 registries