Local MCP capabilities provider for Expo
massa is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Valid Brazilian test data: CPF (Brazilian individual taxpayer registration number), CNPJ (Brazilian company taxpayer registration number), credit card, account number, and more, in CSV, JSON, SQL, or Excel format.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http massa-mcp https://massa.criando.dev/mcp
# 2 — ask your agent for something these tools do
# gerar, gerar_documento, importar_ddl and 2 more
massa costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http massa-mcp https://massa.criando.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Gera massa de teste a partir de um schema JSON do massa e devolve o arquivo como texto (csv, json ou script sql). Até 100 linhas por chamada; acima disso nada é gerado e a resposta traz o schema e um curl para a API (/api/generate), que gera o volume todo. Com formato xlsx (Excel), devolve um link que baixa o arquivo, sem o teto de linhas: mostre o link ao usuário exatamente como veio. Sem seed no
| Parameter | Type | Required | Notes |
|---|---|---|---|
| schema | object | yes | o schema JSON do massa, como objeto |
| formato | string | no | csv (padrão), json, sql ou xlsx (Excel: volta um link para baixar o arquivo, que não entra no contexto) |
| tabela | string | no | nome da tabela dos INSERT, só com formato sql (aceita esquema.tabela; padrão massa) |
| dialeto | string | no | banco do script, só com formato sql: mysql, oracle ou sqlserver. Vazio é SQL padrão (Postgres) |
Gera de 1 a 100 documentos válidos de um tipo: cpf, cnpj, cartao (número, validade e CVV), conta (banco, agência e conta com DV) ou senha. Os dígitos verificadores são calculados, não inventados. Cada tipo aceita só as suas opções (uf no cpf, alfanumerico no cnpj, bandeira no cartao, banco na conta, as regras de tamanho e caracteres na senha); opção que não vale para o tipo é erro. Devolve também
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tipo | string | yes | cpf, cnpj, cartao, conta ou senha |
| quantidade | integer | no | quantos gerar, de 1 a 100 (padrão 1) |
| seed | integer | no | semente do sorteio; omitida, o servidor sorteia uma e a devolve |
| mascara | boolean | no | com pontuação: cpf, cnpj, cartao (espaços) e conta (hífen no DV). Não vale para senha |
| uf | string | no | só cpf: sigla do estado de emissão (define o 9º dígito); vazio sorteia |
| alfanumerico | boolean | no | só cnpj: formato alfanumérico novo (IN RFB 2.229/2024) |
| bandeira | string | no | só cartao: visa, mastercard, elo, amex, hipercard ou diners; vazio sorteia |
| banco | string | no | só conta: código do banco (001, 033, 041, 104, 237, 341); vazio sorteia |
| tamanho_min | integer | no | só senha: tamanho mínimo (padrão 12) |
| tamanho_max | integer | no | só senha: tamanho máximo, até 128 (padrão 16) |
| min_maiusculas | integer | no | só senha: mínimo de maiúsculas; 0 não usa o tipo (padrão 1) |
| min_minusculas | integer | no | só senha: mínimo de minúsculas; 0 não usa o tipo (padrão 1) |
| min_numeros | integer | no | só senha: mínimo de números; 0 não usa o tipo (padrão 1) |
| min_especiais | integer | no | só senha: mínimo de especiais; 0 não usa o tipo (padrão 1) |
| especiais | string | no | só senha: caracteres especiais aceitos (padrão !@#$%&*-_+=?) |
Converte um CREATE TABLE (Postgres, MySQL, Oracle ou SQL Server) num schema do massa: o tipo de cada coluna sai do nome (nr_cpf vira cpf), do CHECK ou do tipo SQL. Devolve o schema, o nome da tabela, o dialeto e avisos de colunas a revisar. Passe o schema a gerar (com tabela e dialeto) para obter os INSERT.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ddl | string | yes | texto do CREATE TABLE (a primeira tabela é importada) |
Lista os tipos de campo que o massa gera (nome, cpf, cnpj, cartao_credito, agencia, data_nascimento, senha…), com grupo, descrição e parâmetros de cada um, e o formato do schema JSON que a ferramenta gerar recebe. Chame antes de montar um schema.
No parameter schema on file.
Confere se um número é válido pela regra oficial: cpf, cnpj (inclusive alfanumérico), cnh, pis, cns, rg (SP), titulo_eleitor, cartao (bandeira, tamanho e Luhn; devolve a bandeira), agencia (precisa do banco) e conta (precisa do banco e da agência). Aceita com ou sem máscara. Não gera nada.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tipo | string | yes | cpf, cnpj, cnh, pis, cns, rg, titulo_eleitor, cartao, agencia ou conta |
| valor | string | yes | o número a conferir, com ou sem máscara |
| banco | string | no | código do banco (001, 033, 041, 104, 237, 341); obrigatório em agencia e conta |
| agencia | string | no | agência da conta; obrigatória em conta |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install massa or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| gerar | external-sink | external-sink: keyword "curl" |
| gerar_documento | no tags | |
| importar_ddl | no tags | |
| listar_tipos | no tags | |
| validar_documento | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish massa can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.