# io.github.PugarHuda/amanat (npm · amanat-mcp)

Storm risk, route risk and reanalysis backtests for any point on earth. No key, no wallet.

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

## Components

- npm · `amanat-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pugarhuda-amanat/amanat-mcp.md), [page](https://verifymcp.io/servers/pugarhuda-amanat/amanat-mcp)

## Channel facts

- Registry: `npm`
- Package: `amanat-mcp`
- Version: `0.1.3`
- 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-09-21.

- **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**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 533 tokens (~133/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 io.github.PugarHuda/amanat MCP server?

io.github.PugarHuda/amanat runs locally as an npm package, launched with npx -y amanat-mcp. 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 pugarhuda-amanat -- npx -y amanat-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "pugarhuda-amanat": {
      "command": "npx",
      "args": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pugarhuda-amanat": {
      "command": "npx",
      "args": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pugarhuda-amanat -- npx -y amanat-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pugarhuda-amanat --command npx --arg -y --arg amanat-mcp
```

### Hermes

```yaml
mcp_servers:
  pugarhuda-amanat:
    command: "npx"
    args: ["-y", "amanat-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pugarhuda-amanat": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pugarhuda-amanat -t stdio -c npx -a -y amanat-mcp
```

### Other

```json
{
  "mcpServers": {
    "pugarhuda-amanat": {
      "command": "npx",
      "args": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
```

## 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-09-21 (score 81, +1)

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

### 2026-09-19 (score 80, +1)

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

### 2026-09-17 (score 79, +1)

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

### 2026-09-15 (score 78, +1)

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

### 2026-09-13 (score 77, +1)

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

### 2026-09-11 (score 76, +1)

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

### 2026-09-08 (score 75, +1)

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

### 2026-09-07 (score 74, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (4)

### `storm_risk` (~138 tokens)

Storm risk for a place or coordinate, 0 to 1, with the reading behind it: wind, gusts, precipitation, sea state, the nearest named cyclone, and a band across 51 ECMWF ensemble members. 0.75 is the line a parametric cover pays on. Accepts a place name, a whole question naming one, or "lat,lon".

Input parameters:

- `hours` (integer): Hours ahead, 0 to 168. Omit to read it from the question, or 0 for now.
- `place` (string, required): A place name, a question naming one, or "lat,lon".

### `route_risk` (~108 tokens)

Storm risk along a route, each leg read at the hour a vehicle travelling at `speed` actually reaches it — not one reading for the whole voyage. Returns the worst leg and whether it crosses the 0.75 trigger.

Input parameters:

- `from` (string, required): Origin place name.
- `legs` (integer): Waypoints. Default 3.
- `speed` (number): Speed in km/h. Default 37, about 20 knots.
- `to` (string, required): Destination place name.

### `backtest` (~127 tokens)

Would the 0.75 trigger have fired at this place over this date range? Read from the ERA5 reanalysis archive, so it is what actually happened rather than a forecast. Typhoon Rai at Cebu, 2021-12-15 to 2021-12-18, reads 1.000.

Input parameters:

- `end` (string, required): ISO date, e.g. 2021-12-18.
- `place` (string, required): Place name or "lat,lon".
- `start` (string, required): ISO date, e.g. 2021-12-15.

### `telegraph_onchain_jobable` (~160 tokens)

Which Telegraph intents an ERC-8183 on-chain job cannot survive, and which miners on each one can actually receive a job. A job is routed by rank and nothing in that path checks whether the miner it lands on declares an `on_chain.request` mapping — so on most intents the job is answered from that miner's first endpoint with no parameters. Read this before putting a contract on the on-chain rail. Pass `intent` for a verdict on one intent alone: can_receive_a_job is true, false, or null where the leader's registration cannot be fetched from outside the node — null is never a no.

Input parameters:

- `intent` (string): One intent, e.g. STORM_ALERT. Omit for the whole audit.

## Diagnostics

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

## Score history

- 2026-09-21: 81
- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 78
- 2026-09-15: 78
- 2026-09-14: 77
- 2026-09-13: 77
- 2026-09-12: 76
- 2026-09-11: 76
- 2026-09-10: 75
- 2026-09-09: 75
- 2026-09-08: 75
- 2026-09-07: 74
- 2026-09-06: 59
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 71

## Common questions

### What is the io.github.PugarHuda/amanat MCP server?

io.github.PugarHuda/amanat is an MCP server listed in the public MCP registry as io.github.PugarHuda/amanat. Storm risk, route risk and reanalysis backtests for any point on earth. No key, no wallet. This page covers its npm package (amanat-mcp).

### Is the io.github.PugarHuda/amanat MCP server safe to use?

io.github.PugarHuda/amanat scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.PugarHuda/amanat MCP server expose?

io.github.PugarHuda/amanat exposes 4 tools: storm_risk, route_risk, backtest, telegraph_onchain_jobable. Their descriptions and schemas cost roughly 533 tokens of context every time the server is loaded.

### Is the io.github.PugarHuda/amanat MCP server still maintained?

io.github.PugarHuda/amanat is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.PugarHuda/amanat MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/amanat-mcp
- Socket report: https://socket.dev/npm/package/amanat-mcp
- Repository: https://github.com/PugarHuda/amanat
- Website: https://amanat-miner.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/pugarhuda-amanat/amanat-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pugarhuda-amanat/amanat-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pugarhuda-amanat/amanat-mcp