Privi Network
Related Servers
Alternatives to Privi Network
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenancealalanet-agent is the open local client of alalanet.com, the free service an AI agent asks before it installs, connects or pays. A stdio MCP server whose key stays on your machine: it signs agent passports, receipts, skill and package releases, mail and memory locally (16 tools) and checks files and agents against alalanet's public transparency log. Hosted checks: https://alalanet.com/mcp.216Apache 2.0
- 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
- AlicenseAqualityDmaintenancesecurity tools for AI agents: URL safety scanning, prompt injection detection (200+ patterns), email/password breach checks via HIBP, domain & IP reputation analysis, and AI skill supply chain scanning. Free tier (3 calls/day) or pay-per-request with USDC micropayments via x402.932 npm1MIT
- AlicenseNot gradedqualityCmaintenanceBudget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to operate through a local, signed boundary that blocks prompt injection and secret leakage, verifies outputs, preserves cross-session memory, and provides offline-verifiable receipts. It also exposes 900+ MCP tools for discoverable agent actions.7MIT
- AlicenseAqualityCmaintenancePolicy-gated MCP execution for AI agents—ShadeGuard, x402, signed receipts, no custody. 16 tools, 18 chains.182MIT
TDQS
Scored across 2 tools
Both tools are purely informational surfaces about the Privi network, so an agent may hesitate over which to call when asked a general 'what is Privi' question. The descriptions do differentiate them (endpoint discovery vs. pricing/limitations), but the boundary is narrow and partly overlapping since pricing is arguably part of the service directory.
Both tools use a consistent privi_network_<noun_phrase> pattern with snake_case throughout, so the set is predictable. The deviation is minor: neither uses a verb, so the names describe resources rather than actions, which is acceptable but slightly less informative.
Two tools is thin even for a deliberately read-only informational server; the scope could reasonably justify a small handful more (e.g. per-service detail or status lookups). It is not a mismatch, but it sits at the borderline of under-scoped.
For the stated informational-only purpose, the surface covers discovery and pricing, which are the two most obvious needs. However, there is no tool to retrieve details for a single endpoint, check live availability/health, or fetch machine-readable pricing per service, leaving agents with dead ends beyond the two summary calls.