About phantomoperator
PhantomOperator is a paid service for authorized privacy and public-exposure checks, aimed at people and AI agents. Its operations cover web metadata, exposure signals, breach indicators and wallet hygiene, with x402 payments on Base.
Key features
- 01Web metadata and tracker audits
- 02Public-web exposure searches
- 03Email breach checks
- 04Exposure scoring and mitigations
- 05Wallet and Monero privacy audits
- 06Removal guidance and combined reports
Use cases
- 01Audit metadata on an owned website
- 02Check authorized identities for exposure
- 03Review email breach indicators
- 04Assess wallet hygiene and removal options
MCP support
The service provides an MCP endpoint at /mcp. MCP clients can list and call tools using JSON-RPC 2.0; paid-tool handoff includes the HTTP route and payment guidance.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://freysaai.freysa.dev/mcpclaude mcp add --transport http normancomics-phantomoperator https://freysaai.freysa.dev/mcp{"mcpServers":{"normancomics-phantomoperator":{"type":"http","url":"https://freysaai.freysa.dev/mcp"}}}Open in Cursor{"servers":{"normancomics-phantomoperator":{"type":"http","url":"https://freysaai.freysa.dev/mcp"}}}Open in VS Code{"mcpServers":{"normancomics-phantomoperator":{"type":"http","url":"https://freysaai.freysa.dev/mcp"}}}{"mcpServers":{"normancomics-phantomoperator":{"serverUrl":"https://freysaai.freysa.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEPhantomOperator
PhantomOperator is a pay-per-call privacy and public-exposure analysis service for authorized users and AI agents. It provides structured checks for web metadata leakage, public-web exposure, breach indicators, privacy posture, and wallet hygiene.
Authorization required: Only assess URLs, identities, email addresses, wallets, and systems you own or are expressly authorized to assess. Do not submit seed phrases, passwords, API keys, or other secrets.
Live service
Service: https://freysaai.freysa.dev
Source: github.com/normancomics/PhantomOperator
Updates: @phntmop on X
| Resource | URL |
|---|---|
| Human landing page | / |
| Agent quickstart | /quickstart |
| Free illustrative report | /sample-report |
| Free Monero address-decoding preview | POST /demo/monero-decode |
| OpenAPI 3.1 | /openapi.json |
| MCP endpoint | /mcp |
| x402 discovery | /.well-known/x402 |
| A2A agent card | /.well-known/agent-card.json |
| ERC-8004 registration | /.well-known/agent-registration.json |
| LLM guide | /llms.txt |
| Aggregate service telemetry | /usage |
| Service status | /status |
| Terms and scope | /terms |
Payments
Primary rail: Base native USDC via x402
Paid routes at POST /skills/* use x402 v2 exact payments.
| Field | Value |
|---|---|
| Network | Base mainnet, eip155:8453 |
| Asset | Native Base USDC |
| USDC contract | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Payment receiver | 0xC5f20C3Ad7B730B34620ecF39c2C5681482A6Cd6 |
| Production facilitator | Coinbase CDP x402 |
| ERC-8004 agent | 821239 |
| ERC-8004 identity registry | 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 |
An unpaid valid request receives HTTP 402 Payment Required. An x402-compatible client signs the stated payment requirement and retries the same request. Never send a plain ERC-20 transfer as a substitute for the x402 payment credential.
Optional secondary rail: MPP Tempo OUSD
Equivalent routes are available at POST /mpp/skills/* through MPP with Tempo OUSD. This is a separate optional rail; it is not required to use Base USDC x402.
Optional privacy rail: Monero invoices
A production Monero flow is included but is disabled by default. It requires a privately reachable, view-only monero-wallet-rpc, a fixed XMR/USD quote configuration, and a local proof secret. Once configured, a client:
- requests
POST /billing/monero-quotewith{ "skillId": "metadata-audit", "input": { ... } }; - receives a unique wallet subaddress, exact atomic-XMR amount, expiry, and status URL;
- pays the amount, then polls
GET /billing/monero-invoice/:invoiceIduntil required confirmations are reached; - retries the requested skill with
X-Payment-Method: moneroand the returnedX-Paymentproof.
The service uses the view-only wallet RPC only to allocate subaddresses and verify incoming confirmed amounts. It never needs a Monero spend key. Configuration names are documented in .env.example.
Available operations
The canonical schemas, payment requirements, and examples are generated at /openapi.json. Prices are denominated in USDC and may be read from that document before payment.
| Operation | What it does | Base x402 price |
|---|---|---|
metadata-audit | Reviews public HTTP headers, HTML metadata/comments, and third-party trackers for exposure signals. | $0.05 |
threat-scan | Searches public-web results for potential PII exposure associated with an authorized identity. | $0.10 |
breach-check | Checks an email against available breach intelligence and optionally performs a k-anonymity password-range check. | $0.10 |
opsec-score | Produces a structured public-exposure score and prioritized mitigations. | $0.25 |
monero-opsec-audit | Decodes a supplied Monero address and returns privacy-posture guidance. | $0.25 |
data-removal | Identifies supported broker-removal paths and drafts a removal request; it does not submit requests without explicit authorization. | $0.50 |
spam-caller-removal | Prepares official caller-ID unlisting and spam-label dispute steps; it does not submit requests. | $0.10 |
wallet-opsec-audit | Reviews public Base/EVM wallet hygiene signals. | $0.50 |
full-privacy-sweep | Combines relevant authorized checks into one report. | $1.00 |
cypherpunk-redteam-dossier | Combines multiple authorized assessment modules. | $5.00 |
sovereign-opsec-retainer | Produces an organization-level authorized assessment package. | $25.00 |
Agent quickstart
- Fetch
/openapi.json,/.well-known/x402, or/mcp. - Validate that the target and submitted information are authorized and non-sensitive.
- Call the selected
POST /skills/<operation>route with valid JSON. - On
402, inspect the returned x402 requirement and retry using an x402-compatible Base-USDC client. - Validate the returned JSON against the published operation schema.
For MCP clients, send JSON-RPC 2.0 initialize, tools/list, and tools/call requests to POST /mcp. The paid-tool handoff returns the exact HTTP route and payment guidance.
Local development
npm install
cp .env.example .env
npm test
npm start
The server defaults to port 3000. Set PUBLIC_BASE_URL to the deployed HTTPS origin and use a protected .env file. See .env.example for non-secret configuration names. Do not commit credentials, payment keys, private keys, or customer data.
Deployment and discovery
The public service publishes OpenAPI, x402, A2A, ERC-8004, MCP, llms.txt, robots, and sitemap discovery documents. Its current distribution work includes ERC-8004, MPPScan, Global A2A Registry, Agent Tools, 402 Index, Coinbase Bazaar, and a Bankr skills pull request. A directory is only described as listed after acceptance is verifiable; indexes may crawl asynchronously.
Privacy and telemetry
/usage displays aggregate settled-service telemetry. It intentionally excludes request bodies, raw IP addresses, customer wallets, and payment credentials. See TERMS.md for the service scope and limits.
License
MIT.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.