Home / MCP registry index / io.usefulapi/reviso

Reviso MCP by usefulapi

io.usefulapi/reviso in the official MCP registry. Endpoint https://reviso.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read customers, invoices and ledger entries; create customers and draft invoices in Reviso.

We read its 23 tools on 2026-11-11. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http reviso https://reviso.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "reviso": {
      "url": "https://reviso.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"reviso","type":"http","url":"https://reviso.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

reviso_get_company reviso_list_customers reviso_get_customer reviso_list_suppliers reviso_get_supplier reviso_list_products reviso_get_product reviso_list_invoices reviso_get_invoice reviso_list_orders reviso_get_order reviso_list_quotations reviso_get_quotation reviso_list_accounts reviso_list_accounting_years reviso_list_account_totals reviso_list_entries reviso_list_projects reviso_list_reference reviso_create_customer reviso_create_supplier reviso_create_product reviso_create_draft_invoice

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-11): 580010e99296a3c4. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-reviso/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-reviso)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.