Skills nansen-mpp-payment

📦

nansen-mpp-payment

Name: nansen-mpp-payment
Author: internet-court

Content revision r1 Critical ⚙️ External commands🌐 Network access📁 Filesystem access

Run Nansen API Calls Through Tempo MPP

Paid Nansen API access can require API keys or wallet setup. This skill shows how to use Tempo MPP for pay-per-call requests.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Do not auto-install this skill.

The canonical policy requires operator review before any installation action.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "nansen-mpp-payment" from https://skillstore.io/skills/internet-court-nansen-mpp-payment.md and its manifest at https://skillstore.io/api/skills/internet-court-nansen-mpp-payment/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/internet-court-nansen-mpp-payment.md Signed manifest GET /api/skills/internet-court-nansen-mpp-payment/manifest Signed lockfile GET /api/skills/internet-court-nansen-mpp-payment/lockfile

Test it

Using "nansen-mpp-payment". I need to call a paid Nansen endpoint without an API key.

Expected outcome:

Use Tempo MPP only if the endpoint supports payment credentials.
Confirm wallet login and funding before any paid request.
Treat each request as billable and require explicit approval.

Using "nansen-mpp-payment". Compare MPP with x402 for my Nansen workflow.

Expected outcome:

MPP uses Tempo-managed payment credentials. x402 uses the Nansen CLI wallet flow. Choose based on wallet ownership and approval requirements.

Using "nansen-mpp-payment". Can I discover which paid endpoints are available?

Expected outcome:

Yes. Start with public endpoint metadata, then verify the target endpoint and payment rail before sending paid requests.

Security Audit

Critical

v2 • 7/21/2026 Open versioned report

Most external-command detections are false positives caused by Markdown inline-code markers and fenced examples. The skill does instruct users to download and execute a remote Tempo installer through a curl-to-bash pipeline, which is a critical supply-chain execution risk. Direct requests to Nansen endpoints are intentional but make network calls and may incur payment charges through the Tempo wallet.

Files scanned

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

Critical

SKILL.md:34

Pipe to shell pattern

curl -fsSL https://tempo.xyz/install | bash

The setup command downloads content from a remote URL and executes it immediately with Bash. A compromised or changed installer endpoint could run arbitrary code on the user system.

Low

SKILL.md:40

System reconnaissance

tempo wallet whoami

The command queries the local Tempo CLI for wallet identity and readiness. It is limited to the documented wallet context but can reveal account information in the terminal.

Capability review items (4)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low

SKILL.md:34

Hardcoded URL

curl -fsSL https://tempo.xyz/install | bash

The command fetches executable installer content from tempo.xyz. Its impact is captured more directly by the pipe-to-shell finding, but it is a real network dependency.

Low

SKILL.md:49

Hardcoded URL

tempo request POST https://api.nansen.ai/api/v1/smart-money/netflow \

This documented tempo request sends a paid API request to api.nansen.ai. It is intentional, but it contacts an external service and can spend wallet funds.

Low

SKILL.md:53

Hardcoded URL

tempo request POST https://api.nansen.ai/api/v1/tgm/holders \

This documented tempo request sends a paid API request to api.nansen.ai. It is intentional, but it contacts an external service and can spend wallet funds.

Low

SKILL.md:62

Hardcoded URL

curl https://api.nansen.ai/.well-known/x402

The curl command contacts the Nansen well-known endpoint to discover payment capabilities. This is an intentional external network request.

Risk Factors

⚙️ External commands (21)

🌐 Network access (10)

SKILL.md:12 SKILL.md:18 SKILL.md:34 SKILL.md:49 SKILL.md:53 SKILL.md:62 SKILL.md:86 SKILL.md:87 SKILL.md:88 SKILL.md:89

📁 Filesystem access (1)

SKILL.md:62

Detected Patterns

Pipe to shell patternSystem reconnaissance

Audited by: claude View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/internet-court-nansen-mpp-payment/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/internet-court-nansen-mpp-payment/security.svg)](https://skillstore.io/skills/internet-court-nansen-mpp-payment?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/internet-court-nansen-mpp-payment?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-nansen-mpp-payment/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-nansen-mpp-payment.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

internet-court. (2026). nansen-mpp-payment security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/internet-court-nansen-mpp-payment/audits/2

BibTeX citation

@techreport{internet-court-internet-court-nansen-mpp-payment-2026,
  author = {internet-court},
  title = {nansen-mpp-payment security audit report (audit version 2)},
  institution = {Skillstore},
  year = {2026},
  number = {2},
  url = {https://skillstore.io/skills/internet-court-nansen-mpp-payment/audits/2},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nansen-mpp-payment security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
  - name: "internet-court"
date-released: "2026-07-21"
url: "https://skillstore.io/skills/internet-court-nansen-mpp-payment/audits/2"
identifiers:
  - type: other
    value: "skillstore:internet-court-nansen-mpp-payment:audit:2"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Access Nansen Without API Keys

Use Tempo MPP when a paid endpoint supports payment credentials and the user wants no long-lived API key.

Test MPP Payment Flows

Compare Nansen API key, x402, and MPP paths before building payment-aware API integrations.

Document Paid Endpoint Discovery

Check Nansen paid resource metadata and explain which payment rails are available for each endpoint.

Try These Prompts

Choose an Access Method

Explain whether Tempo MPP fits my Nansen task. I do not have a Nansen API key and want to avoid local wallet management.

Prepare Tempo Setup

Walk me through preparing Tempo for Nansen MPP access. Include login, funding checks, and approval points before paid requests.

Plan a Paid Request

Help me plan a Nansen MPP request for this endpoint: [endpoint]. Include schema lookup, cost awareness, and required approvals.

Review Payment Integration

Review this Nansen workflow for API key, x402, and Tempo MPP tradeoffs: [workflow]. Identify payment, credential, and operational risks.

Best Practices

Confirm user approval before installing Tempo or running billable requests.
Check endpoint schemas before sending paid requests.
Use read-only discovery steps before wallet funding or paid calls.

Avoid

Do not run remote installer scripts without verifying the source.
Do not send wallet or payment actions without explicit consent.
Do not use this skill when an API key or x402 flow is required.

Frequently Asked Questions

Does this skill install Tempo for me?

No. It documents the setup and expects separate installation with user approval.

Can it call Nansen without an API key?

Yes, when the endpoint supports MPP and the user approves the paid request.

Does it manage wallet keys?

No. Tempo manages the payment flow separately from the Nansen CLI wallet flow.

Are requests free?

No. The documented API calls can be paid requests and should require explicit approval.

Which AI tools can use it?

The report lists support for Claude, Codex, and Claude Code.

Does it replace x402?

No. It covers the MPP payment rail and explains when x402 remains the better choice.

Developer Details

Author

internet-court

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/internet-court/internet-court-skill/tree/main/vendored/nansen/nansen-mpp-payment

Ref

3f6e026a3363e0954ede7bef0cfe88d4475de137

Maintenance freshness

7/21/2026

Usage

1 downloads · 0 views

File structure

📄 SKILL.md