Global Fishing Watch vs Nasa Eonet
A side-by-side look at the Global Fishing Watch and Nasa Eonet MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Global Fishing Watch for environment & nature work as a local process; choose Nasa Eonet for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Global Fishing Watch when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_GFW_FISHING_TOKEN.
Choose Nasa Eonet when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 44/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | PLATFORM_GFW_FISHING_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Global Fishing Watch | View Nasa Eonet |
Tools & capabilities
Global Fishing Watch tools
No tool names declared yet. Check the project README from the listing page.
Nasa Eonet tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Global Fishing Watch
{
"mcpServers": {
"global-fishing-watch": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-global-fishing-watch"
],
"env": {
"PLATFORM_GFW_FISHING_TOKEN": "YOUR_PLATFORM_GFW_FISHING_TOKEN_HERE"
}
}
}
}
Nasa Eonet
{
"mcpServers": {
"nasa-eonet": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nasa-eonet"
]
}
}
}
Frequently asked questions
Global Fishing Watch is categorized under Environment & Nature and uses a local stdio subprocess. Nasa Eonet belongs to Environment & Nature and uses a local stdio subprocess. Pick Global Fishing Watch for environment & nature work and Nasa Eonet for environment & nature.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Global Fishing Watch has no declared pricing — check the project's own site. Nasa Eonet has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add global-fishing-watch and nasa-eonet as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Global Fishing Watch has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Nasa Eonet has 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.