mcpbeat Sign in

WizerAPI Contract Intelligence MCP Server

not responding

WizerAPI Contract Intelligence is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Review contracts for risks: summary, severity-rated flags, key terms, and clause coverage.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 91 checks
2
Tools
read from the server
578 ms
Response time
average over 24h
open, no key
Access
streamable-http

WizerAPI Contract Intelligence does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add contract-intelligence --transport http https://mcp.wizerapi.com/contracts
Settings → Connectors → Add custom connector, then paste this address
https://mcp.wizerapi.com/contracts
~/.codex/config.toml
[mcp_servers.contract-intelligence]
url = "https://mcp.wizerapi.com/contracts"
.cursor/mcp.json
{
  "mcpServers": {
    "contract-intelligence": {
      "url": "https://mcp.wizerapi.com/contracts"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "contract-intelligence": {
      "type": "http",
      "url": "https://mcp.wizerapi.com/contracts"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analyze
analyze_contract
First-pass review of ONE contract: plain-language summary, risk flags (with severity low|medium|high and explanations), key terms (parties, dates, term, termination notice, governing law, payment terms, auto-renewal), and presence/absence of 8 standard clauses with verbatim evidence excerpts. Input: raw contract text 100-150,000 chars (≤50,000 on the Free plan); optional title, counterparty, and document_type (msa|nda|sow|employment|lease|services|license|other). Raw text is never stored — only a content hash and the structured result. METERED — the most expensive WizerAPI operation: 12 AU + 1 AU per 1,250 chars (a 30,000-char contract ≈ 36 AU; the 150,000-char max ≈ 132 AU). Call check_usage BEFORE long documents. Re-analyzing byte-identical text in the same organization is 0 AU (cached: true). Every result reports its au_cost. Automated first-pass assistance, NOT legal advice.
usage
check_usage
Check the current billing period usage for YOUR WizerAPI organization: plan, included AU, used AU, remaining AU, overage so far, and the per-minute rate limit. Costs 0 AU and is never blocked by the session budget. Call this BEFORE large metered jobs (theme extraction over many reviews, long contracts) to confirm quota headroom, and AFTER quota errors to see where you stand.

Endpoints

URLTransportStateLatencyChecked
https://mcp.wizerapi.com/contracts streamable-http answering 578 ms 6 min ago

Alternatives to WizerAPI Contract Intelligence

same job, measured the same way
P
PermitReporter — Georgia Permit Intelligence
by permitreporter

Source-linked Georgia permit search, county coverage, contractor signals, and authorized watches.

8 tools answering
K
Kai
by kailayerhq

Semantic code intelligence — call graphs, dependencies, impact analysis, and test coverage.

253 installs/wk local only
RevenueBase
by revenuebase

Find B2B contacts, inspect audience coverage, enrich emails, and verify deliverability.

answering
P
PermitReporter — US Building Permit Intelligence
by permitreporter

Source-linked building-permit search across 34 US states and DC, with county-level coverage.

8 tools answering
Feason Context
by feason-com

Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.

answering
F
First Party Data CRO
by atul0016

First-party funnel, rage-click, checkout, A/B test, and page-speed CRO intelligence.

93 installs/wk local only
Test Intel
by barissozudogru

Coverage analysis, untested function detection and complexity scoring for TS and JS.

52 installs/wk local only
Sheetspec
by helloo1568

Contract testing and quality gates for spreadsheets created by AI agents.

69 installs/wk local only

WizerAPI Contract Intelligence — questions

Answers built from our own checks of this server.

What can WizerAPI Contract Intelligence do?
It exposes 2 tools, read directly from the server on our last check. Among them: analyze_contract, check_usage. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is WizerAPI Contract Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 578 ms. The bar chart above shows every period we have measured.
Is WizerAPI Contract Intelligence still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists WizerAPI Contract Intelligence as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect WizerAPI Contract Intelligence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does WizerAPI Contract Intelligence need an API key?
No. WizerAPI Contract Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.