br.com.salvy/mcp
Salvy
Is the Salvy MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Consulte e gerencie linhas, faturas e colaboradores da Salvy pelo seu agente de IA.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"code":"unauthorized","message":"Usuário não autorizado","publicDetails":{"friendlyMessage":"Usuário não auto- Endpoint
- https://mcp.salvy.com.br/mcp (streamable-http)
- Host
- mcp.salvy.com.br
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.salvy.com.br/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server clerk.salvy.com.br, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes profile email offline_access.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/SalvyLTD/salvy-mcp
- Website
- https://docs.salvy.com.br/mcp-guide
- Registry
- active, updated 2026-10-23 · registry entry
Compare this server with others.
More servers
Servers that mention colaboradores or consulte.
- UPí — upCampo br.com.upcampo/upi · needs auth
- CDF Finance MCP io.github.VessellTech/cdf.mcp · needs auth
- Sudrel br.com.sudrel/sudrel · needs auth
- io.github.SamuelMoraesF/mcp-banco-inter · needs env
- io.github.SamuelMoraesF/mcp-organizze · alive
- Calepio fr.calepio/calepio · needs auth
- ERPPro br.com.erppro/erp · needs auth
- io.github.CloudCorpRecords/chatdata · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.