datasinking-mcp vs Reg Monitoring
datasinking-mcp is an MCP server published by heubme2020. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Reg Monitoring is an MCP server published by regmonitoring.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  datasinking-mcp | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.2.18 Downloads/month (npm): 1 142 Downloads/week (npm): 250 Forks (GitHub): 3 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | datasinking-mcp | Reg Monitoring |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 22 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release (differs) | 2026-10-29 | Not published |
| Where it runs (differs) | On your machine (datasinking-mcp) | Remote server (mcp.regmonitoring.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/heubme2020/datasinking | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-11-01 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 22 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
datasinking-mcp
MCP server for DataSinking — full-text financial reports (US, UK, China, Japan, Korea, Taiwan) as clean Markdown, for Claude, Cursor and other AI agents. Earn $7 per purchase per referral (recurring): https://datasink.ing/affiliate
Reg Monitoring
Financial regulatory updates, deadlines and enforcement actions from regulators worldwide.
How to run each
datasinking-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Reg Monitoring As a remote MCP server
claude mcp add --transport http regulatory-updates https://mcp.regmonitoring.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Reg Monitoring has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: datasinking-mcp · What it can do: Reg Monitoring · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.