Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.PugarHuda/amanat

NPM · AMANAT-MCP · SCANNED SEP 21

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

Available components

npm · amanat-mcp 81
+4 this week 81 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

npm · amanat-mcp

# add to Claude Code
claude mcp add pugarhuda-amanat -- npx -y amanat-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "pugarhuda-amanat": {
      "command": "npx",
      "args": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pugarhuda-amanat": {
      "command": "npx",
      "args": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add pugarhuda-amanat --command npx --arg -y --arg amanat-mcp
# ~/.hermes/config.yaml
mcp_servers:
  pugarhuda-amanat:
    command: "npx"
    args: ["-y", "amanat-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pugarhuda-amanat": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add pugarhuda-amanat -t stdio -c npx -a -y amanat-mcp
// mcp.json
{
  "mcpServers": {
    "pugarhuda-amanat": {
      "command": "npx",
      "args": [
        "-y",
        "amanat-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +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.

  • 19 Sept 26 +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.

  • 17 Sept 26 +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.

  • 15 Sept 26 +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.

  • 13 Sept 26 +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.

  • 11 Sept 26 +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.

  • 8 Sept 26 +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.

  • 7 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/amanat-mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~533 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
backtest ~127

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.

NameTypeReqDescription
endstringyesISO date, e.g. 2021-12-18.
placestringyesPlace name or "lat,lon".
startstringyesISO date, e.g. 2021-12-15.

No output schema declared.

No examples provided.

route_risk ~108

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.

NameTypeReqDescription
fromstringyesOrigin place name.
legsinteger–Waypoints. Default 3.
speednumber–Speed in km/h. Default 37, about 20 knots.
tostringyesDestination place name.

No output schema declared.

No examples provided.

storm_risk ~138

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".

NameTypeReqDescription
hoursinteger–Hours ahead, 0 to 168. Omit to read it from the question, or 0 for now.
placestringyesA place name, a question naming one, or "lat,lon".

No output schema declared.

No examples provided.

telegraph_onchain_jobable ~160

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.

NameTypeReqDescription
intentstring–One intent, e.g. STORM_ALERT. Omit for the whole audit.

No output schema declared.

No examples provided.

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.