Skip to content

MCP servers › io.github.guhttps › veu

MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19

veu MCP server

Registry name io.github.guhttps/veu

Véu — the publisher's title

by guhttps · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗

Hides personal data and secrets before text reaches an AI and restores them in the answer. — the publisher's description

8 of 8 record checks metversion 0.8.0PythonMITstandard input/output

Summary

io.github.guhttps/veu is a local MCP server listed in the official MCP registry at version 0.8.0, under the namespace of the GitHub account guhttps. Its linked repository, github.com/guhttps/veu, belongs to the same GitHub account.

Record checks

8 of 8 record checks met · 1 does not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #5,752 of 20,610 packages by monthly downloads, tied with 6 others
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
PyPI · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.8.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-18 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-11-18 to 2026-11-19; 3 in the 90 days before the 2026-11-19 snapshot.
Most recent 3 versions
  • 0.8.0 · 2026-11-19
  • 0.7.2 · 2026-11-19
  • 0.7.1 · 2026-11-18
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.7.1 (published 2026-11-18) → 0.8.0 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher’s GitHub release note for v0.8.0 (“Véu v0.8.0”), published 2026-11-19.

Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
### Adicionado
- **Mais tipos de dados**, em Python e JavaScript:
  - **frases de recuperação de carteiras de criptomoeda** (`CHAVE_PRIVADA`): 12 a 24 palavras da lista oficial do BIP-39, numeradas ou não. Valem pelo checksum (os vetores oficiais são testados) ou com "seed", "carteira", "frase de recuperação" por perto; uma lista de palavras em inglês sem isso fica;
  - **Pix copia e cola** (`CHAVE_PIX`): o código inteiro, que traz a chave, o nome e a cidade de quem recebe, conferido pelo CRC16;
  - **boleto** (`BOLETO`): linha digitável bancária e de arrecadação e código de barras, pelos dígitos verificadores; a linha formatada some mesmo com um dígito errado;
  - **matrícula de certidão** de nascimento, casamento e óbito (`CERTIDAO`, 32 dígitos), pela estrutura do registro civil;
  - **IMEI de celular** (`IMEI`, com Luhn): antes ele era escondido como cartão de crédito;
  - **RNM** (antigo RNE) de estrangeiros, como `RG`; **CVV** do cartão; **coordenadas em graus, minutos e segundos** (`23°33'01"S 46°38'02"W`); **e-mails disfarçados** (`joao [at] gmail [dot] com`, `maria arroba empresa ponto com`);
  - **segredos**: tokens em links (`?token=`, `X-Amz-Signature=`), segredos de 2FA (`otpauth://...secret=`), senha de QR de Wi-Fi (`WIFI:...;P:...;`) e códigos de verificação ("seu código de verificação é 483920").
  O operador sintético gera IMEI, boleto e certidão falsos e válidos no mesmo formato.
- **Extensão em português e inglês:** o nome e a descrição vêm de `extensao/_locales`, então o navegador mostra o nome no idioma de quem usa e as lojas do Edge e do Firefox ganham uma página em cada idioma. Um teste confere que todo idioma cabe nos limites das lojas.
- **Simulação de uso** (`scripts/simular_usuarios.py`): textos de 72 perfis de trabalho (advogada, contador, médica, RH, atendimento por WhatsApp, programador, suporte de TI, imobiliária, Portugal, Argentina, Chile e outros), com dados fictícios, conferindo vazamento, exagero, a volta dos dados e se Python e JavaScript concordam.
- **Registro profissional** (`REGISTRO_PROFISSIONAL`): OAB, CRM, CRO, CREA, CRF, COREN, CRC, CRP e outros conselhos, com o estado ("OAB/SP 123.456", "CRM-SC nº 12345", "CRP 06/123456"). Só o número some; a sigla e o estado ficam, para a IA saber de que profissional se trata. Sem o estado, "CRM 365" continua sendo software.
- **CTPS** (`CTPS`): número e série da carteira de trabalho antiga, com o contexto por perto.
- **Logins nome.sobrenome** ("gislaine.vieira", "/home/joao_silva") viram `PESSOA`, sem pegar domínios (`maria.souza.com.br`), arquivos (`config.yaml`) nem palavras comuns.
- **Endereço MAC** (`MAC`, no grupo Infraestrutura de TI): "95:7F:76:CE:A3:DA", "1c-bb-bd-4a-58-ad" e, com contexto, "aabb.ccdd.eeff". Broadcast e horários ficam.
- **Coordenadas de GPS** (`COORDENADAS`): "-23.550520, -46.633308". Sem contexto, só com cinco casas decimais e sinal negativo; "média 12.3456, 45.6789" fica.
- **Números de cadastro** (`CADASTRO`): prontuário, matrícula (RA), carteirinha do convênio e apólice, com o contexto por perto. Datas e valores em reais ao lado ficam.
- **Datas de nascimento em tabelas:** num `INSERT`, num CSV ou num JSON, a coluna "nascimento" no cabeçalho vale para as datas das linhas de baixo.
- **Senha logo depois da palavra** ("Login admin, senha bGsE$34", "rede Visitantes, senha Visit@2026"), quando o valor tem cara de senha; "senha inválida" e "senha 123456" ficam.
- **Cookies de sessão** (`Cookie: session_id=...`, `Set-Cookie: PHPSESSID=...`) viram `SEGREDO`.
- **O nome da coluna é o contexto da célula** em CSV, Excel e JSON: "11/01/1941" na coluna `data_nascimento`, "Ana" na coluna `nome` e um CPF sem pontuação na coluna `cpfCliente` agora somem (nomes de coluna com `_`, `-` e camelCase viram palavras). No Excel, datas e números guardados como valor (não como texto) também são protegidos; restaurados, voltam como texto.
- **E-mail codificado em URL** ("checkout?email=ana%40example.com"), **endereço sem número na nota fisc

The release on GitHub

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the PyPI package declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.8.0
Latest stable
0.8.0
Status
current
Withdrawn
no

Source: pypi.org · 2026-11-19. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-19 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-1b5de42bf386526fe…
License
MIT

Source: the package registry · 2026-11-19.

Usage

Downloads
739 in the last month

Source: pypistats.org · 2026-11-19.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 0.8.0 on PyPIExists and can be installedmatchesPyPI · 2026-11-19
Repository github.com/guhttps/veuOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.guhttps
GitHub owner
a personal account (guhttps)
Repository
github.com/guhttps/veu
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-18.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 8 record checks met · 1 does not apply

  • #5,752 of 20,610 packages by monthly downloads, tied with 6 others
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-18). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.guhttps/veu

Answered from the data above

Who publishes io.github.guhttps/veu?

The registry ties the namespace io.github.guhttps to the GitHub account guhttps; only its owner can publish under it. Its linked repository, github.com/guhttps/veu, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.guhttps/veu safe to install?

We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.guhttps/veu been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.guhttps/veu publish a security policy?

Yes: its repository has a public security policy (github.com/guhttps/veu/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.8.0, the latest stable release on PyPI.

Where is the source code of io.github.guhttps/veu?

In github.com/guhttps/veu, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
registry · 2026-11-19
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
package registry · 2026-11-19
Integrity hash
declared (sha256)
package registry · 2026-11-19
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-11-19
Popularity
739 downloads a month
package registry · 2026-11-19
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
your machine
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.guhttps/veu: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.guhttps/veu

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 8 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.guhttps/veu)](https://protocolprobe.com/mcp/servers/io.github.guhttps/veu)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology