# FixMyContract — contract clause information (remote · www.fixmycontract.com)

Explains common contract clause types, with CUAD frequency data. Informational — not legal advice.

- Trust score: 25/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.fixmycontract.com`: 25/100 (this document), [markdown](https://verifymcp.io/servers/com-fixmycontract-info/api-mcp.md), [page](https://verifymcp.io/servers/com-fixmycontract-info/api-mcp)

## Channel facts

- Endpoint: `https://www.fixmycontract.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the FixMyContract — contract clause information MCP server?

FixMyContract — contract clause information is a hosted endpoint at https://www.fixmycontract.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-fixmycontract-info 'https://www.fixmycontract.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fixmycontract-info": {
      "url": "https://www.fixmycontract.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fixmycontract-info": {
      "type": "http",
      "url": "https://www.fixmycontract.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fixmycontract-info]
url = "https://www.fixmycontract.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fixmycontract-info": {
      "type": "remote",
      "url": "https://www.fixmycontract.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fixmycontract-info --url 'https://www.fixmycontract.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fixmycontract-info:
    url: "https://www.fixmycontract.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fixmycontract-info": {
      "Transport": "http",
      "Url": "https://www.fixmycontract.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fixmycontract-info -t streamable-http -u 'https://www.fixmycontract.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fixmycontract-info": {
      "type": "http",
      "url": "https://www.fixmycontract.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 25, −53)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.23 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-23 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 74)

First indexed and scored.

## MCP tools (4)

### `list_clause_types` (~60 tokens)

List contract clause types

Lists the contract clause types the FixMyContract glossary explains (slug, name, category), optionally filtered by category. Use a slug from this list with explain_clause_type.

Input parameters:

- `category` (string): Optional category name, e.g. "Liability".

### `explain_clause_type` (~116 tokens)

Explain a contract clause type

Returns the FixMyContract glossary entry for one clause type (for example "auto-renewal", "indemnification", "non-compete"): what the clause does, what to watch for and what is commonly asked for, plus how often it appears in the CUAD v1 dataset where available. General information about the clause type, not an assessment of any particular contract.

Input parameters:

- `clause` (string, required): Clause type name or glossary slug, e.g. "limitation of liability" or "auto-renewal-clause".

### `get_clause_frequency` (~80 tokens)

Clause frequency in public contracts (CUAD)

Returns how many of the 510 public commercial contracts in the CUAD v1 dataset contain a clause type, as counted for the FixMyContract /data/cuad page. Without an argument, returns every clause category, most common first.

Input parameters:

- `clause` (string): Optional clause type or CUAD category name, e.g. "cap on liability".

### `find_free_review_page` (~61 tokens)

Find a free contract review page

Returns links to the FixMyContract free review pages for a contract type (for example NDA, lease, freelance, employment), or all of them without an argument.

Input parameters:

- `contract_type` (string): Optional contract type, e.g. "NDA".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fixmycontract-info/api-mcp#diagnostics

## Score history

- 2026-11-05: 25
- 2026-11-04: 25
- 2026-11-03: 25
- 2026-11-02: 25
- 2026-11-01: 25
- 2026-10-31: 25
- 2026-10-30: 25
- 2026-10-29: 25
- 2026-10-28: 25
- 2026-10-27: 25
- 2026-10-26: 25
- 2026-10-25: 25
- 2026-10-24: 25
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74

## Common questions

### What is the FixMyContract — contract clause information MCP server?

FixMyContract — contract clause information is an MCP server listed in the public MCP registry as com.fixmycontract/info. Explains common contract clause types, with CUAD frequency data. Informational, not legal advice. This page covers its hosted endpoint (https://www.fixmycontract.com/api/mcp).

### Is the FixMyContract — contract clause information MCP server safe to use?

FixMyContract — contract clause information scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the FixMyContract — contract clause information MCP server expose?

FixMyContract — contract clause information exposes 4 tools: list_clause_types, explain_clause_type, get_clause_frequency, find_free_review_page. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.

### Does the FixMyContract — contract clause information MCP server require authentication?

Its publisher declares no required credentials for FixMyContract — contract clause information. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the FixMyContract — contract clause information MCP server still maintained?

FixMyContract — contract clause information is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.fixmycontract.com/api/mcp
- Website: https://www.fixmycontract.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-fixmycontract-info/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fixmycontract-info/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-fixmycontract-info/api-mcp