Environmental Esg Mcp
com.thenextgennexusPublished by thenextgennexus.comv1.0.0Updated Oct 26, 2026
⚠️ DEPRECATED — G2's Cloudflare anti-bot defeats free scraping. Not commercially viable without paid
Overview
A deprecated remote Apify-hosted MCP endpoint for environmental and ESG data that its own description says no longer works reliably.
- What you can do
- The registry description gives no tool list; it only states that the server is deprecated.
- According to that description, its intended purpose was scraping environmental/ESG material, but G2's Cloudflare anti-bot protection now defeats free scraping.
- The provider also states it is not commercially viable without paid access.
- No instructions or README are supplied, so the actual tools and outputs cannot be confirmed.
- When to use it
- Probably not worth adding: the provider marks it deprecated and says free scraping no longer works. Consider it only if you specifically need to evaluate or archive this Apify actor, not for production ESG data.
- Requirements
- A remote streamable HTTP endpoint at the provider's Apify actor address. Authentication is required: a bearer token in the Authorization header, described as an Apify API token, obtainable from a free Apify console tier. No local runtime or environment variables are declared.
Installation
In SourceWeft
- Open Environmental Esg Mcp in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.thenextgennexus%2Fenvironmental-esg-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"environmental-esg": {
"type": "http",
"url": "https://nexgendata--environmental-esg-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.