getregdata-mcp 1.0.3 → 1.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -3
- package/actors.js +1440 -32
- package/index.js +33 -21
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# getregdata MCP server
|
|
2
2
|
|
|
3
3
|
An [MCP](https://modelcontextprotocol.io) server that gives any MCP-capable agent
|
|
4
|
-
(Claude Desktop, Claude Code, Cursor, Cline, Windsurf,
|
|
5
|
-
access to **
|
|
4
|
+
(Claude Desktop, Claude Code, Cursor, Cline, Windsurf, ...) direct
|
|
5
|
+
access to **25+ official business-registry actors** for KYC/AML, credit-risk,
|
|
6
6
|
due-diligence and B2B data across **11 jurisdictions**: Poland, Germany, Italy,
|
|
7
7
|
Spain, Austria, France, Belgium, Czechia, Slovakia, the US (California) and the UAE -
|
|
8
8
|
plus a cross-border adverse-media screener.
|
|
@@ -40,6 +40,21 @@ Add to your MCP config (`claude_desktop_config.json`, or `.mcp.json` for Claude
|
|
|
40
40
|
Same block in the client's MCP settings (`mcp.json` / MCP servers panel). The server
|
|
41
41
|
speaks stdio, so `npx -y getregdata-mcp` with `APIFY_TOKEN` in `env` is all you need.
|
|
42
42
|
|
|
43
|
+
### Hosted clients - claude.ai web, ChatGPT developer mode, Gemini (no install)
|
|
44
|
+
|
|
45
|
+
This npm server is stdio-only. For hosted agents that need a remote HTTPS endpoint,
|
|
46
|
+
connect **Apify's hosted MCP server** with OAuth instead - the regdata actors are
|
|
47
|
+
first-class tools there:
|
|
48
|
+
|
|
49
|
+
```
|
|
50
|
+
https://mcp.apify.com/?actors=regdata/crbr-beneficial-owners-scraper,regdata/krz-debtor-scraper,regdata/germany-handelsregister-scraper,regdata/poland-krs-financial-scraper,regdata/adverse-media-screener
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
Swap in any of the [25+ regdata actors](https://apify.com/regdata), or connect plain
|
|
54
|
+
`https://mcp.apify.com` and let the agent discover them via `search-actors`
|
|
55
|
+
("Poland beneficial owners", "Germany insolvency", ...). OAuth signs you into your
|
|
56
|
+
own Apify account, so billing and the free credit work exactly like the local server.
|
|
57
|
+
|
|
43
58
|
## Usage
|
|
44
59
|
|
|
45
60
|
Once connected, just ask your agent in natural language:
|
|
@@ -68,7 +83,7 @@ your token, the Apify platform, and the official registry source.
|
|
|
68
83
|
|
|
69
84
|
```bash
|
|
70
85
|
npm install
|
|
71
|
-
npm run smoke # verify
|
|
86
|
+
npm run smoke # verify all tools load with real input schemas
|
|
72
87
|
APIFY_TOKEN=xxx npm start
|
|
73
88
|
```
|
|
74
89
|
|