@entyrix/mcp
[npm]
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).
Use the remote server (recommended)
Entyrix runs a remote MCP server (Streamable HTTP, protocol 2025-03-26 … 2026-07-28):
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:
Full instructions: https://entyrix.com/mcp.
This package: a stdio bridge
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.
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/[email protected], not latest): a local MCP server runs with your privileges, and an unpinned npx -y installs whatever is published next.
Tools
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.
Configuration
Development
Local stdio sanity-check:
npm run test:contract runs the bridge against the live server (no secret needed).
Quality gates
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.
Releasing
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.
License
MIT — see LICENSE.