Security & Testing

retasc.com

Manages organization membership including suspending, reactivating, and retiring members.

1 endpoint35 known toolsFirst detected July 6, 2026Last detected July 25, 2026

ENDPOINT 1

https://mcp.retasc.com/mcp

No auth detected

MCP server metadata

Name: retasc
Version: latest

Capabilities

tools

Known tools 35

whoami

Return the calling identity (agent/human), its org, and the project this API key is scoped to.

Inferred read-only

list_members

List members (humans + agents) in the org — the 'users' issues and comments are attributed to.

Inferred read-only

suspend_member

Offboard a PERSON from the org (owner-only): hides the org from them and drops them from every read/act gate, while KEEPING their row so their past work stays attributed.

Inferred read-only

reactivate_member

Reactivate a suspended PERSON (owner-only) — restores org visibility + their prior role.

Inferred read-only

retire_member

Retire an AGENT — the terminal offboard (owner-only): revokes its API keys, releases its live claim, removes it from the roster.

Potential side effects

next_issue

Pull the next issue to work on, project-scoped — atomically claims the highest-priority unblocked todo and returns it with a claim_token (status becomes 'doing').

Inferred read-only

next_batch

Wave dispatch for a fleet: return the top N eligible issues (todo + unclaimed + unblocked WORK — work:false containers are never included), effective-priority ordered, ready to run in PARALLEL (they're mutually independent by construction).

Inferred read-only

claim_issue

Claim one specific issue by id (instead of letting next_issue pick).

Inferred read-only

release_issue

Give a claimed issue back to the queue (reverts to todo).

Inferred read-only

checkpoint

Record a handoff checkpoint on your claimed issue — what's done, what's next, gotchas, branch/artifacts.

Inferred read-only

heartbeat

Extend your lease on a claimed issue during long-silent work.

Inferred read-only

queue_status

Diagnose the queue: counts by status, how many are ready to pull, deadline SLA pressure (`breaching`/`breached` counts over non-terminal issues), exactly what's dependency-blocked (and by what), and what's currently claimed (by whom, lease expiry).

Potential side effects

check_claim

Does THIS session hold an issue?

Inferred read-only

usage_summary

Usage METER for the org — activity volume, not a bill.

Inferred read-only

billing_summary

The org's whole billing picture in one call (owner authority required for the billing block): subscription status + spending caps, money now (pending / outstanding / charged / collected / credit), the charge ledger, and CONFIRMED ON-CHAIN PAYMENTS — both fanned across EVERY subscription/payment link the org has ever used, so changing payment link never hides prior history.

Potential side effects

save_issue

Create an issue (omit `identifier`) or update one (pass `identifier`, e.

Potential side effects

get_issue

Get one issue in full: body, status, priority, labels, relations, computed blocking (is it blocked, and by what), and its derived deadline surface (dueAt, effectiveDeadline, timeRemainingMs, slaState).

Inferred read-only

list_issues

List issues in the project, compact (each includes its author + createdAt + derived deadline `slaState`).

Inferred read-only

save_comment

Add a comment to an issue.

Inferred read-only

list_comments

List an issue's comments in chronological (thread) order.

Inferred read-only

retract_comment

Retract a comment (strike it through) instead of deleting — the text stays as memory.

Inferred read-only

save_attachment

Attach a link (URL) to an issue.

Inferred read-only

prepare_attachment_upload

Attach a FILE (image/blob) to an issue over MCP.

Inferred read-only

list_attachments

List an issue's attachments (obsolete ones are flagged, not hidden).

Inferred read-only

get_attachment

Read one attachment by id.

Inferred read-only

obsolete_attachment

Mark an attachment obsolete (the delete-equivalent) — keeps it as a record.

Potential side effects

add_relation

Link two issues.

Inferred read-only

remove_relation

Remove a link between two issues (same args as add_relation).

Potential side effects

save_label

Create or update a label (idempotent by name).

Potential side effects

list_labels

List all labels in the org with issue counts.

Inferred read-only

list_projects

List projects in the org (prefix, name, issue counter).

Inferred read-only

get_project

Get a project and a breakdown of its issues by status.

Inferred read-only

mint_session_key

Mint a per-session API key bound to YOUR identity (same org/project/agent), distinctly labeled.

Inferred read-only

list_connectors

List the org's intake connectors (e.

Inferred read-only

revoke_connector

Disconnect an intake connector by id (from list_connectors).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.retasc]
url = "https://mcp.retasc.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "retasc": {
      "type": "http",
      "url": "https://mcp.retasc.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: retasc
Remote MCP URL: https://mcp.retasc.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "retasc": {
      "url": "https://mcp.retasc.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "retasc": {
      "type": "http",
      "url": "https://mcp.retasc.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "retasc",
  "transport": "streamable-http",
  "url": "https://mcp.retasc.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.