mcp-identity
@powforge/mcp-identity
MCP server that scores any Nostr pubkey's depth-of-identity before your handler runs. Chaintip-anchored Schnorr cert, L402 priced, drop-in for AI agents that need Sybil resistance on top of paid APIs.
npm: npm i @powforge/mcp-identity
Homepage: https://powforge.dev/explorer
Whitepaper: https://powforge.dev/whitepaper
What It Does
Three MCP tools that wrap the PowForge Depth-of-Identity Oracle:
doi_score_lookup— given a Nostr pubkey (hex or npub), returns multi-dimensional identity score (network, longevity, kinetic-filter cost). L402-priced via the upstream oracle.doi_sign_vouch— builds an unsigned Nostr event for vouching depth-of-identity for another pubkey. Caller signs; oracle counts toward score on observation.doi_score_verify— offline Schnorr verification of a signed DoI cert returned from the oracle. No network.
Related MCP server: AgentStamp
Why Identity-Anchored Pricing
Most paid-API services charge per-request flat. That fails on agent-to-agent surfaces where:
New agents look identical to scrapers — no signal on intent or risk.
Long-tail abusers extract value cheaper than they impose cost.
Whitelist gating doesn't scale to open agent ecosystems.
DoI gives your server a quantitative number for "how much would it cost to fake this caller's identity at this depth" — anchored to a specific Bitcoin chaintip cert that's non-repudiable. Use it as a multiplier on your L402 macaroon price, a rate-limit input, or a routing key.
Quick Start
npm i @powforge/mcp-identityAdd to your MCP config (Claude Desktop, Cursor, etc):
{
"mcpServers": {
"powforge-identity": {
"command": "npx",
"args": ["-y", "@powforge/mcp-identity"]
}
}
}Restart the client. Three new tools appear under powforge-identity.
Why Chaintip-Anchored
The score includes a Schnorr signature over (score, dimensions, score_chaintip_height, score_chaintip_blockhash). That binds the claim to Bitcoin's kinetic filter — recomputable PageRank scores can be silently rewritten, but a chaintip-anchored cert is a fixed claim against a known time. Verification is offline.
The oracle's falsifiable claim window is documented in the whitepaper.
L402 Pricing
The MCP server transparently handles the L402 macaroon dance with oracle.powforge.dev. First call returns a 402 with a Lightning invoice; the wrapper pays from a wallet you configure (env: LNBITS_INVOICE_KEY) and retries. No keys, no accounts.
Status
v0.7.0 published to npm 2026-04-28.
Three tools exposed.
Cert format documented in the whitepaper.
Oracle availability monitored at https://powforge.dev/oracle/freshness.
License
MIT.
Source
Source lives in a private development repo. Issues, questions, and bug reports welcome here.
Available Tools
3 toolsdoi_score_lookupA
Fetch a Depth-of-Identity score for a Nostr pubkey from the PowForge oracle. Returns either an L402 challenge (macaroon + bolt11 invoice + price_sats) for the caller to pay, or a Schnorr-signed score envelope when paid auth is supplied. Pricing is 1-2 sats per call.
Inputs: pubkey (required), auth.
doi_score_verifyA
Locally verify a Schnorr-signed DoI score envelope returned by the PowForge oracle. No network call. Default oracle pubkey is hardcoded; override via oracle_pubkey or the ORACLE_PUBKEY env var.
Inputs: envelope (required), oracle_pubkey.
doi_sign_vouchA
Build an UNSIGNED kind:33335 PowForge vouch event template. The MCP server intentionally never holds keys — the caller signs externally and publishes the signed event to relays.
Inputs: target (required), depth (required), vouch_count (required), sats, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a distinct purpose: fetching a score, verifying a signature, and creating a vouch template. No overlap in functionality.
Tools follow a snake_case pattern with a 'doi_' prefix, but the structure varies slightly: 'doi_score_lookup' and 'doi_score_verify' share a consistent pattern, while 'doi_sign_vouch' uses a different verb-object order.
With three tools, the server provides a focused, minimal set covering the core operations needed for identity scoring on Nostr. The count is well-scoped for its domain.
The tools cover the essential workflow: fetch, verify, and prepare a vouch. Minor gaps include lack of oracle configuration or retrieval of existing vouches, but the core use case is addressed.
Maintenance
Related MCP Connectors
Neutral W3C DID/VC identity and reputation oracle for AI agents (did:key/did:web, eddsa-jcs-2022).
Trust scores and on-chain payment receipts for x402 services.
Statistical adjudication for agents: backtest judges, fact-checks. Pay per call in USDC via x402.
Payment-backed trust scores for AI agents on Base (ERC-8004). $0.01 per check via x402.
Related MCP Servers
- FlicenseAqualityDmaintenance9 tools, Lightning-gated. Pay per call. For agents that need verifiable signed actions with an audit trail. Nostr event signing via daemon Publish events to relays Create Lightning invoices Action receipts — signed proof of agent actions Identity attestation9-
- AlicenseAqualityDmaintenanceTrust intelligence MCP server for AI agents. 19 tools for identity stamps, reputation scoring (0-100), agent registry, forensic audit trails, ERC-8004 bridge, and A2A passports via x402 USDC micropayments.192Apache 2.0
- AlicenseNot gradedqualityDmaintenanceLightning Network trust oracle for AI agents. Provides real-time node reachability checks, trust scores, and personalized pathfinding for 17,000+ Lightning nodes via 12 MCP tools.4 npmAGPL 3.0
- AlicenseNot gradedqualityBmaintenanceTrust-aware Nostr MCP server. 236 tools for identity, social, DMs, trust scoring, AI-to-AI dispatch, Lightning payments, privacy proofs, and encrypted vaults. NIP-46 bunker auth; keys never leave the signing device.1,349 npm1MIT