# Legal Reasoning Prover MCP for AI Agents AI Agent Connect

> Legal Reasoning Prover is an Connector that forces AI agents to produce rigorous, IRAC-based legal analysis grounded in actual US law. It prevents the common problem of hallucinated citations and logical leaps by requiring every conclusion to trace back to specific statutes, verifiable Bluebook-compliant cases, and clear jurisdictional rules. It ensures your agent doesn't just give a general answer but provides a defensible legal argument with specific procedural remedies.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_x5QP6bbbIPasqiBCFEkRUDREOoSZbvh26udzVNXF/ai-agent-connect
- **Tags:** legal-reasoning, us-law, irac, bluebook, structured-reasoning, decision-pivots, audit, compliance

## Description

Legal Reasoning Prover is an Connector that forces AI agents to produce rigorous, IRAC-based legal analysis grounded in actual US law. It prevents the common problem of hallucinated citations and logical leaps by requiring every conclusion to trace back to specific statutes, verifiable Bluebook-compliant cases, and clear jurisdictional rules. It ensures your agent doesn't just give a general answer but provides a defensible legal argument with specific procedural remedies. When you use this within the Vinkius catalog, you turn a generic chat into a rigorous drafting tool that follows ABA standards and Bluebook citations. You get a defensible analysis that actually leads to a motion or a filing, not just a summary of consult an attorney. This means you no longer have to worry about your agent making up a case name or skipping the logical bridge between a law and a fact. It demands that the agent identifies the correct circuit or state law and forces it to play devil's advocate by presenting the strongest counter-arguments. It is built for high-stakes legal work where precision is the only option.

## Tools

### validate_legal_reasoning
validate_legal_reasoning audits a legal argument to ensure it follows IRAC logic, uses real citations, and identifies the correct jurisdiction. It provides specific feedback on how to fix broken syllogisms or missing counter-arguments.

## Prompt Examples

**Prompt:** 
```
A client was fired for reporting safety issues. Analyze a wrongful termination claim under federal law.
```

**Response:** 
```
Verdict: JURISDICTION_BLIND. You stated 'federal law' but didn't identify the specific statute. 

| Statute | Elements | Requirements |
| --- | --- | --- |
| **SOX § 806** | Public company whistleblowers | Administrative exhaustion |
| **OSHA § 11(c)** | Workplace safety retaliation | Specific reporting triggers |

Name the statute, the court, and whether the employee exhausted administrative remedies before filing suit.
```

**Prompt:** 
```
Analyze if a non-compete in a contract is enforceable.
```

**Response:** 
```
Multiple rejections.

1. **AUTHORITY_UNGROUNDED** — 'courts have generally held' is weasel authority. Which court? Which case?
2. **JURISDICTION_BLIND** — non-compete enforceability varies by state. California bans them. Texas requires ancillary agreement. Illinois requires $75K salary. Which state governs?
3. **SYLLOGISM_BROKEN** — 'too broad' lacks element-by-element analysis of scope, duration, and restriction.
```

**Prompt:** 
```
Write an IRAC for a breach of contract where the defendant acted in bad faith.
```

**Response:** 
```
Verdict: REASONING_PROVEN.

* **Syllogism sound** — PDA elements mapped to facts (temporal proximity, no prior warnings, comparator retention).
* **Authority grounded** — McDonnell Douglas and Ortiz v. Werner properly cited.
* **Jurisdiction identified** — NDIL, 7th Circuit, 28.U.S.C. § 1331.
* **Counter addressed** — pretext analysis distinguishes performance defense.
* **Remedy specific** — EEOC timeline, damages cap, and statutory fees.
```

## Capabilities

### Block fake citations
It catches fabricated case names and placeholder parties before they reach your draft.

### Enforce IRAC structure
It maps every legal conclusion back through Issue, Rule, Application, and Conclusion steps.

### Identify jurisdiction
It forces the agent to name the specific court, governing law, and choice-of-law basis.

### Force counter-arguments
It requires the agent to disclose and distinguish adverse controlling authority per ABA rules.

### Define procedural remedies
It ensures every analysis ends with a specific motion type, statutory basis, and relief sought.

### Verify Bluebook citations
It checks for proper reporter volumes, page numbers, and court designations.

