402lounge
REMOTE · MCP.402LOUNGE.COM
Receipts, invoices and a payTo register for AI agents that pay with x402 (USDC on Base).
Available components
Last scanned (22 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (lounge.wallet.remove). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 10924 tokens (~185/item across 59 items; 59 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.5.0 → 0.5.1 functional
- Server version: 0.4.0 → 0.5.0 functional
- New tool “receipts.refunds” functional
- New tool “receipts.set_supply” functional
- “receipts.record” added an optional parameter “supply” cosmetic
- “company.update” reworded the description of “own_accounts” cosmetic
- 6 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.402lounge.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=402lounge.com | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4915e35a0a883c4f0eeaef764942fcf3 |
| SANs: 402lounge.com, mcp.402lounge.com, *.mcp.402lounge.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.402lounge.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| 402lounge.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.402lounge.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.402lounge.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
register.lookup Who is behind this wallet? ~62
Wallet in, seller out: the listing that owns a payTo address, its verification level, its paid endpoints and the last health check. Free, no account. Call it before you pay someone new.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | A payTo address on Base |
No output schema declared.
No examples provided.
seller.check The company check of a listing (level 2) ~346
Level 2 for a listing of your company on level 1: action start {listing} opens the check and returns its steps. The domain of the listing is proved by an email address at it: email {id, email} sends a code there, confirm_email {id, code} confirms it. Without a mailbox, add the DNS TXT record from the check instead (_402lounge.<host>, value 402lounge-verify=<token>). verify {id} runs the steps again (company data with the name of the person who acts for the company, VIES, the domain, EU sanctions list, payment). Once all pass, 402lounge approves it, then the listing is on level 2 for a year. checkout {id} gives the Polar link for 10 € a year, included in Books. get {id}, withdraw {id}.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | start, get, verify, email, confirm_email, checkout or withdraw, as the description explains |
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| code | string | – | confirm_email: the six-digit code from the mail |
| string | – | email: an address at the domain of the listing | |
| id | string | – | The check, from start. Every action but start needs it |
| listing | string | – | The listing slug, e.g. glassnode |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| session_token | string | – | A lounge session token (lg_...) if you have one |
No output schema declared.
No examples provided.
seller.get Your seller levels ~138
Your company as a seller: every listing with its level (0 listed, 1 wallet verified, 2 company verified, 3 invoicing), the company check and its steps, the seller profile (register entry, representative), the invoicing mandate and self-billing, and what is missing for the next level.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| session_token | string | – | A lounge session token (lg_...) if you have one |
No output schema declared.
No examples provided.
seller.invoices Documents in your name ~196
Invoices 402lounge issued in your name (L-2610-10427-01), credit notes your buyers issued to you (G-...) and their cancellations, newest first, each with its e-invoice. With id the whole document. PDF and XML: GET /v1/seller/invoices/{id}/pdf and /xml.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| id | string | – | Optional: one document in full, by id or number |
| limit | integer | – | How many documents, 1 to 200 |
| month | string | – | Optional: only this month, YYYY-MM |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| session_token | string | – | A lounge session token (lg_...) if you have one |
No output schema declared.
No examples provided.
seller.invoices.cancel Cancel a document in your name ~167
Admin agents, the owner and finance. Cancels an invoice in your name or a credit note you received, with a reason: a cancellation in your number range follows, the original stays. The payments are open again and the next monthly run issues them anew.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| id | string | yes | The invoice or credit note, by id or number |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| reason | string | yes | Why, 3 to 500 characters. It is written on the cancellation |
| session_token | string | – | A lounge session token (lg_...) if you have one |
No output schema declared.
No examples provided.
seller.mandate Invoicing mandate (level 3) ~257
Admin agents and owners. get shows the mandate text (link, version, sha256) and whether it is signed. sign: first call returns a challenge, sign it with your wallet and call again with agreement_proof {message, signature}. Then, with a listing on level 2 and Books, buyers on level 3 get monthly invoices in your name (§ 14 (2) UStG), issued by 402lounge. revoke ends it at the end of the month.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | get shows the text and whether it is signed, sign signs it (a challenge first), revoke ends it at the end of the month |
| agreement_proof | object | – | sign, second call: the challenge message the first call returned, and your wallet's signature over it |
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| confirm | boolean | – | sign: true, after you read the mandate text from get |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| session_token | string | – | A lounge session token (lg_...) if you have one |
No output schema declared.
No examples provided.
seller.prices State the prices of a listing ~204
Admin agents and owners. What your listing costs, in your words: up to 12 lines, each a label, a price in USDC and whether it is per call or the minimum top-up of a balance. All lines at once, they replace the ones before. The listing page shows them instead of what the nightly check read from your 402 answers. An empty list removes them. Nobody checks them, so state what a buyer really pays.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| listing | string | yes | The listing slug, e.g. glassnode |
| prices | array | yes | Every line of the listing, in the order to show. [] removes them |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| session_token | string | – | A lounge session token (lg_...) if you have one |
No output schema declared.
No examples provided.
seller.profile Representative and register entry ~316
Admin agents and owners. What level 2 needs on top of the company data: the name of the person who acts for the company (representative_name, the role is optional). The commercial register court and number help the check but are optional, no_register: true where there is none. sole_proprietor: true when the company is one person, then show_name says whether the register may show the name.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| no_register | boolean | – | true when the company is in no commercial register |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| register_court | – | – | The court or office that keeps the register, where the country names one: Registergericht in Germany, Firmenbuchgericht in Austria. GET /v1/countries names it per country |
| register_number | – | – | The number in the register, as the register writes it (GET /v1/countries names the register per country) |
| representative_name | – | – | The name of the person who acts for the company. null clears it |
| representative_role | – | – | e.g. Managing director |
| session_token | string | – | A lounge session token (lg_...) if you have one |
| show_name | boolean | – | With sole_proprietor: whether the register may show the name |
| sole_proprietor | boolean | – | true when the company is one person |
No output schema declared.
No examples provided.
seller.self_billing Self-billing agreement ~218
Admin agents and owners. Without a mandate, a company on level 2 can agree that its buyers on level 3 issue credit notes (Gutschriften) for what they paid, on any plan. get, sign (challenge, then agreement_proof), revoke (at the end of the month).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | get shows the agreement and whether it is signed, sign signs it (a challenge first), revoke ends it at the end of the month |
| agreement_proof | object | – | sign, second call: the challenge message the first call returned, and your wallet's signature over it |
| client | string | – | Your client name, e.g. "claude-code 2.1" |
| confirm | boolean | – | sign: true, after you read the agreement from get |
| proof | object | – | An EIP-4361 message you got from a challenge, signed by your wallet |
| session_token | string | – | A lounge session token (lg_...) if you have one |
No output schema declared.
No examples provided.
How do I install the 402lounge MCP server?
402lounge is a hosted endpoint at https://mcp.402lounge.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.402lounge.com
claude mcp add --transport http com-402lounge-mcp 'https://mcp.402lounge.com/mcp'
What is the 402lounge MCP server?
402lounge is an MCP server listed in the public MCP registry as com.402lounge/mcp. Receipts, invoices and a payTo register for AI agents that pay with x402 (USDC on Base). This page covers its hosted endpoint (https://mcp.402lounge.com/mcp).
Is the 402lounge MCP server safe to use?
402lounge scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the 402lounge MCP server expose?
402lounge exposes 59 tools: lounge.requirements, lounge.terms, lounge.signup, lounge.me, lounge.agent.update, and 54 more. Their descriptions and schemas cost roughly 10,729 tokens of context every time the server is loaded.
Does the 402lounge MCP server require authentication?
No. We connected to 402lounge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 402lounge MCP server still maintained?
402lounge is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the 402lounge MCP server?
VerifyMCP ran 12 checks on 402lounge, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about 402lounge: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.