neus_context, catalog, hosted verification links, and other flows that do not require your NEUS account or billable usage on your balance.
First call: use neus_context (public) so assistants ground answers in the current verifier list and billing model before deeper tools.
Add Authorization: Bearer with your personal access key from Access keys when you need account-scoped tools—for example neus_me, private proof reads, or checks that debit your credits. Same token you send to api.neus.network (SDK Authentication). Call neus_me after connecting to confirm the session.
If you connect using only the MCP URL, tools can still return https://neus.network/verify links for browser completion. That browser step uses NEUS hosted sign-in (passkey or wallet). It does not automatically attach your personal access key to your IDE MCP connection.
Backend or automation: if a server already calls api.neus.network with Authorization: Bearer, you may send the same personal access key on the MCP HTTP transport from that trusted environment only. Never expose that value to browsers or mobile clients.
Privacy: neus_proofs_check is yes/no only. Private proofs follow the same rules as the API when the user is signed in (Proof context).
Related
Overview
Default flow.
Setup
Connect.
Hosted Verify
User UX.