Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mcp-dir/tribunal_tse_pje-mcp --skill tribunal_tse_pje-mcpgit clone --depth 1 https://github.com/mcp-dir/tribunal_tse_pje-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mcp-dir/tribunal_tse_pje-mcp/tribunal_tse_pje-mcp)<a href="https://agentmods.dev/skills/mcp-dir/tribunal_tse_pje-mcp/tribunal_tse_pje-mcp"><img src="https://agentmods.dev/badge/skills/mcp-dir/tribunal_tse_pje-mcp/tribunal_tse_pje-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mcp-dir/tribunal_tse_pje-mcp/tribunal_tse_pje-mcp"><img src="https://agentmods.dev/badge/skills/mcp-dir/tribunal_tse_pje-mcp/tribunal_tse_pje-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00120 | $0.00931 |
| Opus 5 | $0.00060 | $0.00465 |
| Sonnet 5 | $0.00024 | $0.00186 |
| Haiku 4.5 | $0.00012 | $0.00093 |
Grade A, and why
tribunal_tse_pje-mcp scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api.mcp.ai/api/tribunal_tse_pje/consultar \ How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tribunal TSE: Processo Judicial Eletrônico (PJe) — REST API skill
Você tem acesso à Tribunal TSE: Processo Judicial Eletrônico (PJe) REST API na MCP.AI.
Tribunal TSE: Processo Judicial Eletrônico (PJe), consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago.
Base URL
https://api.mcp.ai/api/tribunal_tse_pje
Todo endpoint é um POST na Base URL + o path abaixo. Os parâmetros vão no corpo JSON.
Autenticação
Inclua em toda request:
Authorization: Bearer sk_live_...
Content-Type: application/json
Gere sua chave em https://app.mcp.ai/settings/api-keys (workspace API key
sk_live_…, não expira, revogável). Uma única chave serve pra todos os seus MCPs.
Formato de resposta
{ "ok": true, "tool": "<tool_id>", "result": <payload> }
Exemplo cURL
curl -X POST https://api.mcp.ai/api/tribunal_tse_pje/consultar \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{}'
Reportar problemas
Se um endpoint retornar erro, vazio ou dado inesperado, reporte (não desista calado): POST /api/tribunal_tse_pje/report com { "message": "...", "context"?: "...", "conversation"?: [...] }. Isso notifica o time da MCP.AI.
Endpoints (1)
tribunal_tse_pje_consultar
Tribunal TSE: Processo Judicial Eletrônico (PJe), consulta em fonte oficial. (POST /api/tribunal_tse_pje/consultar)
| Parâmetro | Tipo | Obrigatório | Descrição |
|---|---|---|---|
numero_processo |
string | Não | Parâmetro de consulta "numero_processo". |
cpf |
string | Não | Parâmetro de consulta "cpf". |
cnpj |
string | Não | Parâmetro de consulta "cnpj". |
classe_judicial |
string | Não | Parâmetro de consulta "classe_judicial". |
objeto |
string | Não | Parâmetro de consulta "objeto". |
orgao |
string | Não | Parâmetro de consulta "orgao". |
uf |
string | Não | Parâmetro de consulta "uf". |
municipio |
string | Não | Parâmetro de consulta "municipio". |
ano_eleicao |
string | Não | Parâmetro de consulta "ano_eleicao". |
data_inicial_autuacao |
string | Não | Parâmetro de consulta "data_inicial_autuacao". |
data_final_autuacao |
string | Não | Parâmetro de consulta "data_final_autuacao". |
nome_parte |
string | Não | Parâmetro de consulta "nome_parte". |
nome_advogado |
string | Não | Parâmetro de consulta "nome_advogado". |
oab |
string | Não | Parâmetro de consulta "oab". |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 76 lines · 0 tokens per session scan A cb6592bcfd7e
tribunal_tse_pje-mcp is a skill published in the GitHub repository mcp-dir/tribunal_tse_pje-mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 120 tokens to every session and 931 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
jsonapi
Strict JSON:API v1.1 specification compliance. Trigger: When creating or modifying API endpoints, reviewing API responses, or validating JSON:API compliance.
validating-us-core
Validate FHIR R4 resources and Bundles against US Core / USCDI profiles with the official HL7 FHIR validator before submitting to an EHR. Covers running validatorcli.jar (or the public validator.fhir.org), declaring meta.profile, must-support elements, common conformance gaps (missing code/category/status), and…
api-compliance-checker
Designs GDPR-compliant API patterns, PCI-DSS field handling, SOC2 audit log schemas, HIPAA data endpoints, and regulatory compliance checklists for any API. Use whenever the user asks about GDPR, data privacy, "right to be forgotten", data retention APIs, PCI compliance for payments, HIPAA for health data, SOC2 audit…
adding-activity-logging
Adds or changes activity logging (the audit trail) for a Django model in PostHog. Use when a model's writes must show in the Activity side panel or the advanced activity logs, when adding ModelActivityMixin, an ActivityScope, a modelactivitysignal receiver, an activity describer, or field exclusions, when auditing…
telnyx-10dlc-curl
10DLC brand and campaign registration for US A2P messaging compliance. Assign phone numbers to campaigns.
806-regulations-eu-data-act
Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should…