# Emsc (npm · @pipeworx/mcp-emsc)

EMSC (European-Mediterranean Seismological Centre) MCP — wraps the seismicportal.eu FDSN event web…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-emsc/emsc-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-emsc/emsc-mcp)
- npm · `@pipeworx/mcp-emsc`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-emsc/pipeworx-mcp-emsc.md), [page](https://verifymcp.io/servers/pipeworx-io-emsc/pipeworx-mcp-emsc)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-emsc`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-emsc).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 667 tokens (~333/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Emsc MCP server?

Emsc runs locally as an npm package, launched with npx -y @pipeworx/mcp-emsc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-emsc -- npx -y @pipeworx/mcp-emsc
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-emsc": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-emsc"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-emsc": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-emsc"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-emsc -- npx -y @pipeworx/mcp-emsc
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-emsc": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-emsc"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-emsc --command npx --arg -y --arg @pipeworx/mcp-emsc
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-emsc:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-emsc"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-emsc": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-emsc"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-emsc -t stdio -c npx -a -y @pipeworx/mcp-emsc
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-emsc": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-emsc"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-01 (score 64, −14)

- [security regression] Tool safety: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `search_earthquakes` (~465 tokens)

Search seismic events from EMSC (European-Mediterranean Seismological Centre) via the FDSN-standard seismicportal.eu API. Global coverage with especially strong Europe/Mediterranean reporting — complements USGS. Filter by UTC time range, magnitude, and location (either a bounding box OR a center point + radius in degrees). Times are UTC ISO 8601, depth in km, and place names come from the Flynn-Engdahl region. Example: search_earthquakes({ start: "2026-01-01", end: "2026-02-01", minmag: 5.0, orderby: "magnitude" }) or search_earthquakes({ lat: 38.0, lon: 23.7, maxradius: 5, minmag: 3 }).

Input parameters:

- `end` (string): End of UTC time window, ISO 8601.
- `lat` (number): Center latitude for circular search (use with lon + maxradius).
- `limit` (number): Maximum number of results, 1-1000 (default: 50).
- `lon` (number): Center longitude for circular search (use with lat + maxradius).
- `maxlat` (number): Bounding box northern latitude, -90 to 90 (optional).
- `maxlon` (number): Bounding box eastern longitude, -180 to 180 (optional).
- `maxmag` (number): Maximum magnitude (optional).
- `maxradius` (number): Maximum radius in degrees from center lat/lon (optional).
- `minlat` (number): Bounding box southern latitude, -90 to 90 (optional).
- `minlon` (number): Bounding box western longitude, -180 to 180 (optional).
- `minmag` (number): Minimum magnitude (optional).
- `minradius` (number): Minimum radius in degrees from center lat/lon (optional).
- `orderby` (string): Result ordering (default: "time", i.e. newest first).
- `start` (string): Start of UTC time window, ISO 8601 (e.g. "2026-01-01" or "2026-01-01T00:00:00").

### `recent_earthquakes` (~150 tokens)

Get recent earthquakes from EMSC (European-Mediterranean Seismological Centre): the last N days above a minimum magnitude, newest first. Convenience wrapper over the FDSN event API. Global coverage, strong in Europe/Mediterranean. Times are UTC ISO 8601, depth in km. Example: recent_earthquakes({ days: 7, minmag: 4 }).

Input parameters:

- `days` (number): How many days back to look (default: 7).
- `limit` (number): Maximum number of results, 1-1000 (default: 50).
- `minmag` (number): Minimum magnitude to include (default: 4).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-emsc/pipeworx-mcp-emsc#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 64
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Emsc MCP server?

Emsc is an MCP server listed in the public MCP registry as io.github.pipeworx-io/emsc. EMSC (European-Mediterranean Seismological Centre) MCP, wraps the seismicportal.eu FDSN event web… This page covers its npm package (@pipeworx/mcp-emsc).

### Is the Emsc MCP server safe to use?

Emsc scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Emsc MCP server expose?

Emsc exposes 2 tools: search_earthquakes, recent_earthquakes. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Is the Emsc MCP server still maintained?

Emsc is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Emsc MCP server under?

Emsc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Emsc MCP server?

VerifyMCP ran 16 checks on Emsc, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-emsc
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-emsc
- Repository: https://github.com/pipeworx-io/mcp-emsc
- Website: https://pipeworx.io/packs/emsc
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-emsc/pipeworx-mcp-emsc.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-emsc/pipeworx-mcp-emsc/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-emsc/pipeworx-mcp-emsc.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-emsc/pipeworx-mcp-emsc