
Sec Contracts MCP server
online · 100% uptimeSEC Contracts MCP — material-contract exhibits (EX-10 / EX-4 / EX-2) found by CLAUSE LANGUAGE over…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Sec Contracts yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Sec Contracts tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Sec Contracts compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 241 ms
- faster than 57% of 30,031 servers
Release history: 5 versions in the registry since 2026-09-16, latest 2026-10-29, typically one every 14 days.
Install Sec Contracts in Claude Code, Cursor or VS Code
claude mcp add --transport http sec-contracts https://gateway.pipeworx.io/sec-contracts/mcp
What the publisher says
From the Sec Contracts repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/sec-contracts
Material-contract exhibits from SEC filings — credit agreements, indentures, merger agreements, employment and severance agreements — found by the clause language inside them, over SEC EDGAR full-text search. The inverted question edgar cannot answer: not "what did Adobe file" but "which credit agreements filed since 2025 contain a change-of-control clause".
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tools
- seccontractssearch(query, match?, exhibittype?, form?, since?, until?, company?, sic?, limit?, includesnippets?) — exhibits (EX-10 / EX-4 / EX-2, or any) whose text contains a phrase. One row per exhibit document: company, CIK, ticker, root form, filing date, exhibit type and the filer's exhibit description, a snippet around the match, the document URL and accession; plus the same rows grouped by filing.
- seccontracttext(url | adsh + filename + cik, max_chars?, offset?, find?) — the exhibit as paged plaintext. find jumps to the first occurrence of a phrase ("Change of Control" definition, "Termination Fee").
- seccontractsbycompany(company, exhibittype?, form?, since?, until?, limit?) — one filer's material contracts newest first, by ticker, name or CIK.
Auth
Keyless. SEC asks for a descriptive User-Agent on every request; the pack sends one.
Data sources
- — EDGAR full-text search. Indexes every document in a filing from 2001 onward; each hit carries filetype (EX-10.1, EX-4.2, 10-K…), filedescription, adsh, ciks, sics, display_names.
- — the exhibit documents themselves.
Things the next person would otherwise rediscover (all measured 2026-08-28):
- efts has no exhibit-type parameter. forms=EX-10 returns zero — forms filters the root form. Exhibit filtering is client-side on file_type, over-fetching 100 documents a page (up to 500 per call). EX-10(?!\d) is the prefix test, because EX-103 exists as a filer typo.
- No highlights. The search response carries no snippet. Snippets are produced by reading the first 1.5 MB of each matched exhibit and windowing the first occurrence of the phrase, five documents at a time.
- A one-sided dateRange=custom is ignored. startdt without enddt yields an empty filter and 2008 hits. Both ends are always sent.
- Unquoted words are ANDed (one matchphrase clause each); OR between terms works; a double-quoted phrase is exact; q= matches nothing. The by-company tool therefore queries a broad OR of contract words (agreement OR indenture OR amendment …) with a ciks filter.
- Archive URLs need the registrant's CIK, not the accession prefix. Filing-agent accessions (0001193125-… = Donnelley) return 503 on the agent-CIK path. Search rows carry the resolved cik and document_url for this reason.
- efts's response cache leaks across sics / ciks / entityName. The endpoint sits behind an API Gateway cache keyed on q, the date window, forms and from/page — but not on sics, ciks or entityName. Measured 2026-08-28: a sics=7372 request returned the unfiltered 10,000-hit result cached seconds earlier for the same q and dates, and the reverse leak (an unfiltered request served the software-only set) too. The body's echoed query shows which filters actually ran. The pack appends a negated nonsense token to q (-zqfs7372) whenever one of those filters is set — efts compiles it to a must_not that matches nothing (totals verified identical), and the cache key becomes unique per filter set — and re-checks sic/cik on every row, reporting in note if anything was dropped. Any other pack passing ciks/sics to efts is exposed to the same leak.
- Coverage floor is 2001-01-01; an earlier since is clamped and noted in the response.
Quick Start
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Sec Contracts: common questions
- Is Sec Contracts MCP server safe?
- Mostly: it is graded B (77/100). Read the Sec Contracts safety report
- How do I install Sec Contracts?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Sec Contracts need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Sec Contracts maintained?
- The last commit was 38 days ago (2026-09-26). The latest release is v0.2.0.
- Is Sec Contracts up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Sec Contracts compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 241 ms (faster than 57% of 30,031 servers). Full comparison.