io.github.DIALLOUBE-RESEARCH/hypernatt-terminal

MCPcommunitydegraded
v2.8.0io.github.DIALLOUBE-RESEARCHUnknownUpdated 20d agoGitHub

Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments.

Endpoint healthdegraded
checked 9 days ago · last reachable 9 days ago · 1032ms · 2 endpoints
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http, sse). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
20d agoLast update
Package
Authorio.github.DIALLOUBE-RESEARCH
LicenseUnknown
Version2.8.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface8 tools · 1 privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · 1 privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

swap_via_nattswapNo description published

This tool published no description. Forge does not invent one.

swap_quoteNo description published

This tool published no description. Forge does not invent one.

get_vault_proofNo description published

This tool published no description. Forge does not invent one.

get_agent_manifestNo description published

This tool published no description. Forge does not invent one.

get_btc_usdc_signalNo description published

This tool published no description. Forge does not invent one.

get_mm_hunt_scoreNo description published

This tool published no description. Forge does not invent one.

get_similarity_matchNo description published

This tool published no description. Forge does not invent one.

hypernatt-terminalprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.