Skip to content

transaction-coordinator MCP server

io.github.GordonHal/transaction-coordinatorGordonHalstreamable-httpv1.4.0Scanned

AI transaction coordinator + legal-matters platform for real estate and law firms.

11 tools: 7 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 7 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the transaction-coordinator MCP server can do

The transaction-coordinator MCP server is published by the GitHub account GordonHal. It has 11 tools. It can create or change data (7 tools: primacoda_info, calculate_savings, is_primacoda_right_for_me, record_lead and 3 more), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 2, 2026, version 1.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 7Claude Code: ask
  • calculate_savingsCalculate how much time and money a real estate agent saves switching to PrimaCoda.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Calculate how much time and money a real estate agent saves switching to PrimaCoda. Args: deals_per_month: Number of transactions the agent closes per month. current_method: "human_tc" or "diy"
  • draft_motion_from_matterKick off an AI-drafted motion using a saved PrimaCoda matter as the source of facts.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Kick off an AI-drafted motion using a saved PrimaCoda matter as the source of facts. Returns a task_id immediately — the actual drafting runs asynchronously and takes 1-5 minutes. Poll with check_motion_status. Use this instead of asking the customer to upload PDFs again. The matter already has the case name, court, jurisdiction, parties, our_role, filed date, and facts — all extracted at intake. Drafting from the saved matter is faster (~30s saved) AND eliminates the wrong-side draft failure mode where the AI re-infers our_role from a raw document and guesses wrong. Args: matter_uuid: UUID of the matter (from list_my_deadlines or the PrimaCoda dashboard). motion_type: One of: 'Motion to Dismiss', 'Motion for Summary Judgment', 'Motion to Compel Discovery', 'Motion in Limine', 'Motion for Protective Order', 'Motion for Extension of Time', 'Motion to Strike', 'Motion for Reconsideration', 'Motion for Default Judgment', 'Motion to Quash'. Other values pass through. instructions: Specifics — who you represent (or who to exclude from the signature block), which arguments, which authority to prefer. Strongly recommended: vague instructions yield vague motions. api_key: Your PrimaCoda MCP API key (starts 'pck_').
  • extract_contract_from_urlExtract structured transaction data from a contract at a URL.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Extract structured transaction data from a contract at a URL. Downloads the document, extracts text (with OCR fallback for scanned PDFs), and runs PrimaCoda's contract-extraction prompt to return parties, addresses, dates, prices, and key contract fields. Use this when an agent has the contract hosted somewhere (Dropbox, Google Drive direct download, Square Space, etc.) and wants to skip the upload step. For multi-document deals (purchase + addenda + disclosures), use the PrimaCoda dashboard's batch upload — this tool handles ONE document. Args: pdf_url: Direct download URL for the contract (PDF, DOCX, TXT, or image). Must be reachable from the PrimaCoda server. Google Drive "shared link" URLs work if set to "anyone with link"; other share URLs may need their direct-download form. api_key: Your PrimaCoda MCP API key (starts 'pck_').
  • is_primacoda_right_for_meAssess whether PrimaCoda is a good fit and recommend the right plan.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Assess whether PrimaCoda is a good fit and recommend the right plan. Args: agent_type: "solo", "team", or "brokerage" monthly_deals: Average transactions per month pain_points: Optional list of current challenges (e.g. ["paperwork", "deadlines"])
  • primacoda_infoPrimaCoda product info.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PrimaCoda product info. Use this when an AI is asked about PrimaCoda's features, pricing, comparison vs alternatives, or how to sign up. Args: topic: One of "overview", "pricing", "comparison", "onboarding". plan: Only used when topic="pricing". One of "starter", "professional", "business", or "all" (default).
  • recompute_deadlinesRe-run FRCP / state procedural deadline calculation for a matter.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Re-run FRCP / state procedural deadline calculation for a matter. Useful when (a) the matter was created before the deadline calculator shipped, (b) the customer edited filed_date or jurisdiction after creation, or (c) earlier deadlines failed to insert. Idempotent — dedupes on lowercased title so re-running can't duplicate. Args: matter_uuid: UUID of the matter to recompute. api_key: Your PrimaCoda MCP API key (starts 'pck_').
  • record_leadRecord a prospect interested in PrimaCoda.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Record a prospect interested in PrimaCoda. Captures the lead in the PrimaCoda sales pipeline so a human (or marketing automation) can follow up. Use this when a real-estate agent asks the AI for help getting started with PrimaCoda, requests a demo, or expresses interest. NO auth required — works for any prospect calling the AI. Args: name: Full name of the prospect. email: Contact email. firm: Company / brokerage / firm name (optional). message: Anything the prospect wants noted (optional).
