Build into the tools people already use.
Remote MCP uses a bare endpoint and bearer or OAuth app authentication. Credentials stay out of URLs; personal data still needs a separate consent decision.
FOR BUILDERS
Make your agent
ask better.
Hussh gives external agents a consent-first route to relevant information: discover what is available, ask for one narrow scope in plain language, wait for the person, then receive an encrypted export only after approval.
01DiscoverSearch the person’s live scope catalog. Never hard-code a broad profile request.
02RequestState one returned scope and a human-readable purpose.
03ApproveThe person decides in Hussh—not in a hidden agent workflow.
04ConfirmCheck the request state. A pending request is not access.
05RetrieveUse the approved grant to receive the encrypted, bounded export.
Connect systems deliberately.
An approved export does not authorize a CRM mutation. Read, create, and update require a signed-in owner, typed intent, confirmation, binding, idempotency, and readback. Delete is blocked in v1.
Developer workspacehushh.ai/developers
Open-source researchgithub.com/hushh-labs/hushh-research
Developer communityhushh.ai/discordSearch user scopes · request consent · check consent status · get encrypted scoped export. A compatibility context tool exists, but it is not the normal path.
Bearer or PKCE lets a developer app connect. It never gives that app automatic access to someone’s personal information.
No query-token URLs. No plaintext fallback. Connector private keys and ciphertext do not belong in a prompt, log, or tool description.