Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Projuris ADV

REMOTE · API.MCP.AI

Wrapper for the official Projuris ADV REST API (legal practice management): cases, people (clients/p

Available components

0 this week 76 Trust /100

Last scanned (14 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2923 tokens (~76/item across 38 items; 38 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 38 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 39 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.460 → 0.9.467 functional
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: pass → 0.97 functional
    • Server version: 0.9.459 → 0.9.460 functional
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.454 → 0.9.459 functional
  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.452 → 0.9.454 functional
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.450 → 0.9.452 functional
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.449 → 0.9.450 functional
  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.442 → 0.9.449 functional
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.429 → 0.9.442 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.mcp.ai/p_projuris

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ai CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 1bf4d405299e078a0e62ff16cded599b
SANs: mcp.ai, *.mcp.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.mcp.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
mcp.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.mcp.ai/p_projuris Verified 200
http (plaintext) http://api.mcp.ai/p_projuris Inconclusive 406
MCP tools · 38 exposed · ~2,794 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
authenticate ~99

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

connect ~42

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

marketplace ~532

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

NameTypeReqDescription
actionstring––
argumentsstring––
cancel_commentstring––
cancel_reasonstring––
conversationstring––
immediateboolean––
limitnumber––
mcp_idstring––
messagestring––
prompt_bodystring––
prompt_categorystring––
prompt_descriptionstring––
prompt_slugstring––
prompt_targetsarray––
prompt_titlestring––
prompt_toolstring––
prompt_varsstring––
querystring––
report_contextstring––
request_detailsstring––
request_namestring––
tier_slugstring––
tool_idstring––

No output schema declared.

No examples provided.

projuris_consulta ~95

Busca genérica: POST /<recurso>/consulta com `filtro` (corpo). `recurso` = nome kebab-case (ex.: "processo", "pessoa", "intimacao"). Use para entidades sem tool de consulta nomeada.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––
recursostringyes–

No output schema declared.

No examples provided.

projuris_consulta_andamento ~76

Busca Andamentos/movimentações do processo por filtro (POST /andamento/consulta-geral). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_apontamento_horas ~81

Busca Apontamento de horas (timesheet) por filtro (POST /apontamento-horas/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_assunto ~71

Busca Assuntos/matérias por filtro (POST /assunto/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_atendimento ~76

Busca Atendimentos (CRM/relacionamento) por filtro (POST /atendimento/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_contrato ~73

Busca Contratos (honorários) por filtro (POST /contrato/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_intimacao ~73

Busca Intimações/publicações por filtro (POST /intimacao/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_pessoa ~77

Busca Pessoas (clientes, partes, advogados, contatos) por filtro (POST /pessoa/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_processo ~79

Busca Processos/casos (judicial e extrajudicial) por filtro (POST /processo/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_receita_despesa ~78

Busca Financeiro: receitas e despesas por filtro (POST /receita-despesa/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_tarefa ~85

Busca Tarefas (compromissos, prazos, providências) por filtro (POST /tarefa/consulta-com-paginacao). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_consulta_usuario ~68

Busca Usuários do escritório por filtro (POST /usuario/consulta). `filtro` = critérios conforme a API; pagine com pagina/quantidade_registros.

NameTypeReqDescription
filtroobject––
paginanumber––
quantidade_registrosnumber––

No output schema declared.

No examples provided.

projuris_create_andamento ~47

Cria um(a) Andamentos/movimentações do processo (POST /andamento). `data` = corpo conforme a API oficial.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

projuris_create_apontamento_horas ~54

Cria um(a) Apontamento de horas (timesheet) (POST /apontamento-horas). `data` = corpo conforme a API oficial.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

projuris_create_atendimento ~49

Cria um(a) Atendimentos (CRM/relacionamento) (POST /atendimento). `data` = corpo conforme a API oficial.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

projuris_create_pessoa ~50

Cria um(a) Pessoas (clientes, partes, advogados, contatos) (POST /pessoa). `data` = corpo conforme a API oficial.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

projuris_create_tarefa ~54

Cria um(a) Tarefas (compromissos, prazos, providências) (POST /tarefa). `data` = corpo conforme a API oficial.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

projuris_create_webhook ~43

Cria um(a) Webhooks de integração (POST /webhook). `data` = corpo conforme a API oficial.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

projuris_get ~63

GET genérico em qualquer recurso REST do Projuris ADV. `path` (ex.: "/processo/123") + `query` opcional. Use para recursos sem tool nomeada.

NameTypeReqDescription
pathstringyes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_apontamento_horas ~53

Busca um(a) Apontamento de horas (timesheet) por código (GET /apontamento-horas/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_arquivo ~52

Busca um(a) Arquivos/documentos (GED). Download em /arquivo/download/{codigo} por código (GET /arquivo/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_assunto ~43

Busca um(a) Assuntos/matérias por código (GET /assunto/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_atendimento ~48

Busca um(a) Atendimentos (CRM/relacionamento) por código (GET /atendimento/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_intimacao ~45

Busca um(a) Intimações/publicações por código (GET /intimacao/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_pessoa ~49

Busca um(a) Pessoas (clientes, partes, advogados, contatos) por código (GET /pessoa/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_processo ~51

Busca um(a) Processos/casos (judicial e extrajudicial) por código (GET /processo/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_receita_despesa ~50

Busca um(a) Financeiro: receitas e despesas por código (GET /receita-despesa/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_get_usuario ~40

Busca um(a) Usuários do escritório por código (GET /usuario/{codigo}).

NameTypeReqDescription
codigo–yes–
queryobject––

No output schema declared.

No examples provided.

projuris_list_webhook ~55

Lista Webhooks de integração (GET /webhook). Pagine com pagina/quantidade_registros.

NameTypeReqDescription
paginanumber––
quantidade_registrosnumber––
queryobject––

No output schema declared.

No examples provided.

projuris_request ~111

Escape hatch: chamada REST crua à API Projuris ADV. `method` (GET/POST/PUT/DELETE/PATCH) + `path` (ex.: "/processo/123" ou "/v2/processo/consulta") + `query`/`body` opcionais. Cobre os 757 recursos, inclusive v2 e configs.

NameTypeReqDescription
bodyobject––
methodstringyes–
pathstringyes–
queryobject––

No output schema declared.

No examples provided.

projuris_update_apontamento_horas ~66

Atualiza um(a) Apontamento de horas (timesheet) (PUT /apontamento-horas). `data` = corpo completo conforme a API oficial, INCLUINDO o campo de código do registro.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

projuris_update_pessoa ~62

Atualiza um(a) Pessoas (clientes, partes, advogados, contatos) (PUT /pessoa). `data` = corpo completo conforme a API oficial, INCLUINDO o campo de código do registro.

NameTypeReqDescription
dataobjectyes–

No output schema declared.

No examples provided.

report_bug ~50

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

NameTypeReqDescription
contextstring––
conversationstring––
messagestringyes–

No output schema declared.

No examples provided.

show_version ~17

Show the current MCP platform and adapter versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolkit_info ~37

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Projuris ADV MCP server?

Projuris ADV is a hosted endpoint at https://api.mcp.ai/p_projuris, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.mcp.ai

# add to Claude Code
claude mcp add --transport http mcp-dir-projuris-mcp 'https://api.mcp.ai/p_projuris'
Common questions

What is the Projuris ADV MCP server?

Projuris ADV is an MCP server listed in the public MCP registry as io.github.mcp-dir/projuris-mcp. Wrapper for the official Projuris ADV REST API (legal practice management): cases, people (clients/p. This page covers its hosted endpoint (https://api.mcp.ai/p_projuris).

Is the Projuris ADV MCP server safe to use?

Projuris ADV scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Projuris ADV MCP server expose?

Projuris ADV exposes 38 tools: projuris_request, projuris_get, projuris_consulta, projuris_consulta_processo, projuris_get_processo, and 33 more. Their descriptions and schemas cost roughly 2,794 tokens of context every time the server is loaded.

Does the Projuris ADV MCP server require authentication?

No. We connected to Projuris ADV without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Projuris ADV MCP server still maintained?

Projuris ADV is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Projuris ADV MCP server?

VerifyMCP ran 12 checks on Projuris ADV, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Projuris ADV: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.