## Use Cases

### Wrongful Termination Analysis
An associate asks about a whistleblower claim. The Connector flags the request for federal law as too vague and demands the specific statute like SOX 806.

### Contract Enforceability
A user asks about a non-compete. The Connector catches the lack of state-specific analysis and demands a jurisdiction check for California versus Texas.

### Motion to Dismiss
A lawyer drafts a 12(b)(6) argument. The Connector verifies that the facts actually meet the plausibility standard required by the cited case.

### Compliance Audit
A corporate counsel checks a new policy. The Connector ensures the agent identifies the correct choice-of-law basis for multi-state operations.

## Benefits

- Stop hallucinated cases from ruining your credibility. validate_legal_reasoning catches fake citations and weasel authority before they make it into your draft.
- Ensure every conclusion is logically sound. The Connector forces a strict IRAC flow so your agent can't leap from facts to conclusions without a rule.
- Eliminate jurisdiction blindness. Your agent will stop giving generic US law answers and start naming specific circuits and state-specific rules.
- Meet ABA professional standards. By forcing the disclosure of adverse authority, the Connector ensures your analysis is balanced and legally responsible.
- Turn analysis into action. Instead of vague advice, the tool requires a specific procedural vehicle like a 12(b)(6) motion or a specific statutory basis.
- Maintain Bluebook compliance. Every citation is checked for volume, reporter, page, and court, ensuring your work meets professional standards.

## How It Works

The bottom line is your AI agent stops guessing and starts drafting defensible legal arguments.

1. Input your legal issue or a draft analysis into your AI client.
2. The Connector audits the logic against US legal frameworks and citation standards.
3. You receive a verdict on the reasoning's validity with specific instructions on what to fix.

## Frequently Asked Questions

**Can Legal Reasoning Prover help me avoid fake case citations?**
Yes. It identifies fabricated case names and weasel authority, ensuring that every citation your AI client provides is a real, verifiable Bluebook entry.

**How does Legal Reasoning Prover ensure my legal analysis is logically sound?**
It enforces a strict IRAC structure. This means your agent must show the logical bridge between a legal rule and the specific facts of your case before reaching a conclusion.

**Does Legal Reasoning Prover work for state and federal law?**
It covers both. It forces your agent to identify specific federal circuits, state statutes, and choice-of-law bases rather than giving generic answers.

**Can I use Legal Reasoning Prover to check for ABA compliance?**
Yes. It specifically requires the agent to disclose adverse controlling authority, which is a core requirement of ABA Model Rule 3.3(a)(2).

**What does Legal Reasoning Prover do about jurisdiction issues?**
It eliminates jurisdiction blindness. Your AI client will be forced to name the specific court and governing law for every analysis it performs.

**Will Legal Reasoning Prover help me draft specific motions?**
It does by requiring a specific procedural remedy. Instead of general advice, it forces the agent to identify the specific motion type and statutory basis needed.

**Does it verify if cited cases actually exist?**
It catches the most common hallucination patterns — placeholder names like 'Smith v. Jones' and 'Doe v. Roe', weasel authority language like 'courts have generally held', and citations that lack proper Bluebook format. It cannot access legal databases to verify every case, but it forces the agent to provide full citation details (party names, reporter, court, year, specific holding) — which dramatically reduces fabrication because the agent must commit to verifiable specifics.

**Is it only for litigation or does it work for transactional law?**
The IRAC framework is most natural for litigation analysis, but the five pivots apply broadly. For transactional work: the 'syllogism' becomes 'does the contract structure achieve the stated objective?', 'authority' becomes 'is the statutory basis for this structure valid?', 'jurisdiction' becomes 'which state law governs this agreement?', and 'remedy' becomes 'what happens if the counterparty breaches?' The reasoning validation is universal — the domain language adapts.

**Does it generate legal advice?**
No. Legal Reasoning Prover generates zero content. It validates the STRUCTURE of legal reasoning — whether the argument follows IRAC, whether citations are properly formed, whether jurisdiction is identified, whether counter-arguments are addressed. The agent does the legal analysis; the tool proves whether that analysis is structurally sound. It is a reasoning quality gate, not a legal advisor.