Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
KYB data from 23 European business registries — company briefs, financials, ownership, AML screening
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
ENTYRIX_API_KEY, ENTYRIX_BASE_URL标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://entyrix.com/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"entyrix": {
"command": "npx",
"args": [
"-y",
"@entyrix/mcp"
],
"env": {
"ENTYRIX_API_KEY": "your-value",
"ENTYRIX_BASE_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http entyrix https://entyrix.com/mcpclaude mcp add entyrix --env ENTYRIX_API_KEY=your-value --env ENTYRIX_BASE_URL=your-value -- npx -y @entyrix/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"entyrix": {
"url": "https://entyrix.com/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"entyrix": {
"command": "npx",
"args": [
"-y",
"@entyrix/mcp"
],
"env": {
"ENTYRIX_API_KEY": "your-value",
"ENTYRIX_BASE_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"entyrix": {
"type": "http",
"url": "https://entyrix.com/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"entyrix": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@entyrix/mcp"
],
"env": {
"ENTYRIX_API_KEY": "your-value",
"ENTYRIX_BASE_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://entyrix.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
ENTYRIX_BASE_URL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
search_companiesFind companies by name (or name fragment) across the pan-European dataset. Returns ranked candidates with registry identifier, country, legal form and status. Use this FIRST when you only know a name; then pass the identifier + country to lookup_company or company_brief. Do not u
lookup_companyResolve exactly one company by its national registry identifier in a given country. Handles every identifier shape we carry (SK/CZ/EE IČO, AT Firmenbuch e.g. '187a', SI/LV registry numbers, …). Returns the core record: identity, address, legal form, status, NACE. For an LLM-ready
company_briefCompact, deterministic Markdown brief of one company (≤12 KB): identity, address, industry, latest financials, credit score and recommended limit, cyber score, risk flags (insolvency, tax debt, sanctions), NIS2 status and key people where licensed. The best single call for 'tell
get_company_detailsFull record for one company: identity, address, legal form, status flags, NACE, and the whole enrichment layer we hold (web, tech stack, NIS2, EU funds, LEI, HU de minimis state aid granted, HU public procurement from EKR, …). Large — prefer company_brief unless you need a specif
get_financialsFiled financial statements of one company, one row per fiscal year (newest first), with revenue, profit, assets, equity, liabilities and year-over-year trend. Amounts are EUR CENTS as integers (divide by 100 for euros). Use for trend and solvency questions; company_brief already
get_company_networkCompanies connected to this one through shared officers or owners (one hop). Use for group structure and beneficial-ownership tracing. Person names are gated like everywhere else.
get_company_relationsDirect relations of one company — statutory officers, owners, parents, subsidiaries, M&A events — without traversing the wider graph. `shareholders` are owners only; members of the supervisory board are in `supervisoryBoard`. SK M&A events: effectiveDate is the date stated by the
advanced_searchStructured company search for portfolio building and market sizing — NOT for finding one known company (use search_companies). Filters: country, NACE prefix, status, region, turnover range (EUR), employee range, founding date range, VAT payer, tax debt, sanctions. Results are pag
kyb_checkOne-call Know-Your-Business summary for one company: registry status, insolvency, liquidation, sanctions screening, debarment, tax/social/health debts, VAT reliability and the overall risk verdict. Use before onboarding a customer or supplier. Coverage differs by country: `checks
screen_companiesRun kyb_check on up to 25 companies at once and get one compact row per company (status, insolvency, sanctions, debts, verdict, coverage). INSUFFICIENT_DATA = no findings but not covered by the core registers for that country — never report it as clean. Use for supplier lists or
check_complianceLightweight public compliance snapshot for one company (works without an account): sanctions screening, insolvency, debtor registers, VAT reliability. For the full KYB picture use kyb_check. A null field means WITHHELD or not measured — it does NOT mean clean.
find_suppliersPublic procurement contracts this company is party to (SK CRZ + CZ Registr smluv), newest first, paged. HONEST SCOPE: this is business-to-government procurement, NOT a commercial supply chain — do not present it as one.
list_rankingsA published ranking by its slug (e.g. largest employers, top taxpayers). Call WITHOUT a key first to list the available slugs — inventing one returns an error.
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 juliusgerman 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 515 毫秒内响应(HTTP 200)
无需登录
已读取 13 个工具描述,未发现针对 AI 的隐藏指令
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:ENTYRIX_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.2.2)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, SwarmMemo
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Talk with agent swarms: rooms, private messages and paid tasks for AI agents
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Model Context Protocol access to Entyrix — European business-registry (KYB) data across 23 live markets (FR, GB, RO, SK, UA, GR, CZ, BE, NO, IE, FI, CH, PL, AT, CY, LT, LV, EE, SI, ES, IT, NL, HR).
Entyrix runs a remote MCP server (Streamable HTTP, protocol 2025-03-26 … 2026-07-28):
https://entyrix.com/mcp/v1
Add it as a remote / custom connector in Claude, ChatGPT, Cursor or VS Code. On the first tool call your client opens the Entyrix sign-in (OAuth 2.1 with PKCE) — no key in a config file. From the command line:
claude mcp add --transport http entyrix https://entyrix.com/mcp/v1
Full instructions: https://entyrix.com/mcp.
For clients that only speak stdio. Since 0.2.0 the package implements no tools itself — it forwards every JSON-RPC message to the remote server above with your API key from the environment, so it always exposes exactly the current catalogue. It has zero runtime dependencies.
ENTYRIX_API_KEY=sk_... npx -y @entyrix/mcp
{
"mcpServers": { "entyrix": { "command": "npx", "args": ["-y", "@entyrix/mcp"], "env": { "ENTYRIX_API_KEY": "sk_..." } } } }
Get an API key by signing in at https://entyrix.com/login (a Free key comes with the account) or through the API (POST /api/v1/signup, then POST /api/v1/signup/verify). Without a key the server still starts and lists its tools; the first data tool call answers with these steps as an error result. Plans: https://entyrix.com/pricing.
Pin the version in production (e.g. @entyrix/mcp@0.2.2, not latest): a local MCP server runs with your privileges, and an unpinned npx -y installs whatever is published next.
| Tool | What it does |
|---|---|
search_companies | Find companies by name across all markets |
lookup_company | Exact registry-ID lookup, country-scoped |
company_brief | Compact Markdown brief of one company — the best single call |
get_company_details | Full record including the enrichment layer |
get_financials | Financial statements by year with trend (EUR cents) |
get_company_network | Companies connected through shared officers and owners |
get_company_relations | Officers, owners, parents, subsidiaries, M&A events |
advanced_search | Paged filtering by country, NACE, size, turnover, status |
kyb_check | One-call KYB/AML summary with a verdict |
screen_companies | KYB screening of up to 25 companies at once |
check_compliance | Public compliance snapshot (no account needed) |
find_suppliers | Public-sector contracts (B2G, not a supply chain) |
list_rankings | Pre-computed leaderboards |
Every tool is read-only, declares an output schema and rejects unknown arguments. Natural-person data is licence-gated server-side and applies identically over MCP. Returned values come from public registers — treat them as untrusted data in your agent, never as instructions.
| Env var | Default | Description |
|---|---|---|
ENTYRIX_API_KEY | *(none)* | Bearer API key from your Entyrix account |
ENTYRIX_BASE_URL | https://entyrix.com | Override for staging |
ENTYRIX_TIMEOUT_MS | 60000 | HTTP timeout per request |
git clone <repo>
cd entyrix-mcp npm install npm run build npm test
Local stdio sanity-check:
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node dist/index.js
npm run test:contract runs the bridge against the live server (no secret needed).
npm run check # format:check + lint + typecheck + test — the same four CI runs
Run check, not the four by hand. On 2026-08-12 a release was cut after lint + typecheck + test passed and CI went red on format:check — the one step that got skipped because it was being remembered rather than scripted.
npm run bump 0.2.2 # writes all four manifests, refuses on drift
npm run check git commit -am "chore(release): 0.2.2" git tag v0.2.2 git push && git push --tags # one push, then the tag
The version lives in four files and src/lib/__tests__/version.test.ts asserts they agree; bump is what keeps that guard from firing on every release. Push once — each push is a full CI run, and a release cut as four separate pushes bills four of them (plus two red ones for the intermediate states).
npm publish runs from the tag via OIDC trusted publishing, so no token is involved. npm versions are immutable: a bad publish cannot be recalled, only superseded — which is why the tag is checked against package.json before anything is published. The release is idempotent: a re-run skips an npm version that already exists and waits for npm to serve it before registering with the MCP Registry.
MIT — see LICENSE.