mcpbeat Sign in

Tribunal TJPR: Processo MCP Server

answering

Tribunal TJPR: Processo is answering right now. Last checked 10 min ago. It exposes 7 tools. Last commit 19 Aug 2026.

Tribunal TJPR: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

Uptime history 58 days of history · worst day 93%
58 days agonow
98.9%
Uptime 24h
91 of 92 checks
7
Tools
read from the server
1474 ms
Response time
average over 24h
0
Stars
last commit 19 Aug 2026

What changed 81

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 August 2026. No other catalogue keeps this.

11 Oct a tool changed version3 times that day
8 Oct a tool changed version
6 Oct a tool changed version3 times that day
5 Oct a tool changed version
3 Oct a tool changed version
2 Oct a tool changed version2 times that day
1 Oct a tool changed version
13 Sep a tool changed version2 times that day
9 Sep a tool changed version
8 Sep a tool changed version
and 71 more, back to 21 August 2026

Tribunal TJPR: Processo does not always answer

Over the last week it answered 97.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add tribunal_tjpr_processo-mcp --transport http https://api.mcp.ai/p_tribunal_tjpr_processo
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "tribunal_tjpr_processo-mcp": {
      "url": "https://api.mcp.ai/p_tribunal_tjpr_processo"
    }
  }
}
~/.codex/config.toml
[mcp_servers.tribunal_tjpr_processo-mcp]
url = "https://api.mcp.ai/p_tribunal_tjpr_processo"
.cursor/mcp.json
{
  "mcpServers": {
    "tribunal_tjpr_processo-mcp": {
      "url": "https://api.mcp.ai/p_tribunal_tjpr_processo"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "tribunal_tjpr_processo-mcp": {
      "url": "https://api.mcp.ai/p_tribunal_tjpr_processo"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

authenticate
authenticate
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.
connect
connect
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.
marketplace
marketplace
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.
report
report_bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
show
show_version
Show the current MCP platform and adapter versions.
toolkit
toolkit_info
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
tribunal
tribunal_tjpr_processo_consultar
Tribunal TJPR: Processo, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

Endpoints

URLTransportStateLatencyChecked
https://api.mcp.ai/p_tribunal_tjpr_processo streamable-http answering 398 ms 10 min ago

Alternatives to Tribunal TJPR: Processo

same job, measured the same way
Tribunal TJSC: Processo
by mcp-dir

Tribunal TJSC: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering
Tribunal TJRJ: Processo
by mcp-dir

Tribunal TJRJ: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering
Tribunal TJMG: Processo
by mcp-dir

Tribunal TJMG: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering
Tribunal TRF3: Processo
by mcp-dir

Tribunal TRF3: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering
Tribunal TRF1: Processo
by mcp-dir

Tribunal TRF1: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering
Tribunal TRF5: Processo
by mcp-dir

Tribunal TRF5: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering
Tribunal TRF2: Processo
by mcp-dir

Tribunal TRF2: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering
Tribunal TRF6: Processo
by mcp-dir

Tribunal TRF6: Court Case, official-source lookup. Platform-hosted, pay per query with prepaid credi

7 tools answering

Tribunal TJPR: Processo — questions

Answers built from our own checks of this server.

What can Tribunal TJPR: Processo do?
It exposes 7 tools, read directly from the server on our last check. Among them: authenticate, connect, marketplace, report_bug, show_version, toolkit_info and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Tribunal TJPR: Processo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 1474 ms. The bar chart above shows every period we have measured.
How do I connect Tribunal TJPR: Processo?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tribunal TJPR: Processo need an API key?
No. Tribunal TJPR: Processo completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tribunal TJPR: Processo?
It answers our handshake in 1474 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Tribunal TJPR: Processo open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.