Amanat MCP server
Storm risk, route risk and reanalysis backtests for any point on earth. No key, no wallet.
0 stars55 downloads/wk
Reviews
Write oneNobody has reviewed Amanat yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Amanat tools (4)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
backtestWould the 0.75 trigger have fired at this place over this date range? Read from the
route_riskStorm risk along a route, each leg read at the hour a vehicle travelling at `speed`
storm_riskStorm risk for a place or coordinate, 0 to 1, with the reading behind it: wind, gusts,
telegraph_onchain_jobableWhich Telegraph intents an ERC-8183 on-chain job cannot survive, and which miners on each
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Amanat compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 55
- more than 46% of 12,191 servers with a package
What its tools let an agent do: 4 read
Install Amanat in Claude Code, Cursor or VS Code
Runs npx -y amanat-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add amanat -- npx -y amanat-mcp
What the publisher says
From the Amanat repository's README, as published. We do not edit it. Read it on GitHub
Amanat
Signed weather intelligence that a contract acts on by itself.
Signed, not "verified": the network's own verified: true cannot be checked from outside (bug report), so every answer here carries an Ed25519 signature over the fields a contract settles on, and anyone can check it with Node and nothing else:
node -e 'const c=require("node:crypto");fetch("https://amanat-miner.vercel.app/forecast?lat=10.32&lon=123.89&hours=6").then(r=>r.json()).then(({attestation:a})=>console.log(c.verify(null,Buffer.from(a.canonical),c.createPublicKey({key:Buffer.from(a.public_key,"base64"),format:"der",type:"spki"}),Buffer.from(a.signature,"base64"))))'The key it checks against is the one published at /.well-known/amanat.json.
An amanat is a message entrusted to be carried — and, in the language of the old telegraph offices, the dispatch itself. That is the whole shape of this project: a miner sends the amanat, a scoring module tests it, and a contract carries it out without anyone deciding anything by hand.
Built for Telegraph Hackathon Season I. One codebase, three entries:
Live: amanat-miner.vercel.app — read a storm risk for any point, no wallet, no sign-up. It is the same call the contract makes before it spends anything.
In one line, from any MCP client: npx -y amanat-mcp — published to npm and listed in the official MCP registry as io.github.PugarHuda/amanat.
In three minutes: the deck · the film (84 s, cut from live sessions — no mockups) · /api/jobable, which measures how many intents are closed to on-chain jobs, how many are open, and how many cannot be audited at all because their leader publishes its registration at 127.0.0.1. Add ?intent=STORM_ALERT for a verdict on your own.
The three problems this is built around
Everything here comes from measuring the live network rather than guessing at it. The numbers below are reproducible with the scripts in this repo.
1. Deterministic intents are scored as if they were prose. In epoch 240 the rank-1 miner on WEATHERCHECK scored 0.0206 and on STORMALERT 0.0067. The miners are not bad; every scoring module on the network compares text, and those miners answer with numbers. A leaderboard built from those scores is noise — and routing follows the leaderboard.
2. The on-chain rail is real but unused. The Diamond answers getJobBasePrice() with 1000000 and, on 21 August, carried 139 miner registrations against 6 ERC-8183 jobs in its entire lifetime — the last two by a single participant, on 17 August. In a 77-hour window there were 44 MinerRegistered events and 2 JobCreated. Meanwhile the organisers name on-chain intelligence pipelines as the highest-value thing to build.
Read again on 31 August: 341 miner registrations, and still only 14 jobs. Eight of the fourteen are ours. Five settled; the last three have not moved.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Amanat: common questions
- Is Amanat MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Amanat safety report
- How do I install Amanat?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Amanat need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Amanat maintained?
- The last commit was 19 days ago (2026-10-16). The latest release is v0.1.3.
- How does Amanat compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.