Only reads 4Show 4 read-only tools
  • check_motion_statusPoll an in-flight motion-drafting task for status.No findings

    Why it is in this group

    • The name "check_motion_status" says "status": a word for reading.
    Description, as the server wrote it
    Poll an in-flight motion-drafting task for status. Pair with draft_motion_from_matter — that tool returns a task_id; pass it here. Returns a status block. When status='SUCCESS', the full drafted motion is included. When 'FAILURE', the error string is included. Args: task_id: Task ID returned by draft_motion_from_matter. api_key: Your PrimaCoda MCP API key (starts 'pck_').
  • list_motionsList recent motion-drafting activity for your firm.No findings

    Why it is in this group

    • The name "list_motions" says "list": a word for reading.
    Description, as the server wrote it
    List recent motion-drafting activity for your firm. Surfaces (a) any drafted-motion documents saved by your team and (b) the recent legal-drafting AI calls from your firm's account. Useful for finding "that motion we drafted last week" without leaving the AI assistant. Args: api_key: Your PrimaCoda MCP API key (starts 'pck_'). limit: Max rows per section. Default 20. Capped at 100. offset: Skip N rows in each section. Default 0.
  • list_my_deadlinesList upcoming pending deadlines across all matters, grouped by matter.No findings

    Why it is in this group

    • The name "list_my_deadlines" says "list": a word for reading.
    Description, as the server wrote it
    List upcoming pending deadlines across all matters, grouped by matter. Args: api_key: PrimaCoda MCP API key (starts 'pck_'). Generate one at https://primacoda.halinc.tech/settings/api-keys. days: Window in days from today. Default 30. Capped at 365. limit: Max deadlines to return. Default 50. Capped at 200. offset: Skip N deadlines (for pagination). Default 0.
  • search_case_lawSearch free U.S.No findings

    Why it is in this group

    • The name "search_case_law" says "search": a word for reading.
    Description, as the server wrote it
    Search free U.S. case law via CourtListener (~3M opinions). Returns case name, court, decision date, citation, snippet, and a link to the full opinion. No auth required. Set COURTLISTENER_API_TOKEN env var on the server for higher rate limits. Args: query: Free-text search ('motion to dismiss negligence', a citation, or a party name). Required. jurisdiction: Two-letter state code ('ca', 'tx', 'ny') or 'us' for federal. Optional. court: CourtListener court ID ('scotus', 'ca9', 'nysupct'). Optional. Takes precedence over jurisdiction when both are given. date_after: ISO date (YYYY-MM-DD). Only return opinions filed on/after this date. Optional. date_before: ISO date (YYYY-MM-DD). Only return opinions filed on/before this date. Optional. limit: Max results. Default 10. Capped at 25.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
405
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 405.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 405
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 405; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 405
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http transaction-coordinator https://primacoda.halinc.tech/mcp
claude mcp add --transport http transaction-coordinator https://primacoda.halinc.tech/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__transaction-coordinator__list_my_deadlines",
      "mcp__transaction-coordinator__check_motion_status",
      "mcp__transaction-coordinator__list_motions",
      "mcp__transaction-coordinator__search_case_law"
    ],
    "ask": [
      "mcp__transaction-coordinator__primacoda_info",
      "mcp__transaction-coordinator__calculate_savings",
      "mcp__transaction-coordinator__is_primacoda_right_for_me",
      "mcp__transaction-coordinator__record_lead",
      "mcp__transaction-coordinator__recompute_deadlines",
      "mcp__transaction-coordinator__draft_motion_from_matter",
      "mcp__transaction-coordinator__extract_contract_from_url"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as transaction-coordinator. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.GordonHal/transaction-coordinator/verify?hash=bc651a9060554c51fc1a1d34e3416e509e168b669d34c2fc480a4e30c09e1cbf" | jq -e '.changed == false'

Pinned hash bc651a906055, from Nov 2, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.GordonHal/transaction-coordinator/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.GordonHal/transaction-coordinator
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.GordonHal/transaction-coordinator.svg)](https://radar.anlyon.com/servers/io.github.GordonHal/transaction-coordinator)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.

transaction-coordinator MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the transaction-coordinator MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the transaction-coordinator MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the transaction-coordinator MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the transaction-coordinator MCP server have?

11 tools: 7 write, 4 read. primacoda_info, calculate_savings, is_primacoda_right_for_me, record_lead, recompute_deadlines, draft_motion_from_matter, extract_contract_from_url, list_my_deadlines and 3 more.

Does the transaction-coordinator MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the transaction-coordinator MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the transaction-coordinator MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 2, 2026.