Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Live data from 80+ official national company registries. Unmodified. For KYB and due diligence.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://openregistry.sophymarine.com/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http openregistry https://openregistry.sophymarine.com/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"openregistry": {
"url": "https://openregistry.sophymarine.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"openregistry": {
"type": "http",
"url": "https://openregistry.sophymarine.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://openregistry.sophymarine.com/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 sophymarine 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(3.0.0)은 32일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Real-time direct access to unmodified data and raw filings of about 80+ official government registries via MCP.
Tools: search companies, get profiles, officers, shareholders, charges, filings, and financial-statement documents.
Covers UK Companies House, Ireland CRO, France RNE, Spain BORME, Italy InfoCamere, Norway Brreg, Poland KRS, Netherlands KVK, Belgium KBO, Switzerland Zefix, Finland, Czechia, Korea, Taiwan, New Zealand, Cayman Island, Australia, Canada and a lot more.
Free tier; paid keys for higher quota and depth.
Data licensed from 🇬🇧 UK Companies House · 🇮🇪 CRO Ireland · 🇳🇴 Brønnøysund · 🇨🇭 Zefix · 🇵🇱 KRS Ministry of Justice — and a lot more.
Above: an AI agent walks the shareholders of *Iceland Foods Ltd* through 4 UK holding companies — *WD FF MIDCO → ICELAND VLNCO → LANNIS → WD FF LIMITED* — and surfaces the 8 individuals who actually own the chain (Tarsem Dhaliwal 41.35% as the largest shareholder, Walker family 51.31% combined). Every share count, every percentage, read verbatim from the registry's own CS01 PDFs.
We return the registry's own response — unmodified. Every field name, every status value, every raw filing byte (XHTML iXBRL / PDF / XBRL) is preserved exactly as the government's system emits it. The identifiers and jurisdiction routing let you reconstruct the government URL for any record. No aggregator markup. No field renames. No document re-rendering. No AI reinterpretation. No stale cache.
Chain queries across borders in a single prompt — a UK Ltd → its Luxembourg SARL → its Cayman LP → the Jersey trust → the individual beneficiary, all in one conversation. Walk ownership structures through 80+ jurisdictions to unmask the real person behind any company.
Hosted endpoint: `https://openregistry.sophymarine.com/mcp`
A platform by Sophymarine.
| 1. Live | Every tool call is a real-time query to the upstream government registry API at the moment you ask. |
| 2. Direct-to-government | No aggregator, no third-party data warehouse, no nightly scrape. Your AI talks to UK Companies House, France INSEE, German Registerportal, Korean FSS OpenDART directly. |
| 3. Unmodified + source-linked | Every field name, every status code, every raw filing byte returned verbatim. The registry's own identifiers are preserved so any response traces back to the government record. Enterprise tier adds pre-synthesised source_url / registry_url / data_license fields. |
| 4. Zero-stale | No cache layer we control can ever go stale. You see an update the moment the government records it. Contrast with commercial data providers that serve 6-24 hour-old snapshots. |
| 5. Stable | Production-grade reliability, running on Cloudflare Workers' global edge + a warm pool of per-jurisdiction workers for stateful registries. |
| 6. Cross-border | Chain queries across 80+ registries in a single prompt. Walk UK Ltd → LU SARL → KY LP → individual without leaving the conversation. |
| OpenRegistry | OpenCorporates | Companies House API direct | Bureau van Dijk Orbis | |
|---|---|---|---|---|
| Coverage | 80+ national registries | ~140, mostly aggregated from upstream sources | UK only | ~430M companies, aggregated |
| Data freshness | Live — every call hits upstream | Scrape-and-cache (hours–days lag) | Live | 7-day to quarterly refresh |
| Field shape | Verbatim upstream payload + unified envelope | Normalised to OC's own schema | Per-registry CH schema | BvD's own schema |
| Source identifier preserved | Yes — registry URL reconstructable from response | OC ID is primary; mapping back is lossy | Native | BvD ID is primary |
| Filing PDFs / iXBRL bytes | Returned raw | Metadata only; full bytes paywalled | Native | Paywalled |
| Cross-border chain walking | One MCP prompt, ≤80+ jurisdictions | Manual ID-stitching across countries | Out of scope (UK only) | Limited to BvD-mastered entities |
| Authentication | OAuth 2.1 + DCR | API key (signup required) | API key (signup required) | Per-seat license, $30k–$50k+/yr |
| Made for AI agents | MCP-native, JSON-RPC over Streamable HTTP | REST; no MCP wrapper | REST; no MCP wrapper | REST; no MCP wrapper |
One-liner. OpenCorporates and BvD are *aggregators* that re-shape and cache; CH-direct is single-jurisdiction. OpenRegistry is the layer between an AI agent and the original government APIs — verbatim, live, multi-country, no API key for the free tier.
Where OpenRegistry deliberately doesn't have data, the response carries a structured alternative_url pointing at the AML-obliged-only statutory portal. We don't pretend to have data we don't.
Three full request → response examples for the most common tools. All three reproducible on the free tier. Calls are JSON-RPC over MCP Streamable HTTP at https://openregistry.sophymarine.com/mcp; for brevity we show the tool name + arguments + the unwrapped response.
search_companies — find a UK company// Request
{ "name": "search_companies", "arguments": { "jurisdiction": "GB", "query": "Monzo Bank", "limit": 5 } }
// Response (truncated to 1 result) { "jurisdiction": "GB", "count": 5, "results": [ { "jurisdiction": "GB", "company_id": "09446231", "company_name": "MONZO BANK LIMITED", "status": "active", "incorporation_date": "2015-02-06", "registered_address": "Broadwalk House, 5 Appold Street, London, England, EC2A 2AG", "jurisdiction_data": { "company_number": "09446231", "company_status": "active", "company_type": "ltd", "date_of_creation": "2015-02-06", "title": "MONZO BANK LIMITED", "address_snippet": "Broadwalk House, 5 Appold Street, London, England, EC2A 2AG", "kind": "searchresults#company", "links": { "self": "/company/09446231" } // ... 20+ verbatim CH fields } } ] }
get_persons_with_significant_control — UK PSC for a known company// Request
{ "name": "get_persons_with_significant_control", "arguments": { "jurisdiction": "GB", "company_id": "OC404063" } }
// Response [ { "jurisdiction": "GB", "psc_id": "...", "name": "[REDACTED — UK CH residential-address suppression]", "kind": "individual-person-with-significant-control", "nature_of_control": ["ownership-of-shares-25-to-50-percent"], "notified_on": "2024-08-15", "is_active": true, "jurisdiction_data": { "etag": "...", "natures_of_control": ["ownership-of-shares-25-to-50-percent"], "notified_on": "2024-08-15", "country_of_residence": "United Kingdom", "date_of_birth": { "month": 7, "year": 1985 }, "address": { "country": "United Kingdom" }, "links": { "self": "/company/OC404063/persons-with-significant-control/individual/..." } // ... full CH PSC record } } ]
PSC ≠ shareholders. UK Companies House publishes a structured PSC register and a *separate* (filing-only) statement of capital. They disagree: a 10% shareholder appears in the statement of capital but not in PSC; a corporate trustee appears in PSC without being a shareholder. We surface both via
get_persons_with_significant_controlandget_shareholdersrespectively — see the shareholders-vs-PSC case study.
fetch_document — raw iXBRL annual accounts bytes// Request — get the document_id from list_filings or get_financials first
{ "name": "fetch_document", "arguments": { "document_id": "MzQ0MTUyNDU5N2FkaXF6a2N4", "max_bytes": 5000000 } }
// Response (metadata + base64-encoded body) { "jurisdiction": "GB", "document_id": "MzQ0MTUyNDU5N2FkaXF6a2N4", "content_type": "application/xhtml+xml", "size_bytes": 348721, "encoding": "base64", "content": "PCFET0NUWVBFIGh0bWwgUFVCTElDIC...", // signed proxy URL for human download / out-of-band fetch "proxy_url": "https://openregistry.sophymarine.com/document/gb/MzQ0MTUyNDU5N2FkaXF6a2N4/content?token=..." }
The content is the literal iXBRL bytes Companies House sends — your AI agent parses or re-renders as it sees fit. We don't re-encode, normalise tags, or extract figures into our own schema. Pass format: "png" (Browser Rendering required) to receive a rasterised page-by-page render of scanned PDFs instead.
OpenRegistry surfaces three distinct kinds of failure with structured responses so AI agents can branch on them.
Per-IP for anonymous, per-user for signed-in. The cross-border fan-out cap is a separate counter that limits how many *distinct* jurisdictions a caller can hit via search_companies in a rolling 60-second window.
When you exceed either limit, the response is HTTP 429:
{
"jsonrpc": "2.0", "error": { "code": -32000, "message": "rate-limited", "data": { "reason": "rate-limited", "retry_after_ms": 12400, "scope": "ip" // or "user" or "fanout" } } }
The HTTP layer also sets the standard Retry-After: 13 header (seconds, rounded up). Honour `retry_after_ms` exactly — exponential back-off on top is unnecessary; the limit window is fixed-rolling, not adaptive. Fan-out cap (scope: "fanout") is a 60-second rolling window — the second your oldest country falls off, you can hit a new one. Pro tier caps at 10 distinct countries / 60s, Max at 30, Enterprise unlimited.
Some beneficial-ownership registers became access-restricted to AML-obliged entities post-CJEU C-37/20 (DE, ES, IT, NL, LU, AT, MT, PT) and the Cayman Beneficial Ownership Transparency
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요